In a recent turn of events, Microsoft has acknowledged ongoing issues affecting Azure Virtual Desktop (AVD) users following the installation of July’s non-security preview update (KB5040525). Despite Windows 10 nearing the end of its support lifecycle, this update has inadvertently introduced complications that have left users facing unexpected challenges.
Black Screen Dilemma
Users logging into AVD have reported experiencing a frustrating black screen that can persist for a duration of 10 to 30 minutes. This issue is compounded by potential problems with single sign-on (SSO) for Office applications, including Outlook and Teams, which may encounter connectivity disruptions. Microsoft has attributed this predicament to a deadlock occurring between the Azure Active Directory (AAD) broker and the AppX deployment service (AppxSvc), as well as the Background tasks infrastructure service.
For those utilizing FSLogix user profile containers in multi-session environments, the likelihood of encountering these issues is notably higher. Microsoft acquired FSLogix in 2018, aiming to enhance the performance of Office 365 in virtual settings, yet the current situation seems at odds with their goal of streamlining user experience.
Microsoft has clarified that this recent issue differs from a similar scenario encountered earlier in October, where AppxSvc was reported to be in “an invalid state,” also resulting in a black screen. Fortunately, that particular problem was addressed in the October 22 preview update.
Windows 11’s Ongoing Challenges
Meanwhile, Windows 11 24H2 users are not exempt from Microsoft’s update-related woes. After resolving some inaccuracies in the Disk Cleanup tool’s free space estimates, the company has admitted that Task Manager is exhibiting unexpected behavior. Following the installation of the October 2024 non-security preview update, users discovered that Task Manager was displaying zero counts for Apps, Background Processes, and Windows Processes, despite active applications running in the background. This anomaly appears specifically when the ‘Group by Type’ view is enabled on the Processes page.
To gain further insight into this issue, we reached out to Dave Plummer, the original author of Task Manager from the Windows NT 4.0 era. Plummer noted, “I don’t recall my original task manager breaking down the count by type … so I imagine that’s new code that was added at some point along the way.” He characterized the situation as a “fairly severe bug,” while also acknowledging that it might have gone unnoticed during testing, given the infrequency with which users check these counts.
As these challenges unfold, it raises questions about the effectiveness of Microsoft’s quality assurance processes and the overall user experience in their evolving software landscape.
