User Profile
Robert_Hurd
Brass Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
Anyone seeing slowness on their AVD hosts starting last week, mostly on startup in the morning, but also seems to come in waves? We got notified on Wednesday that the Routine Planned Maintenance in Progress for App Service in Canada Central. Since this our users are reporting waves of slowness. I know this is not directly related to the Black screens, Auth for outlook, one drive issues, but I figured it was a attentive AVD support pool that may be able to share if they are seeing this also. I have put in a ticket with MS and am awaiting first contact. Thanks everyone for anything your willing to share.Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
Well here is the Service Health Advisory update.... Workaround: This issue can be reduced significantly by installing this latest patch. An alternative workaround is available but may not be feasible for all customers. The suggested alternate workaround for the issue is for customers to move to Windows 11, as the issue is less likely to occur on this operating system.Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
I did not see that, but if you could mention it again here, that would be great. If it has to do with the fslogix option to 0 then not an option for us as we use appxPackages quite a bit. You seem to mention that you "enable" the KIR. We might try that, but really Windows 11 is working well so far and we were always planning on moving, so now that the Defender issue is reported resolved, I think we will just focus on that.Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
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.Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
So we started having Defender Network Protection and Defender Exclusion issues about 3 weeks ago with our Windows 10/11 AVD pools managed with Intune. Opened ticket with Microsoft and have been working on it ever since. The issue is related to Antimalware Client Version: 4.18.24080.9, if you revert this to an earlier version it starts working again. Revert with this command. run "C:\programdata\microsoft\Windows Defender\Platform\4.18.24080.9-0\MpCmdRun.exe" -revertplatform Next issue, was black screens on login and Outlook client issues on AVD host pools started yesterday. I was able to install the proposed revert patch and that seems to be solved now. I have shared this info with MS and they are working with the Product Group to get the Defender issue patched. Hope this helps some!Re: Azure Virtual Desktop - Black Screens on logins - What we've tried so far
We started having the Defender Network Protection and Defender Exclusions issue on our Win 10/11 AVD multi-session pools about mid Sept, have been working with MS for 3 weeks. Yesterday black screens at logins starting happening on mass. Outlook issues in AVD session, etc. I have applied the fix for the black screens and seems resolved. Also found that the Defender Antimalware Client Version: 4.18.24080.9 that was released on Sept 17 is causing the defender NP and exclusion issue. MS is going to revert back or at least fix the issue for go forward. I have shared all this info with MS and my open ticket. You can temp fix the issue my reverting your version with this command. run "C:\programdata\microsoft\Windows Defender\Platform\4.18.24080.9-0\MpCmdRun.exe" -revertplatformRe: AVD NEW desktop client version 1.0.5555.600 now shows SHUTDOWN status on Pool Host
No, what I mean, is after you turn off validation the agent will automatically downgrade on the pool hosts. Took overnight for one pool and a morning for the other. Not sure if you need hosts on for the downgrade to occur..Re: AVD NEW desktop client version 1.0.5555.600 now shows SHUTDOWN status on Pool Host
Christian1990 I just removed the newest version. Then stopped the rdbootloader service from task manager then then installed the newest version of the desktop agent I could find for download, it was only 1.0.4x When I uninstalled the 1.0.5555.600 version it made my pool host unavailable until I reinstalled the older version. I thought it would still work as it keeps 3 versions on at a time for this exact use scenario. I think the issue is there was new SxS updates also and must do something a bit different then the past. I hope this helps you.AVD NEW desktop client version 1.0.5555.600 now shows SHUTDOWN status on Pool Host
Some of our host pools have updated to this newer version of the AVD desktop client, and now when we shutdown these hosts the status now shows "Shutdown" instead of "Unavialable". Is this expected behavior? The new version also seemed to stop "Start VM on connect" setting from working. I uninstalled the 1.0.5555.600 desktop agent and then reinstalled an older version, then got it to auto update and this seemed to fix this issue. As far as in the past with autoscale scripts, etc, if the VM was in a shutdown state it would not work. Is this new "Shutdown" status by design? Also noticed there is no release notes for this version of the AVD desktop agent. ThanksRe: Remote assistance with Quick Assist is changing
Why is Microsoft doing this? Do we have an official response? This was a useful app that is now rendered useless that is not supporting WSUS updates. This is a joke! Get your priorities together Microsoft. Stop breaking good 'WINDOWS" experiences with your horrible store, no one wants it, that is why we are on WINDOWS!Re: (Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004
PieterWigleven Thanks, we built new pool with 2004 today and had the same issue, we put in the reg value and we can connect now but when we go to programs and features we do not see the SxS Network Stack at all. I have attached a pic. Will wait to hear back.
