COM Surrogate Delete File Error: 14 Fixes for “File Is Open in COM Surrogate” (Windows 11/10)

Quick FIX: For the “file is open in COM Surrogate” error, open Task Manager (Ctrl+Shift+Esc), go to the Details tab, find dllhost.exe, right-click it, and select End task. End all dllhost.exe instances if multiple exist. Retry deleting the file. Windows restarts COM Surrogate automatically. If the error returns, clear the thumbnail cache or disable the Preview Pane in File Explorer.

You right-click a file to delete it and Windows stops you cold: “The action cannot be completed because the file is open in COM Surrogate.” The file is not open in any visible app. No window has it. No program is using it. But Windows refuses to let you touch it. COM Surrogate, the process running as dllhost.exe in Task Manager, is holding a hidden lock on the file while generating its thumbnail preview.

That lock is why you cannot delete it. This guide covers 14 confirmed methods to break that lock, explains exactly what COM Surrogate is and why it grabs files, maps which file types trigger this most often, and includes a security check to confirm your dllhost.exe is not malware.

Also Read: Destiny 2 Cabbage Error Fix

What Causes the “File Is Open in COM Surrogate” Error?

The error occurs when dllhost.exe holds an open file handle on a file you are trying to delete, move, rename, or copy. Before trying any fix, identify which cause matches your situation.

#	Cause	What Happens
1	Thumbnail generation stuck	COM Surrogate stalls while generating a preview for a large image or video and holds the file open indefinitely
2	Corrupted thumbnail cache	Corrupted thumbs.db causes COM Surrogate to retry and fail on the same file repeatedly without releasing the lock
3	Third-party codec pack	K-Lite, Shark007, or CCCP codec handlers run in COM Surrogate and hang when processing certain video formats
4	Antivirus interference	Kaspersky, Bitdefender, or McAfee intercepts COM Surrogate’s file access and leaves the handle in a locked state
5	Preview Pane active	File Explorer’s Preview Pane holds a file handle for the duration of any active file preview
6	Cloud sync tool	OneDrive, Dropbox, or Google Drive shell extensions run through COM Surrogate during active sync operations
7	Outdated graphics driver	COM Surrogate fails during hardware-accelerated thumbnail rendering and leaves the file stuck
8	Orphaned registry key	A file extension’s thumbnail handler points to a DLL that no longer exists; COM Surrogate loads, fails, and holds the lock
9	File Explorer glitch during bulk operations	Large copy or move operations leave dllhost.exe holding file handles after the operation visually completes
10	Low system resources	CPU at 100% or critically low RAM causes COM Surrogate to freeze mid-process without releasing file handles

The most common cause by far is thumbnail generation. When you browse a folder containing large images or videos, Windows generates thumbnail previews using COM Surrogate. If you try to delete any of those files during that process, you will immediately hit this error.

What Is COM Surrogate (dllhost.exe) and Why Does It Hold Files?

COM Surrogate is a legitimate Windows system process. It is not malware. It is not optional. It has been part of Windows since Vista and runs as dllhost.exe in Task Manager.

COM stands for Component Object Model. COM is the Windows framework that allows software components from different applications to communicate with each other. When a program needs to run a COM object (such as a thumbnail generator or a file preview handler), Windows can run that COM object inside the program’s own process or inside a separate “surrogate” process.

The surrogate approach is intentional. If a thumbnail generator crashes while running inside Windows Explorer’s own process, the crash takes down Explorer and your entire desktop. By running the same thumbnail generator inside a separate dllhost.exe surrogate process, Windows isolates the crash. If the thumbnail generator fails, only dllhost.exe dies. Explorer survives. This is the sacrificial process design pattern.

What COM Surrogate does every time you browse a folder:

• Generates thumbnail previews for .jpg, .png, .heic, .mp4, .avi, .mkv, .pdf, and other file types
• Handles file previews in the File Explorer Preview Pane
• Hosts third-party shell extensions including codec pack handlers, cloud sync overlays, and archive previewer plugins

The legitimate dllhost.exe always lives at:

C:\Windows\System32\dllhost.exe

Any dllhost.exe found outside that exact path is suspicious. Seeing multiple dllhost.exe entries in Task Manager is completely normal. Each COM object running out-of-process gets its own isolated dllhost.exe instance.

Which File Types Trigger the COM Surrogate Lock?

Not every file type triggers this error. COM Surrogate locks files when it needs to generate a thumbnail or run a preview handler for that specific format. The table below maps the most common triggers.

File Type	Extension	Why It Triggers COM Surrogate
JPEG image	.jpg .jpeg	Thumbnail generation via Windows Imaging Component
PNG image	.png	Thumbnail generation via Windows Imaging Component
HEIC image	.heic	iPhone photos; HEIC codec triggers a COM Surrogate handler on Windows 11
MP4 video	.mp4	Video thumbnail needs a codec; third-party codecs run inside COM Surrogate
AVI video	.avi	Older format; more likely to use a third-party codec handler
MKV video	.mkv	Requires a third-party codec handler; Shark007 and K-Lite are common triggers
PDF document	.pdf	Requires a PDF preview handler (Adobe Acrobat, Foxit, or Windows built-in)
MOV video	.mov	Apple QuickTime format; may use a third-party handler on Windows

If the error consistently affects .heic files, you recently synced iPhone photos and the HEIC codec handler is getting stuck. If it consistently affects .mkv or .avi files, a third-party codec pack is the most likely culprit.

Method 1: End COM Surrogate in Task Manager (Fix It Now)

This single method resolves the COM Surrogate delete file error in approximately 90% of cases in under 60 seconds. Windows restarts dllhost.exe automatically after you end it, so this is completely safe.

Via the Processes tab (quickest):

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Click the Processes tab.
3. Scroll down to find “COM Surrogate” in the list.
4. Right-click each COM Surrogate entry and select End task.
5. End all COM Surrogate instances if multiple appear.
6. Close Task Manager and retry deleting the file.

Via the Details tab (more precise):

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Click the Details tab at the top.
3. Find dllhost.exe in the alphabetically sorted list.
4. Right-click dllhost.exe and select End task.
5. Confirm if prompted.
6. If multiple dllhost.exe processes are listed, end every one.
7. Retry the delete, move, or rename operation.

After ending COM Surrogate, thumbnail previews in File Explorer may temporarily disappear. Windows regenerates them automatically as you browse. No damage occurs to any files or Windows components.

Tip: If the COM Surrogate delete file error returns the next time you browse the same folder, the problem is a corrupted thumbnail cache or a stuck codec handler, not a one-time glitch. Method 5 (clear thumbnail cache) or Method 8 (update codec packs) provides a permanent fix after Method 1 releases the file for immediate deletion.

Method 2: Restart Windows Explorer

Restarting Windows Explorer terminates all COM Surrogate instances associated with that Explorer session and resets the entire file handle table. This is useful when Method 1 releases the lock but the error reappears immediately.

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Click the Processes tab.
3. Find Windows Explorer in the list.
4. Right-click Windows Explorer and select Restart.
5. The taskbar and desktop briefly disappear and reappear.
6. Retry the file operation.

Method 3: Use PowerToys File Locksmith (Identify the Exact Lock)

PowerToys File Locksmith shows precisely which process holds a lock on a specific file instead of requiring you to guess and end all dllhost.exe instances. This is more accurate than Task Manager when multiple processes might be competing for the same file.

1. Open a browser and go to aka.ms/getpowertoys to download PowerToys from the Microsoft Store.
2. Install PowerToys and open it from the Start menu.
3. In the PowerToys left sidebar, click File Locksmith.
4. Toggle File Locksmith to On.
5. Open File Explorer and navigate to the locked file.
6. Right-click the file and select “What’s using this file?”
7. File Locksmith opens and lists every process currently holding the file.
8. If dllhost.exe (COM Surrogate) appears in the list, click End Task directly from within the File Locksmith window.

File Locksmith works on individual files, entire folders, and multiple selected files simultaneously. For users who regularly work with large media folders and encounter this error, enabling File Locksmith once and leaving it on provides a permanent right-click shortcut to identify and release any file lock.

When Windows Update delivers a new build and COM Surrogate starts behaving differently, the AxeeTech guide on how to fix Windows Update issues easily covers every repair step for update-related system behavior changes.

Methods 4-7: Disable or Reset Thumbnail Generation (Permanent Fixes)

These four methods address the root cause rather than the symptom. They prevent COM Surrogate from generating thumbnails in ways that lock files.

Method 4: Switch to Details View and Disable Preview Pane

1. Open File Explorer and navigate to the folder containing the locked file.
2. Click View in the toolbar.
3. Select Details to switch from thumbnail grid to a text list.
4. Click View in the toolbar again.
5. Click Show, then click Preview pane to uncheck it.
6. Retry the file operation.

Switching to Details view stops Explorer from requesting thumbnail generation entirely. No thumbnail request means no COM Surrogate file lock.

Method 5: Clear Thumbnail Cache via Disk Cleanup

1. Press Win+S, type Disk Cleanup, and open the utility.
2. Select the C: drive if prompted.
3. In the file list, scroll down and check the box next to Thumbnails.
4. Uncheck all other boxes to avoid unwanted deletions.
5. Click OK and then confirm with Delete Files.

A corrupted thumbnail database is one of the most common causes of recurring COM Surrogate errors. Clearing it forces Windows to rebuild the cache cleanly.

Method 6: Disable Thumbnails via Folder Options

1. Press Win+E to open File Explorer.
2. Click the three-dot menu at the top right of File Explorer.
3. Select Options.
4. Click the View tab in the Folder Options dialog.
5. Check the box for “Always show icons, never thumbnails.”
6. Click Apply and then OK.

This setting prevents Explorer from generating thumbnails in any folder on the PC.

Method 7: Disable Thumbnail Cache via Registry

For a system-wide setting that survives profile resets and major updates:

1. Press Win+R, type regedit, and press Enter.
2. Navigate to this exact path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced

3. Right-click an empty area in the right pane.
4. Select New > DWORD (32-bit) Value.
5. Name the new value DisableThumbnailCache.
6. Double-click DisableThumbnailCache and set the value data to 1.
7. Click OK.
8. Open Task Manager, find Windows Explorer, right-click it, and select Restart.

Warning: Always back up the registry before editing it. Open Registry Editor, click File, then Export, and save a backup file before making any changes. Incorrect registry edits can cause system instability.

Other Windows display-related settings sometimes need adjustment alongside graphics driver updates when COM Surrogate rendering failures are involved. The AxeeTech guide on adjusting display brightness automatically in Windows covers the related display configuration settings that share the same graphics driver dependency.

Methods 8-9: Fix Codec and Antivirus Conflicts

Third-party codec packs and antivirus software are two of the most persistent causes of the COM Surrogate delete file error when it affects video files specifically.

Method 8: Update or Remove Third-Party Codec Packs

1. Press Win+I to open Settings.
2. Click Apps, then Installed apps.
3. Type codec in the search box at the top of the apps list.
4. If K-Lite Codec Pack, Shark007, CCCP (Combined Community Codec Pack), or any other third-party codec pack appears, click it and select Update or Uninstall.
5. After removing or updating, download and install VLC Media Player as a replacement.

VLC handles its own codec processing internally without registering shell extensions that run through COM Surrogate. Installing VLC eliminates the third-party codec handler that was triggering the lock on .mkv, .avi, and .mp4 files.

Method 9: Add dllhost.exe to Antivirus Exclusions

When Kaspersky, Bitdefender, McAfee, or another antivirus intercepts COM Surrogate’s file access, the file handle gets caught between the two processes and remains locked.

1. Open your antivirus software.
2. Navigate to Settings, then Exclusions or Exceptions (the menu name varies by software).
3. Add the following path to the exclusion list:

C:\Windows\System32\dllhost.exe

4. Save the changes.
5. Retry the file operation.

This tells the antivirus to allow COM Surrogate to access files without interception. The exclusion applies only to the legitimate system binary at that exact path.

For other Windows privacy and security permission issues that antivirus software sometimes triggers alongside COM Surrogate conflicts, the AxeeTech guide on troubleshooting microphone privacy settings covers the Windows Privacy and security framework that governs all hardware and software permissions simultaneously.

Methods 10-14: Advanced and Last-Resort Fixes

These methods are for recurring errors that Methods 1-9 have not permanently resolved, or for files that remain stubbornly locked despite all standard approaches.

Method 10: Use Process Explorer to Identify the Specific Handle

Process Explorer from Microsoft Sysinternals provides deeper file handle analysis than Task Manager and identifies the exact handle COM Surrogate holds on a specific file.

1. Download Process Explorer from live.sysinternals.com/procexp.exe.
2. Right-click the downloaded file and select Run as administrator.
3. Press Ctrl+F inside Process Explorer to open Find Handle or DLL.
4. Type the full path of the locked file in the search box.
5. Process Explorer identifies every process holding that file, including the specific dllhost.exe instance.
6. End the specific dllhost.exe process from Process Explorer or close the individual handle.

Optional security check: Right-click any dllhost.exe entry in Process Explorer and select Check VirusTotal. Process Explorer sends the process hash to VirusTotal and displays the detection result directly. This confirms the process is genuine Microsoft software with zero flags.

Method 11: Delete via Command Prompt or PowerShell

Bypassing File Explorer entirely removes the trigger for COM Surrogate thumbnail generation. Command Prompt and PowerShell can delete locked files when Explorer-based deletion fails.

Open Command Prompt as administrator (right-click Start > Terminal (Admin)):

cmd

del /f "C:\full\path\to\your\file.ext"

Or open PowerShell as administrator:

powershell

Remove-Item "C:\full\path\to\your\file.ext" -Force

Replace the path with the actual full path and filename of the locked file. The /f flag in del and the -Force flag in Remove-Item override the standard file-in-use protection.

Method 12: Run SFC and DISM for Recurring Errors

If the COM Surrogate delete file error occurs repeatedly on many different files and no single cause appears in Task Manager, corrupted Windows system files may be responsible. Run these in an elevated Command Prompt or Terminal (Admin):

System File Checker (runs offline, no internet required):

cmd

sfc /scannow

If SFC reports files it cannot repair, follow up with DISM (requires internet):

cmd

DISM /Online /Cleanup-Image /RestoreHealth

Run SFC again after DISM completes to confirm all repairs succeeded. Before attempting these commands, the AxeeTech Windows troubleshooter guide covers the automated diagnostic tools that identify the root cause of recurring system errors before any manual command is needed.

If Windows enters a self-repair loop after running SFC or DISM, the AxeeTech guide on what to do when your system is repairing itself explains each phase of the Windows repair process and when it is safe to intervene.

Method 13: Use Unlocker or IObit Unlocker

Third-party file unlock tools inject directly into the Windows process table to force-release file handles.

Unlocker is a classic free tool that adds a right-click context menu option. IObit Unlocker at iobit.com is the actively maintained 2026 alternative with the same right-click integration and a cleaner interface. Both show which processes hold the file and offer a one-click unlock button.

Use either tool as a last resort when all built-in Windows methods have failed.

Method 14: Boot into Safe Mode and Delete

Safe Mode loads Windows with only essential system services. COM Surrogate does not perform thumbnail generation in Safe Mode because Explorer loads in a minimal configuration.

1. Hold Shift on the keyboard while clicking Restart from the Start menu.
2. In the recovery menu, choose Troubleshoot.
3. Choose Advanced options.
4. Choose Startup Settings.
5. Click Restart.
6. When the Startup Settings menu appears, press 4 to enter Safe Mode.
7. Navigate to the file in File Explorer and delete it normally.

Is dllhost.exe (COM Surrogate) a Virus? How to Check

COM Surrogate is a legitimate Windows system process. However, malware sometimes impersonates dllhost.exe by using the same filename. Knowing how to verify the difference takes under two minutes.

The genuine dllhost.exe always lives at exactly this path:

C:\Windows\System32\dllhost.exe

Step 1: Verify the file location via Task Manager

1. Open Task Manager (Ctrl+Shift+Esc).
2. Click the Details tab.
3. Find dllhost.exe in the list.
4. Right-click it and select Open file location.
5. If File Explorer opens to C:\Windows\System32, the process is legitimate.
6. If it opens to any other location (Desktop, Downloads, AppData, Temp), the process is suspicious.

Step 2: Verify the digital signature

1. Open File Explorer and navigate to C:\Windows\System32.
2. Find dllhost.exe.
3. Right-click dllhost.exe and select Properties.
4. Click the Digital Signatures tab.
5. The Signer column should show “Microsoft Windows.”

Step 3: Use Process Explorer for instant VirusTotal verification

1. Open Process Explorer (downloaded from live.sysinternals.com).
2. Find the dllhost.exe process.
3. Right-click it and select Check VirusTotal.
4. A detection ratio appears. 0 detections confirms the process is clean.

Warning: If Task Manager’s Open file location opens any folder other than C:\Windows\System32, do not simply end the process. Run Windows Defender Full Scan immediately by opening Windows Security and selecting Full Scan. Then run a second-opinion scan with Malwarebytes (free at malwarebytes.com) to identify and remove the malicious process before taking any other action.

Signs that a dllhost.exe may be malicious:

• Located outside C:\Windows\System32
• Sustained CPU usage consistently above 50% for more than several minutes
• No digital signature or a signature from an unknown publisher
• Process name appears as “dllhost” or “DLLhost” with unusual capitalization

How to Prevent COM Surrogate File Errors

These seven practices reduce the frequency of COM Surrogate file locks to near zero for most users.

1. Keep codec packs updated or replace them with VLC. K-Lite, Shark007, and CCCP are the most common persistent causes for video files. VLC handles its own codecs without registering COM Surrogate handlers.
2. Use Details view in folders with large media files. Details view does not request thumbnail generation. Switching to Details view before bulk file operations prevents COM Surrogate from locking files during the operation.
3. Turn off the Preview Pane when working with large batches. The Preview Pane opens a file handle the moment you click a file. Disabling it at View > Show > Preview pane removes that lock source entirely.
4. Clear the thumbnail cache monthly. Run Disk Cleanup, check Thumbnails, and delete. This removes corrupted cache entries before they cause recurring errors.
5. Keep graphics drivers updated. Use GeForce Experience (NVIDIA), AMD Software (AMD), or Device Manager for Intel graphics. Outdated drivers cause COM Surrogate to fail during hardware-accelerated thumbnail rendering.
6. Keep antivirus software updated. Outdated definitions increase the likelihood of COM Surrogate’s file access being misidentified as suspicious and intercepted.
7. Avoid bulk delete or move operations while the address bar loading indicator is still spinning. That spinner means Explorer is actively generating thumbnails via COM Surrogate. Starting a bulk delete at that moment triggers file lock errors on whichever files COM Surrogate currently holds.

Frequently Asked Questions

What is COM Surrogate and why does it lock my files?

COM Surrogate is a legitimate Windows process (dllhost.exe) that runs COM objects including thumbnail generators and file preview handlers in an isolated process space away from Windows Explorer. When you browse a folder, COM Surrogate generates thumbnail previews for image and video files. It holds those files open during that process. If you try to delete a file while COM Surrogate still has a handle on it, Windows blocks the operation with the “file is open in COM Surrogate” error message.

How do I delete a file that is open in COM Surrogate?

Open Task Manager with Ctrl+Shift+Esc, click the Details tab, find dllhost.exe, right-click it, and select End task. End all dllhost.exe instances if more than one exists. Close Task Manager and retry deleting the file. Windows restarts COM Surrogate automatically so thumbnails resume generating. If the error returns on the same folder, clear the thumbnail cache via Disk Cleanup or switch to Details view to prevent thumbnail generation.

Is dllhost.exe (COM Surrogate) a virus?

In most cases, no. The legitimate dllhost.exe always lives at C:\Windows\System32\dllhost.exe. To verify, right-click the process in Task Manager’s Details tab and select Open file location. If File Explorer opens to C:\Windows\System32, the process is genuine. Also check the Digital Signatures tab in dllhost.exe properties — it should show “Microsoft Windows” as the signer. If the file location is anywhere else, run Windows Defender Full Scan and Malwarebytes immediately.

Why does COM Surrogate keep coming back after I end it?

COM Surrogate restarts automatically because Windows needs it to generate thumbnails for the files in the current folder. Ending it stops the error for the moment, but browsing back to that folder restarts the thumbnail process and the lock reappears. For a permanent fix, clear the thumbnail cache (Method 5), switch to Details view (Method 4), or remove the third-party codec causing the hang (Method 8). The recurring error points to a specific cause such as a corrupted cache or a stuck codec handler, not a one-time system glitch.

How do I use PowerToys File Locksmith to unlock a file?

Download PowerToys from aka.ms/getpowertoys and install it. Open PowerToys settings, click File Locksmith in the left sidebar, and toggle it to On. Open File Explorer, right-click the locked file, and select “What’s using this file?” File Locksmith opens and lists every process holding the file with an End Task button next to each. Click End Task next to any dllhost.exe entry to release the lock without opening Task Manager.

Which file types most commonly cause the COM Surrogate lock error?

The most common triggers are .mp4, .avi, and .mkv video files (because they need codec handlers that run in COM Surrogate), .heic image files from iPhones (because the HEIC codec handler runs in COM Surrogate on Windows 11), .jpg and .png images (because the Windows Imaging Component generates thumbnails via COM Surrogate), and .pdf files (because PDF preview handlers run in COM Surrogate when a PDF viewer is installed).

Can I permanently disable COM Surrogate?

You cannot permanently disable COM Surrogate because Windows runs many critical COM objects through it. However, you can prevent it from locking files by disabling thumbnail generation entirely via Folder Options (“Always show icons, never thumbnails”), setting the DisableThumbnailCache DWORD to 1 in the registry, or removing the specific codec or preview handler that is causing the hang. These approaches eliminate the file lock behavior while leaving COM Surrogate available for the other COM tasks it performs.

How do I fix COM Surrogate file errors caused by codec packs?

Open Settings > Apps > Installed apps and search for “codec.” Update or uninstall K-Lite Codec Pack, Shark007, or CCCP if any appear. These codec packs register thumbnail handlers that run inside COM Surrogate. If they are outdated or buggy, they hang during video file processing and lock the file. After removing the codec pack, install VLC Media Player. VLC handles its own codec processing internally and does not register COM Surrogate handlers for file thumbnails.

What is the fastest fix for the COM Surrogate delete file error?

The fastest fix is ending dllhost.exe in Task Manager’s Details tab. Press Ctrl+Shift+Esc, click Details, find dllhost.exe, right-click it, select End task, and end all instances. The entire process takes under 30 seconds. Windows restarts COM Surrogate automatically and your file becomes available for deletion immediately. This single method resolves the error in the majority of cases without requiring any settings changes or downloads.

Why does COM Surrogate lock PDF files specifically?

COM Surrogate locks PDF files because a PDF preview handler runs inside it to generate thumbnails and Preview Pane content. When Adobe Acrobat Reader, Foxit PDF Reader, or Windows’ own PDF handler is installed, it registers a COM object that Windows runs through a dllhost.exe surrogate when you browse folders containing PDFs. If that handler stalls during preview generation (particularly for large or complex PDFs), it holds the file open. Switching to Details view or disabling the Preview Pane removes the trigger. Updating the PDF reader software resolves the handler hang.