[German]Microsoft is investigating an issue that is preventing the download of security updates via Windows Server Update Services (WSUS) for Azure Virtual Desktops. Virtual Desktop instances are stuck at the May 2021 update level.
Azure Virtual Desktop is Microsoft's service that enables remote deployment of Windows 10 and other services from the Azure cloud. Now, there is a very specific issue in this environment that affects Windows 10 and its security updates when managed through a Windows Server Update Services (WSUS) running on Microsoft Azure. If the Virtual Desktop is still on Windows 10 version 1909, no updates can be obtained after the May 2021 patchday. In the Windows 10 version 1909 status area, Microsoft writes about this on July 2, 2021:
We are investigating an issue where devices running Windows 10 Enterprise multi-session, version 1909 might not be able to download updates later than May 2021. This is observed in the Settings app under the Windows Update setting, which will display the message "You're up to date" even if no updates later than May 2021 have been installed.
The following platforms are affected:
- Client: Windows 10 Enterprise multi-session, version 1909
- Server: Windows Server multi-session, version 1909
The status text does not mention WSUS, but support article KB5004926 states:
Windows 10 Enterprise Multi-Session, version 1909 (Azure Virtual Desktops (AVD)) may not be receiving monthly security updates from Windows Server Update Services (WSUS).
Microsoft suggests two workarounds for affected administrators. Solution 1 is to "deploy" (i.e., reinstall) the latest images from Azure Marketplace with all security updates to the existing devices. Unless re-deploying the system images is not an option, it is possible to manually install the June 2021 (and later if necessary) security updates on these devices. This would require pre-downloading them from the Microsoft Update Catalog. Instructions on how to do this can be found in KB5004926. Microsoft hopes to provide a solution for the problem soon. (via)
Cookies helps to fund this blog: Cookie settings