Windows April Update KB5083769: When Patches Break Things

If your Windows 11 machines have been playing up since mid-April, you’re not alone. Microsoft’s April 2026 security update, KB5083769, released on Patch Tuesday 14 April, is causing genuine problems across managed fleets. We’re talking frozen Outlook inboxes, silent backup failures, and network browsing that simply stops working.

IT teams and managed service providers have flagged issues affecting a noticeable slice of Windows 11 24H2 and 25H2 systems. The patch was meant to fix security vulnerabilities and improve reliability. Instead, it’s introduced a cluster of faults that have left some businesses without working email, broken backups, and no visibility of their shared network drives.

What’s going wrong?

The problems started appearing almost immediately after the update deployed. Here’s what’s being reported:

• Outlook stops receiving email. Inboxes freeze across all accounts with no error shown. Restarting Outlook clears the backlog temporarily, but it comes back.
• Backup jobs fail silently. Third-party backup tools are hitting VSS (Volume Shadow Copy Service) timeouts and leaving incomplete snapshots behind.
• Network Discovery breaks. File Explorer hangs indefinitely when trying to browse shared network resources.
• DISM errors. System repair operations fail with error 0x800f0915, even on machines with a perfectly healthy internet connection.
• Hard freezes and boot loops. Some systems lock up during idle periods or restart in a loop that prevents normal use. The root cause appears to be changes Microsoft made to how Windows handles SMB compression over QUIC, a networking protocol used to make file transfers faster. The update inadvertently causes persistent network connections to stall silently after the initial handshake. Services that depend on those stable connections, including Outlook, backup agents, and network browsing, all break when the underlying connection times out. Microsoft has acknowledged the issue but has not yet released an emergency fix.

What can you do?

If KB5083769 hasn’t deployed yet: Test it on a single pilot machine before rolling it out. A staged deployment is always sensible, especially when a patch touches backup and system-update tools.

If you’re affected and within the 10-day automatic rollback window: Uninstall the patch via Settings > Windows Update > Update history > Uninstall updates. Reboot, then pause Windows updates to stop it downloading again automatically. Email, backups, and network browsing should return to normal.

If you’re past the 10-day window: Options are more limited. Some users have had partial success disabling the Background Intelligent Transfer Service (BITS) as a short-term workaround, though it’s not a permanent fix. A clean Windows reinstall using current media (keeping your files) is the documented recovery path, but that’s disruptive. Microsoft is expected to release a fix in the coming weeks.

For businesses using a managed IT service: Your provider should be pausing automatic rollout to any remaining machines, inventorying affected systems, validating BitLocker recovery keys, and confirming that backups are restorable before taking further action. If you’re not sure whether your setup is covered, it’s worth checking what your managed IT support arrangement actually includes.

Windows updates are essential for keeping your systems secure, and we’d never suggest skipping them as a rule. But this month’s release is a good reminder that timing and testing matter. If your business in Wrexham, Bangor, Llandudno, or anywhere across North Wales has been caught out by this update and you need a hand sorting it, get in touch with us at Dragon Digital and we’ll get it handled.