Welcome to Microsoft Q&A!
Thank you for sharing the screenshots and the troubleshooting steps you’ve already tried.
From the information shown, the failure appears to occur while Windows is searching/assessing for updates, rather than during the actual update installation.
Since Windows is also reporting that it cannot connect to the update service, I recommend focusing first on the update source and network/proxy path.
1. Check whether Azure Update Manager is involved
If the VM is managed by Azure Update Manager, go to:
Azure portal -> Virtual machine -> Operations -> Updates
If you see errors related to periodic assessment, scheduled patching, or Microsoft.CPlat.Core.WindowsPatchExtension, troubleshoot Azure Update Manager first.
2. Review the Windows Update log
Because the issue occurs during the update scan/assessment, generate WindowsUpdate.log from an elevated PowerShell session:
Get-WindowsUpdateLog
Review the entries around the time the scan fails. This can help identify whether the failure is related to connectivity, the configured update source, or another Windows Update component.
3. Verify the Windows Update source and network connectivity
Having general Internet access does not necessarily confirm that the VM can reach the endpoints required by Windows Update.
Firstly, confirm whether the VM is configured to receive updates directly from Windows Update or through WSUS. An incorrect Group Policy or registry configuration can cause the VM to use an unavailable update source.
For a VM using Windows Update directly, also review:
- Outbound NSG rules
- User Defined Routes (UDRs)
- Azure Firewall or other network virtual appliances
- Proxy configuration
- DNS resolution
- TLS/certificate configuration
NSGs, UDRs, proxy settings, and firewall appliances can prevent an Azure VM from reaching the Windows Update endpoints.
For example, you can verify HTTPS connectivity from the VM with:
Test-NetConnection -ComputerName "windowsupdate.microsoft.com" -Port 443
Test-NetConnection -ComputerName "download.windowsupdate.com" -Port 443
Test-NetConnection -ComputerName "dl.delivery.mp.microsoft.com" -Port 443
You can also check whether a WinHTTP proxy is configured:
netsh winhttp show proxy
4. Reset the complete Windows Update components
Since renaming SoftwareDistribution helped only temporarily, I would recommend resetting the complete Windows Update components rather than repeatedly clearing only that folder.
Microsoft provides the Azure VM Windows Update Reset Tool, which resets the Windows Update servicing components, including wuauserv, cryptsvc, BITS, SoftwareDistribution, catroot2, and then re-registers the relevant Windows Update components.
After completing the reset, retry Windows Update.
If the issue persists after completing the troubleshooting steps above, I recommend opening a support request with Microsoft Support for further investigation or submitting feedback through the Feedback Hub if appropriate. Because Microsoft Q&A is a public community forum, so I have limited access to the internal diagnostic information required to investigate product-specific or backend issues in greater depth.
Reference:
Troubleshoot Windows Update failures on Azure VMs - Virtual Machines | Microsoft Learn
Troubleshoot Windows Update network and proxy issues on Azure VMs - Virtual Machines | Microsoft Learn
Troubleshoot Windows Update Errors That Require In-Place Upgrades for Azure VMs - Virtual Machines | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.