Forum Discussion
JPlendo
Sep 19, 2024Brass Contributor
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
TLDR - Azure Virtual Desktop Black Screens. Could be 2 Min long, could be much longer. Tried removing stuck profiles, spun up all new VMs to see if that would fix it, finally disabled an applicatio...
Robert_Hurd
Oct 31, 2024Brass Contributor
Can you share if you have all other regular monthly KB patches? We are currently running all KB's and the KIR is currently disabled. We have 20 hosts with 10 users each and we usually get 1-5 users a day needing to be moved to a new host. Can you clarify if you have the Sept/Oct KB's removed also? We are migrating to Windows 11 currently as that was the plan anyways, but this issue and the Defender Exclusions/Network Protection issue that I think was patched yesterday was making us pause that deployment, but now we just see to many pluses for dumping Windows 10 and are very disappointed with the current state of MS support. I will be attending Ignite and I plan to voice this concern to anyone that can listen and will be using this thread for historical examples.
m77ewl
Oct 31, 2024Brass Contributor
you don't need to disable the KIR anymore as per Microsoft's documentation. you can just unlink the policy or delete the policy. https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#3421msgdesc
If you install an update released October 22, 2024 (KB5045594) or later, you do NOT need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before October 22, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below.
It would also be good to know what's configured in your fslogix Group policy settings and redirections.xml
If you install an update released October 22, 2024 (KB5045594) or later, you do NOT need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before October 22, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below.
It would also be good to know what's configured in your fslogix Group policy settings and redirections.xml