Windows 10: fake COM Surrogate dlihost.exe cause high CPU usage

I've seen a bunch of posts, saying COM Surrogate high cpu usage, but not find any answer.Recently, I found that it is actually a crypto miner, and it is a fake dllhost.exe it's name is dlihost.exe but "i" capitalizedfile in \AppData\Roaming\DLL\. So i deleted it and my computer back to normal.But i want to know, what should i do after deleting this, because i still worry about safety.

:)

 

Cortana & COM Surrogate high CPU usage when Search or Start Menu is opened

Hi Ruth,

Thank you for suggesting these troubleshooting steps. Unfortunately, starting in a Clean Boot did not resolve the issue. I remember that there were some updates available prior to this issue (KB3156421 and KB3152599) and I didn't do any major changes to
the system.

One thing that I forgot to mention in my first post, is that the high CPU usage also sometimes occurs with the "Host Process for Windows Tasks" process too. It mostly happens with COM Surrogate, but this process shows up sometimes too.

Thanks!

 

WIN10 1703 update cause Explorer.exe high CPU usage

Hi,



Glad you reached out. First, we would like to know if Explorer.exe
is the only cause of high CPU usage. Because the common cause of high CPU usage are the following:

- Windows 10 Memory leak after the update.

- Driver incompatibilities after the update.

- Multiple startup applications

• 
  

We'll be waiting for your update.

 

COM Surrogate Too High CPU Usage Because of Windows Search

Hi Mike,

Please use Nirsoft ShellExView to disable *all* third-party shell extensions. Don't accidentally disable Microsoft extensions.

Log off and log back into your account.

• ShellExView - Shell Extension Manager For Windows
  

• How to Start Explorer.exe Cleanly by Disabling Third-party Modules » Winhelponline
  

This starts a clean instance of Explorer.exe.

If that helps, narrow down the offending extension by reenabling some extensions in ShellExView, logging off and logging back in, and testing. Alternatively, you can restart Explorer via Task Manager to refresh the shell without logging off.

If COM Surrogate continues to use high CPU, try Process Monitor from Microsoft. When the COM Surrogate CPU usage spikes, please run a Process Monitor trace for 2-3 minutes. Save "All Events" to a PML log file. *Zip* the log file and share it on OneDrive.