Organizations relying on Windows 11 endpoints for backup-dependent recovery assurance have, for the duration of this defect, effectively lost their most operationally accessible ransomware recovery control. For businesses in regulated sectors that require demonstrable, tested backup capability as part of their continuity or compliance posture, this gap may constitute a reportable control failure until remediated. The forced choice between patch currency and backup integrity represents a direct operational cost: either accept unpatched systems or accept a recovery capability gap, with no current middle path from Microsoft.
You Are Affected If
Your organization has deployed KB5083769 to Windows 11 24H2 or 25H2 endpoints
You use Acronis Cyber Protect Cloud, Macrium Reflect, NinjaOne Backup, or UrBackup Server as your backup platform
Your backup infrastructure relies on VSS for application-consistent or system snapshots on Windows endpoints
You operate auto-deployment patch policies that would have pushed KB5083769 without pre-deployment backup validation testing
You use Acronis Cyber Protect Cloud and monitor endpoint connectivity via the cloud management console
Board Talking Points
A Microsoft Windows update released in April 2026 has disabled the backup capability on affected Windows 11 systems, meaning those systems currently cannot be restored quickly if hit by ransomware or a system failure.
IT and security teams should immediately verify whether backup systems are still functioning and, if not, roll back the problematic update while Microsoft develops a fix — this decision should be documented as a formal risk acceptance.
Without action, the organization operates without a tested recovery safety net on affected systems for an indefinite period, increasing both recovery time and potential data loss in the event of any incident during this window.