Windows 11 April Update Disrupts Backup Software: Q&A

Microsoft's April 2023 update for Windows 11 (KB5083769) was intended to deliver critical security fixes, but it has since triggered a series of unexpected problems. Beyond earlier reports of BitLocker lockouts, boot loops, and Remote Desktop glitches, users now face conflicts with popular third-party backup applications. The root cause appears to lie in a flaw within the Volume Shadow Copy Service (VSS), a core Windows component that handles snapshot-based backups. Below, we answer the most pressing questions about this ongoing issue and what affected users can do.

What specific problems did the KB5083769 update cause?

Shortly after its release, Windows 11’s April cumulative update (KB5083769) began causing a range of system-level issues. Some users reported that BitLocker drive encryption prompted unexpected recovery key requests, effectively locking them out of their devices. Others experienced boot loops where the system would restart repeatedly, making normal operation impossible. Additionally, a bug in Remote Desktop connections prevented some users from accessing remote machines. More recently, the update has been found to interfere with third-party backup software, preventing the creation or restoration of system snapshots. These varied symptoms all trace back to the same underlying update, highlighting how a single security patch can inadvertently destabilize multiple Windows features.

Which third-party backup apps are affected by the update?

A wide range of popular backup and recovery solutions have been impacted. Reports cite conflicts with Acronis Cyber Protect Cloud, Macrium Reflect, NinjaOne Backup, and UrBackup Server, among others. These applications rely heavily on the Volume Shadow Copy Service (VSS) to take consistent point-in-time snapshots of files and system volumes. After installing KB5083769, users of these tools have encountered failures when initiating backup jobs, receiving error messages related to VSS operations. Some programs also hang or crash when attempting to restore from earlier snapshots. The scope suggests the bug affects any software that interacts deeply with the VSS infrastructure, so even lesser-known utilities may experience similar disruptions.

Why does the update break backup software—what is the VSS bug?

The root cause lies in a defect introduced by KB5083769 in the Volume Shadow Copy Service (VSS). VSS is a built-in Windows feature that coordinates backup applications, file system writers, and storage hardware to create crash-consistent snapshots without interrupting running applications. When working correctly, VSS ensures backups can be taken safely even while files are in use. The update apparently corrupts the communication between VSS and backup tools, causing snapshot creation to fail. Instead of returning a success code, the service may time out or produce incomplete data. Because VSS is a foundational component, any flaw in its implementation can cascade into failures across all dependent software—explaining why multiple backup apps are affected simultaneously.

How can I restore my backup software functionality?

According to cybersecurity news outlet BleepingComputer, the most reliable fix currently is to uninstall the problematic update KB5083769. To do this, go to Settings > Windows Update > Update history, then select Uninstall updates. Find KB5083769 in the list, click Uninstall, and follow the prompts. After restarting your system, your backup applications should begin working normally again. Keep in mind that uninstalling this update also removes the security fixes it contained, so your computer may be more vulnerable to threats. It is advisable to monitor Microsoft’s release channels for a permanent patch—once issued, reinstall the corrected update to restore protection.

Is there a permanent fix from Microsoft yet?

As of now, Microsoft has not released an official patch to resolve the VSS bug triggered by KB5083769. The company typically addresses such issues in subsequent cumulative updates, but no timeline has been announced. Users are left with the temporary workaround of uninstalling the update and waiting. For businesses and IT administrators, this creates a difficult trade-off between system security and backup reliability. Until a fix arrives, it is wise to keep a close eye on the Windows 11 Update History page for announcements. Once a new update supersedes KB5083769 with a corrected VSS module, affected users should apply it promptly.

What should I do in the meantime to protect my data?

While waiting for Microsoft’s permanent solution, consider these steps to maintain backup operations:

• Uninstall KB5083769 as described above to restore VSS functionality immediately.
• Perform a manual backup of critical files using methods that don’t rely on VSS, such as simple file copy or cloud synchronization.
• Enable System Protection and create a manual restore point periodically; this uses the same VSS service but may work if the bug is inconsistent.
• If you cannot uninstall the update (e.g., due to security policies), test your backup tool with a small set of files first to see if any workaround exists in the software’s settings.
• Keep your backup application updated to the latest version, as developers may release patches that work around the VSS flaw.
• Monitor community forums like BleepingComputer for any temporary scripts or registry tweaks that mitigate the issue without fully removing the update.

Remember that no workaround is perfect; prioritizing a full uninstall of KB5083769 remains the most effective short-term solution.

Will future Windows updates prevent similar conflicts?

Microsoft’s update testing process includes a preview ring for enterprises and enthusiasts, but as this incident shows, regressions can still slip through. The company has improved its feedback loop with tools like Windows Insider and dedicated diagnostic data collection, but no system is infallible. For users, the best defense is to delay non-critical updates by a few days to monitor reports from early adopters. IT administrators should consider using Windows Update for Business policies to control update deployment, testing each cumulative update on a small subset of machines before wide rollout. Moving forward, Microsoft is likely to strengthen its VSS testing procedures given the severity of this bug, but users should remain vigilant and maintain robust backup strategies independent of any single update.