How to Fix COM Surrogate Process Issues and What COM Surrogate Is

COM Surrogate is a normal Windows process, not a virus by itself. Windows uses it to host certain COM components outside the app that requested them, so a faulty component can fail without necessarily taking the main app down with it. The process is commonly associated with dllhost.exe, and seeing more than one COM Surrogate instance in Task Manager can be normal.

If COM Surrogate repeatedly crashes, uses unusually high CPU, or makes File Explorer freeze while opening folders, the real cause is often a thumbnail handler, media component, third-party shell extension, damaged file, corrupted cache, or a Windows component problem. The fixes below focus on finding that cause instead of disabling COM Surrogate.

What is COM Surrogate?

COM stands for Component Object Model, a Windows technology that lets software components work with one another. Microsoft documents a system-supplied DLL surrogate that can load DLL-based COM servers in a separate process. One important benefit is fault isolation: if the hosted component crashes, the calling application has a better chance of staying open. See Microsoft's DLL Surrogates documentation for the underlying design.

How to fix COM Surrogate problems

1. End a stuck COM Surrogate process, then retry

Press Ctrl + Shift + Esc to open Task Manager. Under Processes, select a COM Surrogate instance that is clearly stuck or consuming resources and choose End task. Then reopen the folder or app that triggered the issue. Windows can start another surrogate when it is needed.

Do not repeatedly terminate every instance as routine maintenance. Ending the process only resets the symptom; if the problem returns, continue with the checks below.

2. Test thumbnails and rebuild the thumbnail cache

COM Surrogate problems often show up while File Explorer is generating previews for photos, videos, PDFs, or other files. As a diagnostic step, open File Explorer, choose ... > Options, open the View tab, and enable Always show icons, never thumbnails. On Windows 10, Folder Options is available from File Explorer's View ribbon.

If File Explorer stops crashing with thumbnails disabled, clear the thumbnail cache. Search Windows for Disk Cleanup, select the Windows drive, check Thumbnails, and run the cleanup. Microsoft confirms that Disk Cleanup can remove the thumbnail cache in its drive-space cleanup guidance. Re-enable thumbnails afterward and test the folder again.

3. Find the file or component that dllhost.exe is touching

When the crash is tied to one folder or file type, use Microsoft's free Sysinternals Process Monitor. Add a filter for Process Name is dllhost.exe, reproduce the problem, and inspect the file-system activity immediately before the error.

If the same media file is repeatedly accessed just before the crash, move that file out of the folder and test again. If Process Monitor points to a third-party program folder or codec, update, repair, or remove that software from its official installer. Do not delete Windows DLLs or unfamiliar system files just because they appear in the trace.

4. Scan for malware instead of whitelisting COM Surrogate

Because legitimate Windows processes can be imitated by malware, run a security scan if the behavior is unusual or the executable looks suspicious. Open Windows Security > Virus & threat protection and run a Quick scan; use Full scan or Microsoft Defender Offline when a deeper check is warranted. Microsoft's Windows Security guidance explains the available scan options.

Avoid adding a blanket antivirus exclusion for COM Surrogate or turning off protection as a general fix. If a third-party security product is blocking a legitimate component, review its detection history, update the product, and follow the vendor's instructions for that specific detection.

5. Repair Windows system files if the issue is system-wide

If COM Surrogate errors occur across many folders and apps, repair the Windows component store and protected system files. Open Command Prompt as administrator and run these commands in order:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Microsoft recommends running DISM before System File Checker because DISM supplies files that SFC can use for repair. Full instructions and result messages are in Microsoft's System File Checker documentation.

What you should not do

• Do not delete or permanently disable dllhost.exe. COM Surrogate is part of Windows' normal component-hosting mechanism.
• Do not install random codec packs. If a particular format triggers the problem, prefer updates from the app, device, or codec vendor you already use.
• Do not delete a problem file solely from a trace. Move or copy it first, confirm the behavior changes, and keep backups of important data.

In most cases, COM Surrogate itself is only the host. The lasting fix is to identify the thumbnail provider, file, codec, shell extension, security conflict, or damaged Windows component that is causing the surrogate to fail.