STATUS_UNABLE_TO_DELETE_SECTION (0XC000001B) – Quick Fixes

What's Actually Happening Here

The error STATUS_UNABLE_TO_DELETE_SECTION (0XC000001B) means Windows tried to clean up a memory-mapped file section — but something still holds a reference to it. Usually a driver or a background process that didn't release its handle. You'll see this in Event Viewer, or worse, as a BSOD with the same code. The fix is simple: find what's locking the section, and either update it or kill it.

Fix 1: Reboot and Run SFC / DISM (30 seconds)

This is the quickest test. Reboot your machine. If the error doesn't come back, it was a transient lock — a driver held on too long and a restart cleared it. If it does come back, open an admin Command Prompt and run:

sfc /scannow

Then:

DISM /Online /Cleanup-Image /RestoreHealth

The reason step 3 works is: SFC checks system file integrity, and DISM repairs the component store. If the error is caused by a corrupted driver file cached in memory, this wipes that out. Let both finish. Reboot again. If the error stays, move on.

Fix 2: Update or Roll Back Problem Drivers (5 minutes)

The most common real-world trigger for 0xC000001B is a buggy network driver or a storage driver (like Intel RST). What's actually happening: the driver maps a section of memory for DMA or I/O, but when Windows tries to unmount the device or unload the driver, the section still has outstanding I/O. The driver's own unload routine failed to release it.

Open Device Manager. Look for devices with a yellow exclamation — update those first. Then hit View > Show hidden devices. Check these categories:

• Network adapters — especially Realtek, Intel, and Killer drivers. Roll back to a previous version if the error started after an update.
• Storage controllers — Intel RST (Rapid Storage Technology). Disable it in BIOS if you can, or update it.
• System devices — any chipset drivers, especially for AMD or Intel platforms.

For each suspect driver: right-click > Properties > Driver tab > Roll Back Driver if the option is available. If not, download the manufacturer's latest from their site — not Windows Update. Reboot after each change.

Fix 3: Clean Boot and Isolate the Culprit (15+ minutes)

This is the hands-on fix when the error persists. We'll strip down to bare Windows and add things back until the error reappears. Here's the flow:

1. Press Win + R, type msconfig, hit Enter.
2. Go to the Services tab. Check Hide all Microsoft services, then click Disable all.
3. Go to the Startup tab, click Open Task Manager. Disable every startup item.
4. Click OK and reboot. This puts you in a clean boot state — no third-party drivers or services running.

If the error doesn't appear during clean boot, you've confirmed a third-party driver or service is the cause. Now enable services in batches of 5, rebooting each time until the error comes back. When it does, the last batch you enabled holds the offender. Narrow it down one by one.

The reason this works: most drivers load as services. By disabling all non-Microsoft services, you prevent any third-party driver from allocating memory sections. The error won't trigger because the bad driver never starts. Once you find it, update or uninstall that specific driver.

Fix 4: Check for Corrupt Page File or Virtual Memory Settings (10 minutes)

Less common, but I've seen 0xC000001B from a corrupted page file. The system tries to delete a section backed by the page file, but the file itself is damaged. Here's how to reset it:

1. Open System Properties (right-click This PC > Properties > Advanced system settings).
2. Under Performance, click Settings > Advanced tab.
3. Under Virtual memory, click Change.
4. Uncheck Automatically manage paging file size.
5. Select No paging file, click Set. Reboot.
6. Go back and re-enable System managed size. Reboot again.

This deletes and recreates the page file fresh. If the error was from a corrupted page file entry, it's gone.

Fix 5: Check Memory Integrity and Driver Signing (advanced, 15 minutes)

Windows 10 and 11 have a feature called Memory Integrity (part of Core Isolation). It can flag unsigned drivers that try to map memory sections. When a driver fails the integrity check, Windows can't unload it cleanly, leading to 0xC000001B. To check:

1. Open Windows Security > Device Security > Core Isolation.
2. If Memory Integrity is On, try turning it Off and reboot. Test if the error stops.
3. If it does, you have an incompatible driver. Turn Memory Integrity back On (you should). Then check Event Viewer under Windows Logs > System for events with source CodeIntegrity or DriverFault. That will name the exact driver file causing the problem.

The reason step 3 matters: Memory Integrity blocks unsigned drivers from running. But if a driver was loaded before you turned it on, or if the driver is signed but violates policy, Windows can't cleanly remove its memory sections. The error log tells you which .sys file to update or remove.

When to Give Up and Reinstall

If you've tried all five fixes and the error still appears on every boot, you're looking at deeper corruption — maybe the registry hive for a driver is hosed, or the system image itself is damaged. At that point, a repair install (keep files) or a clean install is faster than digging further. Back up your data, download the Media Creation Tool, and choose Upgrade this PC now to do an in-place repair. It replaces all system files while keeping your apps and documents.

But in 90% of the cases I've debugged, Fix 2 (driver update) or Fix 3 (clean boot isolation) found the problem. Start there.