The COM surrogate has stopped working is one of the most common errors these days. It comes out of nowhere when you are browsing through your media files. You do not need to panic because we have provided the best fixes available here and we assure you that this guide should help you fix your problems. Re: com surrogate has stopped working in Windows 7 There are many internet posts, from all PC makers,not just Dell, and with XP/Vista/Win 7 with this problem. As you have reinstalled, I would reinstall back to the original Dell image - F8 at Power on POST will access the Dell PC Restore.
Dear Forum member,As this annoying problem also occurs with my computer, I would like to ask for advice. I attached a text file with the data I retrieved from the DumpFile with AppCrashView from the crashes during the last four days.
These reports only shows loaded modules from Acronis and Windows. I also have the dumpfiles generated by Windows, but I did not attach them.Details on system:Acronis TI 2014 build 6673, (ATIH20146673nl-NL)Windows 7 x64, Core i7 (2600k), 16 GB RAMIf anyone could advise me on this, I would be very pleased.Thanks in advance and kind regards,Erik. I've just started receiving 'Com surrogate stopped working messages'.
I'm running Win 7 Pro SP1 64-bit with all patches applied and TI 2014 Premium Build 6673. From the event log:Faulting application name: DllHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc6b7Faulting module name: tishell32.dll, version: 17.0.0.6673, time stamp: 0x52f0f906Exception code: 0xc0000005Fault offset: 0x0009e027Faulting process id: 0x19c0Faulting application start time: 0x01cfac4a622fbd2dFaulting application path: C:WindowsSysWOW64DllHost.exeFaulting module path: C:Program Files (x86)AcronisTrueImageHometishell32.dllReport Id: 770cb6b9-183e-11e4-b10a-3c970edcc14dAny assistance would be appreciated.Thanks. Hi Mainframer,Unfortunately, to date, Acronis has not fixed this problem, even though it is well known in both the forums and other Internet sites.
Hi Enchantech,Thanks, but that's the same reply I received from Acronis and I have not found those fixes to resolve the problem. It may stop the Error message, but it does not terminate the dllhost 32.
process. With that process still running, the safe release of an external drive containing the backup is not allowed.
Also, my system has a Radeon VGA card, so blaming the problem on an Intel video driver does not appear to solve the issue either.The offending process can be terminated manually, but why should that be necessary with properly written software?I also find it disturbing that, instead of taking on the issue, the Acronis reply to my ticket pointed to the same third party fix as you have indicated. Have they lost all their software engineers?Please don't get me wrong, I do appreciate your help but its just something that I feel Acronis should resolve with an update, along with a fix for the broken parts of their help file.Thanks,Mandacat. Here is my follow-up to my previous post.Granted that these issues and resolutions may be due to my lack of familiarity with the True Image nuances, but maybe they'd be helpful to others.Thank you Acronis, for your reply to my issues, but none of the steps I've tried ( resolved either of my specific problems. What does appear to have resolved them, although time will tell, is the following. Again, although the two problems appear to be resolved, it will take more time to be sure.The 'Com Surrogate' issue, where the external drive could not be 'safely' released, appears to have been resolved by removing the.tib file association with 'Windows Explorer'.
NOW, when directly opening a.tib file, the true image application also opens with it. Prior to correcting the file association,.tib files would open with 'Windows Explorer' which would result in the 'com surrogate' problem and the inability to 'safely' release the external drive.The other problem, which would hang the system with the 'operations in progress, please wait' and never shutdown, may have been caused by the backups defaulting to a daily schedule. When a backup is created, it automatically defaults to a daily schedule with the current time. If the schedule is not removed, this could cause a backup to try and run when not meant to do so and, if the destination is portable, without the destination device connected.Bill. Bill,Thanks for the update, it is quite interesting that the file association of.tib with Windows Explorer appears to be at issue with the COM Surrogate error.
What this tells me is that Windows Explorer does not know how to handle this file type in all cases. Even more interesting is that not all users have this problem only some. That tells me that there is a relationship between the dllhost.32 and the problem.
I would bet that there is a common thread here. Some other app maybe that registers drivers prior to ATI that might be interfering with process in some way. At any rate it is good to know about this possible fix.
If that changes please let us know.As for the other problem I think what you are saying here is if the user creates a backup task and then runs that task using Backup Now button and does not check the Do Not Schedule option for the backup then the default is as you say, daily scheduled at the current time. That is expected behavior and yes that could well cause the operations in progress error.