I know I am not alone as this is a widespread Windows 11 bug where a Windows Update corrupts the core SMB components, and then subsequent updates cheerfully re-break what I just fixed.
TL;DR: Windows Update broke SMB. Go to Settings → System → Recovery → “Fix problems using Windows Update” to force a repair install. Then pause updates before they can break it again.
After wasting days on tweaks, sfc /scannow, DISM, registry hacks, service resets, NewSID workaround, I found the only solution that actually sticks, and it comes from Microsoft itself. Ironically, it’s also delivered via Windows Update.
The Nuclear Option That Works
Around 2022 or later, Microsoft has quietly added a “Repair Install” button that forces Windows to replace itself with a clean copy, while keeping your files, apps, and most settings intact.
- Go to Start → Settings → System → Recovery. (Wait, be noted that it is not the same "recovery" that came from control panel, perhaps that's why we ignored it easily...)
- Under Recovery options, click “Fix problems using Windows Update” (or “Reinstall Windows while keeping your files and apps”).
Follow the prompts. It will download a clean system image (≈30 mins) and reinstall Windows (≈20 mins) with a couple of reboots.
Why this works: It replaces the corrupted SMB drivers (mrxsmb.sys, srv.sys) and service configurations that sfc and DISM often miss.
How to Prevent It From Happening Again
Since we now know the culprit is a rogue update, it is wise to do these immediately after the repair:
- Create a System Restore Point right now (
sysdm.cpl → System Protection → Create). Name it “Post-SMB-Repair” or "Recovery-from-SMB-Hell".
- Pause Updates for at least 2-4 weeks (Settings → Windows Update → Pause updates).
If the problem dares return, you’ll know exactly which update is to blame. Use the Show/Hide Updates Tool to block that specific offender indefinitely.
It’s a special kind of poetic justice that the fix for a Windows Update breakage is… another Windows Update. The left hand breaks, the right hand offers a bandage, but only if you know where to look.
This method finally gave me a stable SMB stack after months of frustration. Hope it helps you reclaim your network shares without having to perform ritualistic sacrifices.