I'm trying to delete a file or remove personal picture information from a *.jpg, but I'm told that "The action can't be completed because the file is open in COM Surrogate." What is going on?
Please open Windows Task Manager, enter processes and find any dllhost.exe processes.
Right click on it and choose: End process. After that please try deleting the file again.
Checked from TM. Don't have any such processes open?! In details I have dllhost.exe open and running, but it doesn't help to end it, reboots itself and the same situation up and running. How to stop the process completely or is it needed somewhere? Can it have something to do that I removed Acronis yesterday, have never had this problem before.
screenshot:
I think this is another of the issues that have emerged since the November update and so far there does not seem to be a fix.
OK. Thanks it seems so, have not heard this before. let's hope MS fixes this.
The problem described above. In addition to that have two COM surrogate processes shortly in task manager when started. What's going on here.
When a picture is right clicked got two COM surrogate processes in task manager, but they disappear shortly, when right clicked a picture again they reappear shortly. If clicked file location, it's c:/windows/system32/dllhost.exe . When TM is started there are two COM surrogate processes which disappear when it's open. A virus or something else? Have scanned with many AV and Malwarebytes etc, but found nothing. Something is keeping these COM surrogates active..? Attached some screenshots. Can't remove eg picture personal information because of this, have not noticed other "weird" things. Eraser.exe bcause wiping some empty drive space. Had com surrogate error with Acronis and W8.1, but don't know if that's the cause. It doesn't help to end dllhost.exe process, it restarts all over in loop.
For a delete try Unlocker here
Thanks, but can delete the file, just not remove personal properties in picture. Going for the thought that it's a Win 10 error, have the same on my laptop after November 1511 update, which has completely different SW and HW.
I have the same problem and it started with the November 1511 update