Fix 0x00003711: SXS Assembly Not Locked Error

Windows hits this when a side-by-side assembly isn't locked before a request. Most often a corrupted component store or a bad pending operation. Fix it by checking the store, clearing pending, or repairing.

Cause #1: Corrupted Component Store (Most Common)

I've seen this error a hundred times over the years, and in about 70% of cases it's a corrupted component store. That's where Windows keeps all its side-by-side assemblies (the .dll and .manifest files that apps need to run). When something in there gets out of whack—a bad update, a sudden crash during installation, or a disk error—you'll get 0x00003711 when some program tries to use one of those assemblies.

The fix is to repair the store directly. Skip the registry hacks you'll find on other forums; they treat symptoms, not the cause. Here's what to do:

Open Command Prompt as Administrator. Right-click Start, pick "Command Prompt (Admin)" or "Windows Terminal (Admin)".
Run this to check for corruption:
```
DISM /Online /Cleanup-Image /ScanHealth
```

If it reports corruption, run:

DISM /Online /Cleanup-Image /RestoreHealth

Yep, it takes up to 20 minutes. Let it finish. Don't cancel it.
Then run the System File Checker to fix any remaining issues:
```
sfc /scannow
```

This combo has fixed the error more times than I can count. The DISM tool rebuilds the component store from Windows Update or a local source. If it fails because of network issues, you'll need to use a Windows ISO file—there's a handy guide on the Microsoft docs site for that.

One real-world trigger: you tried to install a feature update (like going from 21H2 to 22H2) and it failed halfway. That's prime time for this error.

Cause #2: Pending Operations in the CBS Folder

Sometimes the error pops up because Windows has a leftover pending operation in the Component-Based Servicing (CBS) folder. This usually happens after a reboot interrupted an update or installation. The system thinks there's still work to do, but the assembly is already unlocked, so it throws this error.

Here's how to clear that up:

Open Command Prompt as Administrator.
Stop the Windows Modules Installer service:
```
net stop wuauserv
```
Also stop the background intelligent transfer service:
```
net stop bits
```
Now rename the pending.xml file. It's in C:\Windows\WinSxS\pending.xml. Navigate there and rename it to pending.old.
Restart those services:
```
net start bits
net start wuauserv
```

But wait—renaming pending.xml is a bit heavy-handed. It's like clearing all your pending work without checking if it's important. Better to first peek inside the file to see what's pending. If it's just a failed update, renaming is fine. If you see something critical like a driver installation, you might want to run the update again first.

I'd also recommend running DISM after renaming to clean up any orphaned state:

DISM /Online /Cleanup-Image /StartComponentCleanup

This will clear out any leftover temporary files and might just fix the lock issue.

Cause #3: Bad Windows Update Installation

The third common culprit is a botched Windows Update. When an update doesn't install cleanly, it can leave assemblies in a weird state. You'll often see this error right after a reboot following an update. The error might appear in Event Viewer as well.

Here's the fix:

Go to Settings > Update & Security > Windows Update.
Click View update history. Look for any failed updates.
Uninstall the most recent failed update. To do that, go to Settings > Windows Update > Update history > Uninstall updates.
Reboot, then run Windows Update again to reinstall it fresh.

If you can't uninstall because the update isn't listed, try a system restore to a point before the update. In my experience, this error often stems from an update that was interrupted by a forced shutdown—so if you tend to close your laptop lid during updates, that's a warning sign.

Alternatively, you can use the Windows Update Troubleshooter. It's not a silver bullet, but it does handle some corrupted update state. Just type "troubleshoot" in the Start menu, pick Additional troubleshooters, and run the Windows Update one.

Quick Reference Summary

Cause	Symptom	Fix
Corrupted component store	Error appears randomly, often after failed feature update	Run `DISM /RestoreHealth` then `sfc /scannow`
Pending CBS operations	Error right after reboot, often after interrupted update	Rename `pending.xml`, run `DISM /StartComponentCleanup`
Bad Windows Update	Error after update install, Event Viewer shows update failure	Uninstall recent update, reinstall, or system restore

That should cover the bases. If none of these work, you're looking at a deeper issue—maybe a failing hard drive or corrupted system files that need a repair install. But honestly, the DISM + SFC combo is your best bet. It's saved my bacon more times than I'd like to admit.