STATUS_USER_MAPPED_FILE (0XC0000243) fix — memory mapped file error

1. Close the process that has the file memory-mapped

This is the #1 cause I see in the field. Some application—usually a database, editor, or backup tool—opened the file with memory-mapped I/O and never let go. Windows won't let you delete, rename, or modify that file until the mapping is released.

Had a client last month whose entire print queue died because of this—an accounting app memory-mapped a shared database file and locked everyone out. Here's the fix:

1. Open Task Manager (Ctrl+Shift+Esc).
2. Look under the Details tab for the process that originally opened the file—think your IDE, SQL Server, backup software, or a large video editor.
3. Right-click and choose End task.
4. Try your operation again.

If you're not sure which process has the file, use Process Explorer from Sysinternals. Hit Ctrl+F, type the filename, and it shows you exactly which process holds the mapping handle. That tool has saved my bacon more times than I can count.

One more thing: sometimes the process is a background service (svchost.exe or SearchIndexer.exe). If you kill it, it just restarts. In that case, you need to stop the service via services.msc, do your file operation, then restart the service.

2. Clear the Windows file cache (which uses memory mapping)

Windows itself sometimes memory-maps files for caching. If you're getting this error on a file you haven't touched in hours, the system cache is probably holding a stale mapping. This is common on servers with heavy file I/O.

Skip the reboot if you can—just run this from an elevated command prompt:

# Force Windows to flush cached file mappings
# This clears the standby list and releases memory-mapped handles

# Run as Administrator:
net stop wsearch && net start wsearch

That stops and restarts the Windows Search service, which flushes most file cache mappings. If the error persists, run:

# Flush system file cache
# This is the nuclear option—only use if you're stuck

# Open Command Prompt as Admin, then:
C:\Windows\System32\RUNDLL32.EXE C:\Windows\System32\advapi32.dll,ProcessIdleTasks

Wait 30 seconds. That forces Windows to release idle-mapped files. If it still doesn't work, a reboot is your next move—but I've had luck with this trick on many Windows Server 2019 and Windows 10 machines.

3. Disable memory-mapped file usage in the offending application or driver

Some apps give you a setting to turn off memory-mapped I/O. This is rare, but when it's the cause, it's a recurring nightmare. Common culprits:

• Adobe Premiere Pro / After Effects — uses memory-mapped files for project files. Go to Edit > Preferences > Memory and uncheck "Enable memory-mapped file access."
• SQL Server — uses memory-mapped files for tempdb and user databases. Run ALTER DATABASE ... SET MEMORY_OPTIMIZED_DATA = OFF on offending databases.
• Backup software (Veeam, Acronis) — check their settings for "Use memory mapping" or "Enable cached I/O" and turn it off.
• Antivirus real-time scanning — Norton and McAfee have been known to memory-map files during scans. Temporarily disable real-time protection, do your file operation, then re-enable.

If you can't find a setting, check the application's documentation for memory mapped file or file mapping. I once spent three hours on a client's machine only to find a registry key in HKEY_LOCAL_MACHINE\SOFTWARE\SomeApp\FileMapping set to 1. Set it to 0, and the error never returned.

Quick-reference summary table

If none of these work, check if you're running an outdated driver for your storage controller (especially NVMe drives). I've seen the error on a Dell PowerEdge with a bad Intel NVMe driver—updating fixed it. But 90% of the time, it's just a stuck process holding a mapped section open.