This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 9%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
I am experiencing issues with Windows updates failing to install on my SQL Server in VM - Windows environment. The failures started on 2026-01-01, and the updates are being applied through standard Windows Update. The process fails at various steps, and I do not have specific error codes or logs capturing the root cause.
Azure-hosted SQL Server on a Windows virtual machine.
I have not tried anything yet.
I am seeking guidance to identify the cause of the update failures and steps to resolve the issue.
An Azure service that is used to provision Windows and Linux virtual machines.
Installation Failure: Windows failed to install the following update with error 0x80246013: 2022-08 Security Update for Windows Server 2016 for x64-based Systems (KB5012170).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 64%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHY%3C/text%3E%3C/svg%3E)
Hi @hbpaul ,
Issue** **Description: Windows Security Updates were failing to install on the Azure SQL Server VM hbdb-sql-vm7.
Investigation:
Azure-side checks showed the VM and Azure platform were healthy.
The issue was isolated to the guest Windows operating system.
CBS logs and troubleshooting indicated Windows servicing/component issues.
Initial DISM repair reported that the required source files could not be found.
SFC also detected system file corruption that could not initially be fully repaired.
Resolution** **Provided: Recommended repairing the Windows component store using DISM, running sfc`` ``/scannow, rebooting the VM, and then retrying Windows Update.
Final** Resolution: The customer performed DISM followed by SFC cleanup and rebooted the VM. After the reboot, Windows Update was retried and completed successfully without any **errors.