Windows 10: Windows 11 - Thumbnails not generating properly, COM Surrogate High CPU Usage

Hi All,All of a sudden, with nothing changed that I am aware of, any new photos/videos I am adding to the PC, the folders green status bar goes nearly all the way across but then doesn't actually generate the new thumbnails.If I go out of the folder, then back in, it will have generated one more thumbnail, rinse and repeat.I have done SFC, Chkdsk, and an Avast scan, not sure where to go from here.Noticed the COM Surrogate usage is high whilst it's doing this.

:)

 

COM Surrogate using too much CPU, Thumbnail and Icon problem.


Hey guys i've been using Windows 10 for almost a month now, and I'm having some issues with it at the moment. I have too much videos and picture for work, that most thumbnail just won't load or generate.

Issues:

• Thumbnail not generating
• This PC/My Computer keeps loading and saying "Working on it" (File Explorer)
• High CPU usage for COM Surrogate, using 10% of my CPU all the time.

The way to solve it for me at the moment is killing the COM Surrogate process. But I'm looking for a permanent fix, which doesn't involve me killing the process all the time.

Killing the process of COM Surrogate will make:

• Thumbnail and icon to generate (although sometimes it still doesn't)
• This PC/My Computer instantly loads properly, without it saying "Working on it"

Any solution guys?

 

COM Surrogate using too much CPU, Thumbnail and Icon problem.

Your player is incompatible with your system. I just solved this issue by uninstalling 32 bit VLC Player and installing 64 bit version.

 

COM Surrogate high CPU usage due to Microsoft Edge browser

Encountered the high CPU usage issue with COM Surrogate but unlike previous solutions posted on here a few years ago and on other sites there's no video file dllhost.exe seems to be constantly trying to access, when I look at dllhost.exe in Process Explorer
under the file handles it just lists system files and the Edge cache, yet COM Surrogate consistently takes up 10-12% CPU until I manually terminate the process, so it seems there is another issue with COM Surrogate high CPU waste that does not involve Windows
trying and failing repeatedly to cache a thumbnail for a troublesome video file. Even weirder is that when I open a folder in Explorer containing lots of video files COM Surrogate seems to do its job of caching thumbnails and then closes when it's done doing
so. Yet when COM Surrogate decided to start running on its own in the background it keeps running and running and doesn't terminate at all, until forced to do so manually.

Update: I have now isolated this specific problem to Microsoft Edge, the anomalous CPU usage (12%) occurs when I start Edge and does not self-terminate unlike COM Surrogate's normal process when it's auto-started to cache thumbnails. Possibly dllhost is
struggling with "C:\Users\[User]\AppData\Local\Packages\Microsoft.MicrosoftEdge_[profile]\AppData\User\Default\CacheStorage\CacheStorage.edb" or "C:\Users\[User]\AppData\Local\Packages\Microsoft.MicrosoftEdge_[profile]\AppData\User\Default\CacheStorage\CacheStorage.jfm"
or "C:\Users\[user]\AppData\Local\Microsoft\Internet Explorer\CacheStorage\edb.log" if this Process Explorer method is indicative of the problem but this may be something else entirely, but it is related to Edge because the issue only arises when I start Edge
and not when COM Surrogate starts by itself to cache thumbnails, in which case it self-terminates normally when done.

To be clear, ~11% may not seem troublesome but it definitely is when it is CONSTANT. Meaning it does not stop even when I close Edge and has to be manually terminated, I only started looking into this when I noticed my CPU fans running faster consistently
for the past few days or week perhaps. I'm unaware if this anomalous behavior of COM Surrogate also occurs by itself (not triggered by starting Edge) but I will keep an eye out in the coming days.

I have run sfc /scannow (came up 100% no file corruption) and multiple full virus scans with F-Secure and Malwarebytes before posting. This seems like a new bug with Edge and COM Surrogate possibly.