Skip to main content

COM Surrogate (dllhost.exe): what it is, and how to fix crashes and high CPU

Short answer

COM Surrogate (dllhost.exe) is a genuine Windows process that runs plug-ins, such as the codecs Explorer uses for thumbnails, away from Explorer so a crash doesn't take it down. When it crashes or eats CPU, a plug-in is usually to blame. Find it in Reliability Monitor, then update or remove it.

On this page

COM Surrogate (dllhost.exe) is a genuine Windows process that runs other programs’ small plug-ins, such as the codecs and add-ons File Explorer uses to draw thumbnails, in a separate process, so a crash in one doesn’t take Explorer down with it. When you see “COM Surrogate has stopped working” or it eats your CPU, one of those plug-ins is usually the problem, not Windows. Find which one in Reliability Monitor, then update or remove it.

How we put this together: this guide is research, not a test. It’s built from Microsoft’s documentation, two explanations by Microsoft engineer Raymond Chen, MITRE’s malware reference and real Microsoft Q&A threads, all listed under Sources. Steps apply to Windows 11 (24H2, 25H2 and 26H2) and Windows 10.

What is COM Surrogate?

COM Surrogate is a host process that Windows uses to run a plug-in, or COM component, outside the program that asked for it. Microsoft’s documentation says running a component this way gives fault isolation: if the component crashes, the program that called it keeps going.

You meet it most in File Explorer. Thumbnail and preview handlers run in a separate process by default, and Explorer only calls them when a picture or video isn’t already in the thumbnail cache. Raymond Chen explained in 2009 that thumbnail extractors have a poor stability record, so Explorer would rather lose a helper process than itself. When a media folder is involved, a flaky codec is the first suspect.

Seeing several dllhost.exe processes at once is normal. Each one hosts a different component, and the component’s ID (its AppId) appears in that process’s command line.

Is COM Surrogate a virus?

Normally no. The real dllhost.exe is a signed Microsoft file. Malware can borrow a trusted name, though: MITRE, which catalogues attack techniques, lists copying a legitimate file name or folder as a common trick. So spend two minutes checking it.

  1. Open Task Manager (Ctrl+Shift+Esc), go to Details, right-click dllhost.exe and choose Open file location. Windows keeps it in C:\Windows\System32, with a 32-bit copy in C:\Windows\SysWOW64. Anywhere else is a red flag.
  2. Check the signature in PowerShell. A genuine file shows a valid Microsoft signature, and an unsigned one comes back blank:
Get-AuthenticodeSignature -FilePath "C:\Windows\System32\dllhost.exe"

Those checks catch a fake file. They can’t catch malware that injects its code into the real process, so if anything looks off, run a Microsoft Defender Offline scan. Go to Windows Security, Virus & threat protection, Scan options, choose Microsoft Defender Offline scan and click Scan now. Save your work first: it restarts the PC and takes about 15 minutes. If BitLocker is on, suspend it first or have your recovery key ready.

Why does it say “COM Surrogate has stopped working”?

Because a plug-in it was hosting crashed. Windows records which one, so look it up instead of guessing.

  1. Press Windows+R, type perfmon /rel and press Enter to open Reliability Monitor.
  2. Click the red entry for COM Surrogate on the day it crashed, then View technical details.
  3. Note the Fault Module Name. That’s the file that crashed.
  4. Find which program owns it, often a codec pack, a RAW, HEIC or PDF preview add-on, or a cloud drive’s Explorer extension. Update it, or remove it in Settings, Apps, Installed apps.

Not every COM Surrogate crash comes from Explorer. In one Microsoft Q&A thread the fault module was ESENT.dll, Windows’ database engine, and the crash never happened in Safe Mode or a clean boot. That points at a background program or service.

To see exactly what a running dllhost.exe is hosting, add the Command line column in Task Manager’s Details tab. Copy the GUID (the long ID in curly brackets) from its command line and look it up under HKEY_CLASSES_ROOT\AppId in the Registry Editor. Raymond Chen describes this as a debugging technique, so only read the registry here and change nothing.

Why is COM Surrogate using so much CPU?

Usually it’s stuck making thumbnails or previews, often for one awkward file in one folder. Try these in order, and stop when the CPU settles:

  • Switch the problem folder to List or Details view, which doesn’t need thumbnails.
  • Turn off the Preview pane: in File Explorer, View, Show, Preview pane.
  • In File Explorer Options, on the View tab, tick “Always show icons, never thumbnails” for a while.
  • Clear the thumbnail cache: run Disk Cleanup, tick Thumbnails and click OK.
  • If the problem follows one folder, move its newest files out one at a time to find the file that triggers it.

If CPU drops with thumbnails off, a thumbnail handler or codec is the cause. Update or remove it, as in the section above, then turn thumbnails back on.

“The file is open in COM Surrogate”: how to delete it

This means a dllhost.exe instance is still holding the file, usually because Explorer was drawing its thumbnail or preview. Close the Preview pane, then restart Explorer from Task Manager: on the Processes tab, right-click Windows Explorer and choose Restart.

If that doesn’t free it, Microsoft’s free PowerToys has a tool for exactly this. Turn on File Locksmith in PowerToys, then right-click the file, choose Show more options, then the menu item “Unlock with File Locksmith”. It lists the processes holding the file and lets you end the right one. Use “Restart as administrator” in it if the holder belongs to another user.

Still crashing? Isolate it and repair Windows

Start in Safe Mode, then try a clean boot, which is the order Microsoft Q&A moderators give. If it never fails there, a non-Microsoft program or service is to blame: turn your startup apps back on a few at a time until it returns. Then rule out damaged system files with DISM and SFC, in that order, from an administrator Command Prompt:

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

What not to do

Plenty of older guides still suggest fixes that cost you security, and none of them finds the real cause:

  • Don’t add dllhost.exe to the DEP exceptions. It’s Windows 7-era advice that weakens a protection, and one Microsoft Q&A poster found the System32 copy couldn’t even be added on 64-bit Windows.
  • Don’t run bcdedit /set {current} nx alwaysoff. It turns DEP off for the whole system.
  • Don’t exclude dllhost.exe from your antivirus or switch off real-time protection.
  • Don’t delete or disable dllhost.exe. Windows needs it, and it’s what keeps a bad plug-in from crashing Explorer.
  • Skip “DLL fixer”, registry cleaner and “PC repair” downloads. A Microsoft moderator flagged one such site in a COM Surrogate thread for promoting potentially unwanted programs.

Still on Windows 10?

Everything above works the same on Windows 10 22H2. Its free support ended on 14 October 2025, and paid Extended Security Updates to 12 October 2027 bring security fixes only. On Windows 11, 24H2 Home and Pro stopped getting updates on 13 October 2026, so move to 25H2 or 26H2.

Frequently asked questions

Can I end the COM Surrogate process?

Yes, a stuck instance is safe to end from Task Manager. Windows starts another when it needs one. Ending it won’t fix the plug-in behind the problem.

Why are there several COM Surrogate processes?

Each one hosts a different component, identified by the AppId in its command line. Add the Command line column in Task Manager’s Details tab to see them.

Is dllhost.exe safe?

The genuine one is, when it sits in System32 or SysWOW64 with a valid Microsoft signature. If it’s somewhere else or unsigned, run a Microsoft Defender Offline scan.

Should I add COM Surrogate to the DEP exceptions?

No. It’s dated advice that weakens a security feature and doesn’t tell you which plug-in is failing.

What to do now

Open Reliability Monitor with perfmon /rel and click the last COM Surrogate crash. The Fault Module Name tells you which program to update or remove.

Sources

Changelog

24 Oct 2026: rewritten from Microsoft’s documentation and recent Q&A threads, with checks for a fake dllhost.exe and the locked-file error. It replaces a guide first published on 12 September 2018.