1

Hello,

We are encountering regular and increasing issues when using Azure Virtual Desktop. Users are reporting frequent instances of logging into an AVD host and only seeing a blank screen.

These are Windows 10 Enterprise for Virtual Desktop machines and are subject to a scaling plan, so none of the 5 in the pool should be on for a period greater than 24 hours at a time.

Fixes thus far have included forcing them off and clearing their user profiles via Registry, Disk Management, Users folder etc, or moving them onto a different host. I also found a fix recently involving restarting a remote service under services.msc. Applying drain mode to the device they’re on and forcing them onto another host sometimes alleviates the issue, but isn’t a guaranteed solution.

This seems to happen capriciously to any user dialling in from any device (we have Win10 & 11 machines in our domain, neither seems to be more susceptible to this). Some manage to entirely avoid the problem.

For clearer detail, reported instances entail the user signing in via the “Remote Desktop” application and connecting to their company virtual desktop option from there. This successfully loads up a new window, but I’m unsure if they then see the typical startup messages e.g. “Applying Group Policy”, “Preparing desktop” before an empty black screen appears.

6 Spice ups
2

This is a known issue with security update KB5043064, Head to September 10, 2024—KB5043064 (OS Builds 19044.4894 and 19045.4894) - Microsoft Support and check for the KIR in the known issues section

ETA We had this issue over the past few weeks with our W10 AVD hosts, the KIR has vastly improved the situation.

4 Spice ups
3

I was just looking for this KB, glad you were able to share it.

3 Spice ups
4

For this example which LCU/update am I targeting, since KIR doesn’t apparently support removing security updates?
I’m not certain how to interpret the correct target from the forum page, I can see 3 options. KB5043064 isn’t listed but WU says it has been installed.

capture1
capture11478×1136 92.3 KB
5

The issue was resolved on 22nd Oct via [KB5045594]

1 Spice up