Forum Discussion
AppReadiness Service and Black Screen
Hi Lee, since applying the updates MS advised I havent seen this issue on 3 separate deployments at worst they may get a 5-10 second black screen but that is fine as it carries on after that, I would recommend logging with Microsoft, alternatively you could update these to one of the VM's to 20H2 and monitor if any report issues on that if not migrate all to that. Also what HDD's are you running on your WVD's?
StevenR , The server is all patched, has the registry keys added and the latest FSLogix version installed too, it was fine until yesterday when this started again with no changes applied and rebooting cleared it for about 5 active hours. I only have the one VM to keep the costs down but I'm going to go with having two and shutting down one at a time in future. With only 5 or 6 users active at a time it never strains and works well, except for this particular issue. I am looking to build a new pool from scratch on 20H2 to ensure nothing came through the original image. I'll report back once that's built.
Thanks
Lee
Has anybody resolved this yet? It's March 4th, 2021.
We have a case open with Microsoft but after two weeks we're no closer to a solution.
Windows EVD 20H2 19042.804 (fully patched)
FSLogix 2.9.7654.46150
Black screen for 30-90 seconds at logon.
Registry keys from here do not help, and some logons end up with a broken start menu and inability to authenticate to Office365
https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/windows-virtual-desktop-blank-screen
Hi aaronmountford ,
Sorry to here that, if its happening every time it might be worth building another VM to add to the mix put it on win 10 2004 and use GPO/computer/policy/administrative/windows updates/(something) for business and set it to hold the version at 2004 while MS resolve the one that doesn't work, I am running the same versions as yourself and I am not seeing this issue. also how many users do you have on what size VM?
Thanks StevenR
We actually have 4 in a pool (well currently 3 as one is out for troubleshooting). Two are built from an image mid last year (20h1-evd-o365pp), and two from an image from late last year (20h2-evd). Both receive updates as per our security policy. The sizes are all Standard D4s v3.
We don't have a heavy load on them, peak usage on each would probably be 15-20 users but that's a guess. Could be less. Even with just 1 user we get this issue, so it's definitely not performance based.
The one thing we have determined is that disabling the FSLogix services removes the issue completely, although it introduces a bigger problem - group policy fails to apply if the FSLogix services are disabled.
For what it's worth we're using FSLogix with cloud-cache only (Azure Files).
