I was able to get rid of the blank screen delay by modifying the OSOT config (now it shows "Preparing Windows" which keeps users happy). But just having tons of issues in a vGPU enabled environment where the BLAST session freezes on logon occasionally. Or VMs showing as Available, but when users connect they can't get a session (resulting in the VM staying available, and facilitation numerous connection requests that are never successful). I have all the exceptions in place for FSLogix, the Horizon agent, and everything else, but wondering if exceptions are needed for the vGPU driver or something weird like that.

Re: the Black screen and "Preparing Windows"; do you know what is actually modified? We see a similar black screen with ProU+W11, it's marked as a known issue in Liquidware but maybe your fix can work here as well.

Do you use the OSOT tool @Jon Bucud?

I don't, I use Citrix Optimizer 🙂

I'm not sure about Citrix, but on the Omnissa OSOT tool, it's the following setting: "Shorten timeout of desktop session switch to 1s - Machine Policy" After it's been set on a base image, I've never been able to revert it to factory settings, so I always make sure to exclude this on new base images. For base images without the issue, it delays login slightly, but for environments where you have XDR/MDR tech causing a blank screen, this changes the blank scree to "Preparing Windows" which stops tickets and complaints. It sets the following: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System DWORD: DelayedDesktopSwitchTimeout Sets it to: 1

Ah thanks! The session 0 to user session delay switch. I'll check if that ever made it from our Win10 images to Win11.

I think by default it's not set. When I run the OSOT tool it sets it to 1