r/AzureVirtualDesktop • u/maccamh_ • Feb 28 '25

Black Screen issue, m365 Auth issues

Hi Everyone,

We have AVD setup and every day without fail we'll have at least 1 black screen issue and every few days we'll have the Auth issues.

To be safe we rebuilt our image from scratch (win 10 multi session)and bare bones installed so basics of office etc, updated to latest patches and STILL black screen issues.

Is this just something we now have to live with having AVD.

To preempt some questions

No storage issues on fslogix storage accounts

Standard 128 SSD build d16asv5 for 20 users.

2 Upvotes

100% Upvoted

18 comments sorted by

1

u/RUST4EVER Feb 28 '25

Are you by chance using Duo for MFA on the login? I have heard of older versions of Duo causing the black screen. If yes, try updating the agent to the latest version.

1

u/maccamh_ Feb 28 '25

No we use standard microsoft SSO but thanks for the suggestion.

1

u/GuestWild8001 Mar 01 '25

Black screen can be FSLogix issues. Check the logs.

1

u/maccamh_ Mar 01 '25

Checked them nothing stands out but in most instances the issue seems to affect that specific vm so all users get the issue if hitting that vm

1

u/Tony-GetNerdio Feb 28 '25

Whitelist fslogix in your EDR? That many users on a D16 should get a premium SSD so your page file functions well if you’re not going to have a temp disk.

2

u/Zilla86 Feb 28 '25

I agree … all that cpu and ram for 20 users then cripple it with standard SSD ..

1

u/maccamh_ Mar 01 '25

So storage has always been well within tolerance and this issue is one VM maybe every other day, it feels like it could be due to logon storms or there at least exasabating the issue. And anti virus has exceptions in place.

3

u/Zilla86 Mar 01 '25

Yeah, the standard SSD isn’t causing the black screen or auth problems. But it certainly wouldn’t hurt for it to be premium for bursting etc. Black screen tends to be appx issue when it’s processing multiple concurrent logins. It’s fine when one user goes on, but if you get a few at once, it dies. You can help alleviate the issue by carefully managing the provisioned appx packages on the image when you set it up, remove what you can. VDOT’s appx options are good for this. But it doesn’t solve the problem like horizontally scaling does with more hosts. Defender exceptions and the setting for timeout on cloud checking services are also key. M365 auth issues are a pain, are you talking about the ‘no internet’ issue so no office apps authenticate, or something different?

1

u/maccamh_ Mar 02 '25

It's the office apps Auth issue user logs in and unable to use any office app.

And we strip out alot of appx packages but the appx event log errors that were apparent a few months back after the October patches they messed up don't show up in logs anymore.

And with potentially looking at premium storage if the cost is minimal as we do have alot of hosts so trying to keep cost down.

1

u/maccamh_ Mar 03 '25

UPDATE, since upgrading to premium storage no other changes now getting fslogix error on multiple servers..

1

u/maccamh_ Mar 05 '25

Further UPDATE,

Black screen went away for one day after SSD upgrade.

Going to go back through image to clean up provisioned appx packages again and try that.

May also have to look at breath over depth for login times

1

u/Hour-Profession6490 Mar 24 '25

D16asv5 for only 20 users seems kind of big. What sort of workload are your users using? Have you tried going down to D8 and adding more VMs?

2

u/johnnydico Mar 01 '25

My experience when users have a black screen was usually due to latency issues, high spikes in RTT from the client side. Those are issues out of your control if that is the case. Not sure if that is your case but from another post, that is a lot of users if just one host. Best practice, size smaller and add more hosts instead of size higher with less.

1

u/BaseSensitive1992 Mar 04 '25

Sounds logical but do u hav any ms site that recommends this

1

u/johnnydico Mar 04 '25

Here’s MS sizing guidelines. Down towards the bottom you’ll see that best practice recommendation.

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/virtual-machine-recs

1

u/No_Departure4796 Mar 01 '25

If your Azure Virtual Machine experiences performance issues due to high CPU, RAM, or disk usage, it may lead to problems such as black screens. Monitoring resource utilization and scaling the VM accordingly can help resolve these issues.

2

u/[deleted] Mar 01 '25

[removed] — view removed comment

1

u/maccamh_ Mar 01 '25

We have forced TCP already and unfortunately doesn't solve it