Microsoft's recent Windows 11 update, KB5083769, was released with critical security patches, but it has since caused a cascade of issues for users. Beyond well-known problems like BitLocker lockouts and boot loops, this update is now disrupting several third-party backup applications. The root cause appears to be a bug in the Volume Shadow Copy Service (VSS), which is essential for creating system snapshots used by backup tools. If you rely on software like Acronis Cyber Protect Cloud, Macrium Reflect, NinjaOne Backup, or UrBackup Server, this update may leave your backup routines broken. Below, we answer common questions about the situation and how to proceed.
What specific backup apps are affected by the KB5083769 update?
Reports indicate that a broad range of third-party backup applications are experiencing conflicts after installing Windows 11 update KB5083769. Affected programs include Acronis Cyber Protect Cloud, Macrium Reflect, NinjaOne Backup, and UrBackup Server. These tools rely heavily on the Volume Shadow Copy Service (VSS) to take consistent snapshots of files for backup. The bug disrupts VSS operations, causing backups to fail or behave unpredictably. Users of other VSS-dependent backup software may also encounter issues, though the listed names have been most widely reported. If you are unsure whether your backup app relies on VSS, check its documentation or contact support for guidance.
What is causing these backup applications to break?
The core problem lies in a bug within the Volume Shadow Copy Service (VSS), a Windows service that allows backup software to create point-in-time snapshots of files without interrupting active processes. The KB5083769 update introduced an error in how VSS handles snapshot requests, leading to failures when backup apps attempt to utilize this service. Since many third-party backup tools depend on VSS for consistent and disruption-free backups, the bug effectively cripples their core functionality. Microsoft has not yet explained the exact mechanism, but independent researchers have traced the issue back to changes in the VSS component of the update.
Were there other known issues with this update before the backup app problems?
Yes, KB5083769 has been problematic since its release. Before the backup app conflicts emerged, users reported a range of other issues. These include BitLocker lockouts, where the encryption tool would deny access to drives after installation; unexpected boot loops, causing systems to restart repeatedly; and a Remote Desktop bug that prevented connections. The backup app disruption adds to a growing list of headaches for Windows 11 users. Microsoft has acknowledged some of these problems in its support forums but has yet to release a comprehensive fix. The update was intended primarily as a security patch, but the unanticipated side effects have made it a controversial release.
How can I fix my backup software if it stopped working?
According to BleepingComputer and other sources, the most reliable workaround is to uninstall update KB5083769. You can do this through Windows Update settings or by using the Command Prompt to run wusa /uninstall /kb:5083769. After removing the update, restart your system and test your backup application. In many cases, backup functionality returns to normal. However, uninstalling a security patch leaves your computer vulnerable to the exploits the update was meant to address. Microsoft has not provided an alternative fix, so weigh the risk of missing security updates against the immediate need for reliable backups. Keep an eye on official Microsoft channels for a future patch that resolves the VSS bug.
When is Microsoft expected to release a patch for this issue?
As of now, Microsoft has not announced a specific timeline for a fix. The company typically releases cumulative updates on the second Tuesday of each month (Patch Tuesday), but emergency out-of-band patches are possible for critical issues. Given the severity of the backup app incompatibility and the previous reported problems, many hope for a resolution soon. Users should monitor the Windows 11 update history page and the Microsoft Security Response Center for updates. In the meantime, the only confirmed solution is to remove KB5083769, as discussed above. Stay patient and consider using built-in Windows backup tools as a temporary alternative.
Does this problem affect all versions of Windows 11?
The KB5083769 update targets Windows 11 version 21H2 and 22H2 (the main editions as of this writing). If you have automatic updates enabled, you likely have this patch installed. Users on older Windows versions (Windows 10) are not affected directly because the update is specific to Windows 11. However, similar VSS bugs have appeared in past updates for other Windows versions, so cross-platform caution is always wise. To check if you have the update, go to Settings > Windows Update > Update History and look for KB5083769. If present and you rely on third-party backup tools, consider applying the uninstall workaround.
Is there a temporary workaround besides uninstalling the update?
Currently, no other reliable workaround has been publicly shared. Some users have attempted to repair VSS manually using Windows tools like vssadmin, but these efforts have not consistently resolved the conflict caused by the update. Disabling third-party security software or running backup apps in compatibility mode also fails to address the underlying VSS bug. Therefore, uninstalling KB5083769 remains the most effective and recommended temporary step. If you decide to keep the update, be prepared to use alternative backup methods (e.g., manual file copying or built-in Windows 7 backup). Microsoft may later issue a fix that restores VSS functionality without requiring removal of the security patches.