Windows 10: File can't be deleted / modified,, its open in COM surrogate

Hello, i would like to ask how to get rid of the error, which prevents me to modify / delete certain files on my PC, since they are "opened in com surrogate".What bothers me that the two of these files currently on my desctop are SVG icons, one called "credit-card.svg" and second "map-location-dot.svg". Out of all files, these who are opened in COM surrogate. I run the scan Bit Defender and it found nothing. There are 3 COM surrogates processes within my PC, all leads to system32, so everything looks normal, but im little worried, since it picked two files of that particular name. These are

:)

 

The action cant be completed because the file is open in COM surrogate

You have opened or used other programs while tryied to make this change in the properties. To fix this problem, I suggest you close COM Surrogate by using Task Manager

1. press Ctrl+Shift+Esc keys simultaneously.
2. Locate the COM Surrogate process then right click it.
3. Locate End Task.
Note: If you can’t locate COM Surrogate process, switch to Details tab and find dllhost.exe. Then End Task.it

 

I have neither COM Surrogate in TASK MGR nor DLL files...

I have the same thing,COM surrogate and dll not listed,weird that some people have it and others don't. I turned off 'Always show icons never thumbnails' as someone said this may help but it didn't.

 

File open in COM Surrogate

If you enable command line view in task manager then you might see if dllhost.exe is running like this:







If that's the case then it's likely that you have one or more folders containing one or more corrupt images which explorer cannot create thumbnails for or else the thumbnails are corrupted. this can also happen especially with folders that contain video files where thumbnails are created.

The solution is tricky. Either scan for and delete corrupt image files and videos (if you know how to do it) or else move all suspect folders to an external drive and disconnect it. Reboot and test. If the problem has gone you would move folders back one at a time testing after each move.