Thousands of Event ID 10010 DistributedCOM Errors during post

I have no experience with this error, but it has been discussed in the forum for previous versions of 2013.  There is a posted fix though - may be worth a shot

https://forum.acronis.com/forum/38423

This is the actual fix file provided in the thread...

 ti_managers_proxy.zip

Bobbo_3C0Xi,

Thank you for the suggestion.  I read through the thread in detail, and about half way down the Acronis engineer says that the fix in the "file shouldn't fix Com surrogate failure".  I take this to mean that the fix is for Explorer errors, which I am not experiencing. Given that the fix is for a different version I am reluctant to run it. 

I did have a look at Autoruns and this helped me clear out a few orphaned references left over from the upgrade from Win 7 to Win 10. 

I also looked at the Services that others have tried to disable and Acronis Sync Agent Service is already set to Automatic (Delayed Start).  I did set Acronis Nonstop Backup Service to Manual (since I am not using this feature), but it did not remove the DistributedCOM errors during post.  The other two services, namely Acronis Managed Machine Service Mini and Acronis Schedule2 Service would seem to be necessary for the program to run and I have left them on Automatic. 

I am hoping that an Acronis Engineer will suggest a fix.

Mark

I would recommend that you uninstall the TI application run the cleanup tool (item 3) in Bobbo's signature link following all instructions and then reinstall the TI application.

I was not able for find a cleanup tool for TI 2016 on the site and Boobo's signature only lists the tool for 2015.  Is this the one that you want me to try?

By the way, I did try to run the cleanup tool for TI 2013, since this was the previous version (I upgraded to 2016 just before moving to Win 10) and the one most likely to leave uninstalled "features".  However, the tool for TI 2013 would not run in Win 10. 

Nevertheless, the last time that I uninstalled TI 2016, I used https://kb.acronis.com/content/34876 to verifiy that none of the Upper and Lower filters in the CLSID entries contained any of the keys listed as problems. 

Is it still worth cleaning, will the 2015 version work?

Mark

I believe that previous version leftovers are the issue here.  So using the cleanup tools for removing them is advisable.  Many users whom had 2013 installed experienced the issue you are having.  Other than using the tool that Bobbo mentioned uninstall/reinstall of latest version was the best fix.

The 2015 cleanup tool is indeed the correct tool for removing 2016 so grab that and uninstall 2016.  After that  completes reboot your machine and then run the cleanup tool for 2013 and reboot again.  Once that is complete then reinstall the 2016 version.

This should resolve your problem.

Enchantech,

I uninstalled TI 2016 and ran the TI 2015 cleanup tool (file CleanupTool_46_en-US.exe).  I checked for the listed UpperFilters and LowerFilters keys at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} before restarting and there were none.  The TI 2013 cleanup tool does not run in Win 10 (see my previous post), but the intro text for the TI 2015 cleanup tool says that it works for TI 2013, so this should not be needed. 

Reboot after uninstall/cleanup gave no Event ID 10010 DistributedCOM errors as usual.  However, after reinstall there were 439 errors on restart (I think that this is a new record for one boot).  Usually this goes down to 90 errors or so on a restart when I edit the permissions as I described in my first post (so it must be helping somewhat), but I am going to hold off on doing this until I am sure that I will not have to uninstall again. 

The registry has 25 entries for the CLSID HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} (with up to 99 subentries), but only one of them has UpperFilters and LowerFilters, and the UpperFilters for this CLSID have the key fltsrv.  This key also appears in the UpperFilters for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{533c5b84-ec70-11d2-9505-00c04f79deaf} and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}. 

I could start deleting the key fltsrv at random, but I would prefer to have the advice of someone who knows what the entries are supposed to be.  Do you have the ability to refer this to an Acronis Engineer?

Mark

Going back to the original link I mentioned did you see the post from Arachnaut.  He had the exact same DCOM error as you and resolved the issue by:

renaming "C:\Program Files (x86)\Acronis\TrueImageHome\ti_managers_proxy.dll" to
"C:\Program Files (x86)\Acronis\TrueImageHome\ti_managers_proxy.dll.old" and restarting prior to running the proxy file.  Even then, the proxy file didn't seem to have a negative impact when he did, but it may not be necessary in your case

As for the cleanup tool and entries in the registry, you should be fine to delete them after running the cleantool and rebooting if they still exist.  They only reference fltsrv which is specific to the Acronis fltsrv.sys driver.  If there's any doubt though, you can export those keys before you modify and keep them handy to re-impport of need be.

http://www.file.net/process/fltsrv.sys.html

The genuine fltsrv.sys file is a software component of Acronis Storage Filter Management by Acronis.

Also, in that other post, the engineer was looking for others who might be able to produce this error for further testing as they could not replicate it in their lab and seems to not be too common of an issue.  Perhaps you could reach out to them and provide a system report and or see if they can use your system to further identify the issue and/or a more pernament fix?

I found this as well - see the very last 2 posts:  http://forums.whirlpool.net.au/archive/2006477

it links to:  https://forum.acronis.com/forum/35064

The fix in that one again is to rename C:\Program Files (x86)\Acronis\TrueImageHome\ti_managers_proxy.dll" to
"C:\Program Files (x86)\Acronis\TrueImageHome\ti_managers_proxy.dll.old" and restarting

It may be left over issues from 2013 where this issue originated from, but cannot be addressed with the 2013 tool since you're running Windows 10 x64.  Worth a shot to rename the file and reboot and see how it goes.  However, technically, once you run ATIH2015 cleanup, this file shouldn't even exist anymore.  If you do cleanup again, go back and see if any Acronis directories still exist and manually delete before rebooting as well:

C:\Program Files\Acronis, C:\Program Files (x86)\Acronis, C:\Program Files (x86)\Acronis\common, C:\Program Files\Acronis\common, C:\programdata (hidden folder).  If you're not against it, run CCLeaner too - I use it religiously, but I can understand some who may not want to. 

"The main issues with this seems to be that there is a conflict between Windows and ATIH. This occurs randomly in the default installation and is some interaction between explorer and ATIH. This seems to happen if you boot the system, log in and start an explorer session BEFORE the ATIH process(es) is/are really running properly.

In Windows 7 using the resource monitor look for the dllhost processes, right click and use the analyse wait chain.

One of the processes will have a long chain of threads. If this process is killed then everything returns to normal and the issue does not seem to reoccur

reinstalling/repairing ATIH may just have changes something that causes a slightly different timing when the system is booted, hence eliminating the issue."

__________________"

Bobbo,

Thank you for the new suggestions.  I uninstalled Acronis again, ran the TI 2015 CleanUp utility again and rebooted.  After this there were no instances of fltsrv in the entire registry and there were no Acronis directories remaining on the C: drive (I looked at your specific suggestions and searched for Acronis).

I then reinstalled TI 2016 again, and insted of rebooting I went to C:\Program Files (x86)\Acronis\TrueImageHome\ and renamed "ti_managers_proxy.dll" to "ti_managers_proxy.dll.old". (The file was installed with TI 2016 so it is not a carry over.)

When I restarted all of the 10010 DistributedCOM errors related to {1EF75F33-893B-4E8F-9655-C3D602BA4897} were absent.  There were 2 new 10010 errors related to the server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} that the registry says are related to ShellWindows.  (I quick Google search did not turn up any obvious causes.)

Acronis started OK with the file named "ti_managers_proxy.dll.old".

I then renamed "ti_managers_proxy.dll.old" back to "ti_managers_proxy.dll" and rebooted again.  All of the 10010 DistributedCOM errors related to {1EF75F33-893B-4E8F-9655-C3D602BA4897} were back again (93 this time) and the two new ShellWindows related errors were absent.  I have renamed the file "ti_managers_proxy.dll.old" again. 

Does anyone know what "ti_managers_proxy.dll" does and whether it is OK to leave it out in TI 2016?

I will spend some time searching the ShellWindows error tomorrow and see if I can pin it down better (and make it go away). 

Some progress anyway.

Thanks,

Matk

The new 10010 errors related to the server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} that the registry says are related to ShellWindows were not present the next time that I booted windows.  I went into the registry anyway, granted System and Administrators permission to the CLSID {9BA05972-F6A8-11CF-A442-00A0C90A8F39}, and then edited permissions in the DCOM service ShellWindows to give permission to Users.

I then renamed "ti_managers_proxy.dll.old" back to "ti_managers_proxy.dll" and rebooted again.  All of the 10010 DistributedCOM errors related to {1EF75F33-893B-4E8F-9655-C3D602BA4897} were back again. 

I have renamed the file "ti_managers_proxy.dll.old" again and there are now no DistributedCOM errors on boot. 

I am going to stay with this configuration unless anyone has any further suggestions.

Mark

I think you're probably in the best shape possible at this point.  Why this is happening on your machine, I have no idea.  You may still want to contact technical support and open a case with them as this is an issue that has been brought up before and it is not specifically clear what ti_managers_proxy.dll is used for, why renaming it removes those errors, and what the impact of renmaing it has on Acronis functionality.  

Bobbo,

I logged into the Customer Support site and it appears that my upgrade only came with one month of support, and that I would need to pay to contact them. 

Support can contact me if they wish to ask for a system report or further details from me on the error, but I will wait until I have an error that I can not fix another way before I pay for support on software that does not work properly.  And most likely I would try Acronis TI 2013 or move to another product first.

Thank you again for you help with resolving this issue.

Mark

I understand - I would not pay for a support case for this either, but I believe you might find that they would be willing to assist in this matter - especially since this is reproducable in 2016 when it should have been resolved already. If there are applicaiton defiiciency's that need to be addressed, I would hope that techncial support would be willing to assist 1) to make the product better, but 2) to help retain customers.  They provide unlimited recovery support at no charge, but I'm not sure what they consider a case-by-case issue, vs a recovery issue (if the application isn't workign propery, recovery is sure to be an issue as well).

I know you didn't want to originally y apply the fix from the proxy.zip file in the old forum post mentioned above, but I took a look and it is merely another ti_managers_proxy.dll file that you could try to use in lieu of renaming yours to .old.  I could also provide the same file from my 2016 system to see if it has any change for yours one way or another?

delete - sorry don't know how I ended up with a double post.

I did not want to apply the ti_managers_proxy download because I did not want to mix files within versions.  I have just downloaded the file from https://forum.acronis.com/forum/38423 and it is not quite the same size (679 kb old vs. 689 kb current) and the file dates are of course separated by nearly 2 years.  

Since the previous fix was primarily focused on Windows Explorer issues, whereas I am looking at multiple DCOM errors in post (this was apparent when I went into the Bios to change fan settings and the Event ID error times were much earlier than the time when I opened the Event Viewer in Windows), I am reluctant to use the earlier file.  Most of the files in my Acronis\TrueImageHome directory date from a narrow time frame on 26/11/15 (including ti_managers_proxy.dll from 11:13 AM -- North American Pacific Time that is).  Is yours any different?

Do the Acronis Engineers follow these threads?

Mark

Mine is dated 11/26/2015 11:07.  Properties on the file show:  689 KB (706,456 bytes).  There are also 2 other ones that seem to be related.  Attached if you want to try replacing with your own.

Bobbo,

The files that you posted have the same date and size as the ones installed on my computer. 

I decided to see if the TI 2013 file would help, so I copied the 2013 ti_managers_proxy.dll file into the Acronis\TrueImageHome directory.  On reboot all the 10010 DCOM errors reappeared (93 of them).  After deleting the file again and rebooting I got a large number of Event ID 131 (Metadata staging failed) errors (which are apparently related to Devices and Printers).  On reboot the 10010 DCOM errors reappeared again so I did another repair of TI 2016, and the errors were gone on reboot. 

I have been getting transient network access errors, so this seemed like a good time to uninstall and reinstall the Intel network connector software.  After doing this and rebooting the 10010 DCOM errors reappeared.  It took another repair of TI 2016 to make the errors go away.  Still getting the transient errors though (Windows 10 seems to generate lots of Event ID errors and warnings).  

So, in conclusion the 2016 and 2013 versions of the ti_managers_proxy.dll file both give numerous 10010 DCOM errors.  I can make them go away by renaming the the ti_managers_proxy.dll file, but it appears that installing other software can destabilise the fix, and I am not sure how it will work long term. 

A fix from Acronis would be nice!

Mark

After following this thread and all that has been attempted at repair and the end results I have a hypothesis. 

It is possible that since your machine was upgraded from a Win 7 OS with True Image 2013 installed to Window 10 and True Image 2016 the issues here are carry-overs from the previous installations.  So you might wish to consider performing what is known as an In Place Upgrade of Windows 10 on your machine which I think at this point is the only option left for you short of a complete fresh install of Windows 10 itself.

The link below covers how to perform this procedure.  The procedure will overwrite all Windows System files which results for all intents and purposes to a fresh OS installation.  It wil not remove your install apps nor user data nor user settings

I would recommend that you first uninstall True Image 2016 yet once again and run the clean up tool again to remove the applicaiton from the machine before you perform this In Place Upgrade.  I would also recommend that you use a third party uninstaller rather than the standard Windows Programs and Features method to remove the application so that you have a way to remove any leftover registry entries left from the uninstall process.  The uninstaller I use for such purposes is Revo Uninstaller but that is just personal preference.  The use of the Acronis clean up tool afterwards would be secondary insurance for complete removal of the application.  Then follow all the steps outlined in the provided link. 

I have not performed this procedure on a Win 10 install but I have done so on several previous Windows versions.  All but 1 of those fixed the problems that were being experienced with the installation.

There is no guarantee here for success but at this point I think you have exhausted all other possibilities.  Good Luck.

http://www.tenforums.com/tutorials/16397-repair-install-windows-10-plac…

Enchantech,

Thank you for your detailed suggestions. 

Just to clarify, TI 2013 was installed in a fresh install of Windows 7, and I upgraded to TI 2016 just before I upgraded to Windows 10. 

I upgraded my laptop from Win 8.1 to Win 10 with TI 2013 installed and did not have any of the problems that I am having with TI on the desktop.  The laptop does have its own set of Event ID DCOM errors, that I have not had time to troubleshoot properly, and I did try an in place upgrade/repair install to fix problems with freezing on reopening a saved session (a widely reported problem with no well defined solution).  The upgrade did not fix any of the problems with DCOM errors or freezing, and it completely broke both the Workgroup and Homegroup connections to other computers (by requiring a password when one was not needed, and the correct computer address and password did not work -- another widely reported problem with no solution).  I used Acronis to restore to a previous version.  I am pretty commited to Win 10 on the desktop (because of a multiple display set up), but I have also set up a dual boot to Windows 7.  For the laptop, I want to try uninstalling a couple of unneeded Asus utilities (with no Win 10 upgrades), and if that does not work I will probably do a Win 7 install. 

So, this is to say I do not hold out a lot of hope for an in place upgrade/repair install.  If I do the repair on the desktop I will make a full backup so I can recover the previous install.  And it will likely have to wait until I get the laptop sorted out and I have at least half a day to work on it. 

Thanks for your help.

Mark

I understand completely.  I would say that your issue began because of the fact that the TI 2013 product was upgraded to TI 2016 rather than uninstalling TI 2013, running the clean up tool for 2013 and then clean installing TI 2016.

You might keep that in mind while working on your laptop.

I still have a backup for my Windows 7 C: drive for a date a few days before I bought the Acronis TI 2016 upgrade.  So it still would be possible for me to recover that backup, uninstall and cleanup TI 2013 and do the upgrade to Windows 10 again.  I would have to redo all of the configuration fixes that I did to Win 10 to get programs to run properly (Win 10 handles permissions, display scaling etc. differently than "legacy" programs -- i.e. written prior to the Win 10 release -- expect, and even Office 2013 has DPI scaling issues in a multi-display configuration), but that would be doable.  (I also made notes, and it should be easier the second time.)

If I do this would it be better to uninstall TI 2013, do the upgrade and then install TI 2016?  Or is this a non-issue?

Also, I think that there still is a possibility that my problem is related to a conflict with another program, or an incorrect registry setting, or both.  In this case reverting to an earlier version of the Win 7 C: drive and redoing the upgrade would not fix the problem.  So what is the likelihood of this, and are there any previous support cases that would suggest that this is possible/likely?

Thanks,

Mark

Ideally, since you upraded not just ATIH 2013 to 2016 and then Win 7 to Win 10, honestly, I would fresh install Windows 10, configure it exactly how you want it from scratch (no cheating by upgrading and or importing settings, data, applications, etc. this time).  You will then have a pristine Windows 10 baseline build with no residual leftovers to start a good recovery backup image with.

This will take some time as you will basically be building fresh.  However, that alleviates any possibliity of importing past system issues in Win 7 and/or past versions of Acronis.  

Get your base image all set - I'd recommend not even bringing in existing profile data yet and take that image.  Then bring in your profile data from a past backup (just the data - my docs, pictures, music, etc if they live on your OS drive too) and take another offline image as your next recovery point.  

If all is well, then install Acronis 2016, configure backups within Windows and let those run and see how it behaves.  If all is well, take another full offline image and that will be another restore point you can fall back on.

Moving forward, hopeflly it will be smooth sailing in all aspects of your new OS install and/or with Acronis.

Bobbo,

I have too many installed programs with custom settings/configurations and I am only willing to do a fresh install if there are large scale Windows problems (as opposed to having one program with a history of issues producing problems).  Also, there still is a possibility that my problem is related to a conflict with another program, and I could go through all the hastles of a fresh install and still have problems. 

I restored the backup for my Windows 7 C: drive from a few days before I bought the Acronis TI 2016 upgrade, uninstalled TI 2013, and ran the clean up tools for both TI 2013 and TI 2015 (with reboots for both).  I then uninstalled two programs that were not supported in Win 10, namely the Win 7 Atheros Bluetooth suite that came with my Asus motherboard (that also would not uninstall properly in Win 10) and Windows Media player (by turning off all the Media features and re-booting).  (There were a lot of remaining Media Player entries in the registry after the first upgrade.)

After the upgrade to Win 10 and installing all the motherboard Win 10 drivers I had only a few remaing errors in the Event Viewer.  (Getting rid of Media Player and the Bluetooth suite before the upgrade proved to be a very good plan.)  The Task Scheduler had only three orphan tasks (which I removed by deleting the appropriate keys in the registry and reinstailling one utility) and Autoruns only showed a few "file not found" entries (which could all be deleted).  After configuring several other things I did a full Backup of C:, installed TI 2016 and rebooted.  There were 394 Distributed COM 10010 Event ID errors!  The errors still go away if I rename the ti_managers_proxy.dll file to ti_managers_proxy.dll.old.

A few days later I uninstalled TI 2016, ran the 2015 cleanup tool, rebooted, installed TI 2013 with upgrades and replaced the ti_managers_proxy.dll with the one from the Acronis website.  The result on reboot was 108 Distributed COM 10010 Event ID errors.  I then restored the system back to a restore point after installing TI 2016 (which removed TI 2013 and restored TI 2016). 

It is now a week since the re-install, Acronis is running properly and giving no errors with the ti_managers_proxy.dll.old fix.  I am still only getting the occasional, minor Event ID error.  Most of these either have been reported elsewhere and happen with both upgrade and fresh installs or are tied to a program with a Win 10 update.  Most of these minor errors appear to be related to Win 10 program glitches and will likely disappear as Microsoft issues updates.

The TI 2013 program did not give Distributed COM 10010 Event ID errors on my system in Windows 7, so the fact that they appear in Win 10 suggests that they are due to some unresolved conflict rather than some carry over error from TI 2013.  Whatever the cause, I have a properly functioning system am not going to consider a Win 10 fresh install untill something breaks (and a re-install is the best/only fix). 

Acronis Support can contact me if they wish to ask for a system report or further details from me on the error. 

Thanks again to you and Enchantech for your help.

Mark

Hello Everyone,

Thank you for sharing the experience with addressing the issue. I have reported it to the development team. It would be most useful if we had a system report from the computer where events 10010 are still being generated massively. Mark, I have just sent you a message with details on how to send system report to us.

Regards,

Slava

Hello Slava,

Thank you for your e-mail and the above message.  I am glad to see that this issue has come to the attention of Acronis Support.

In your e-mail you asked me to restore an "old backup, where events 10010 are massively generated in Windows event log".  I do have a few backups from the last few months (as I tried to deal with this and other Windows 10 errors), but this should not be necessary, since all that I should have to do is rename the ti_managers_proxy.dll.old file back to ti_managers_proxy.dll and reboot.  This should also have the advantage of providing a system where I have eliminated the major errors (there are still a few minor errors that seem to have been around for years, through multiple Windows versions, that I have not had time to tackle). 

I should also mention that my laptop is showing the same event 10010 Acronis error, where the ti_managers_proxy.dll.old file renaming provides the fix.  The laptop was upgraded from Win 8.1 (rather than Win 7 for the desktop), but it also had the TI 2013 to TI 2016 upgrade, and it has most of the same programs installed.  I could generate another system report from the laptop if it would help.  Please let me know.

In the meantime I will restore the ti_managers_proxy.dll file, reboot, generate a system report and submit it.

Regards,

Mark

Hello Mark,

I have received the system report. Thank you for the assistance in this issue investigation.

If you upload another report from the laptop, that would help to isolate the problem better.

Regards,

Slava

Slava,

I have sent the laptop sysyem report.  I look forward to hearing the results.

Mark

Hello Mark,

Thank you for sending system report from the laptop. I have attached it to our internal ticket, where developers duscuss the problem.

As for results that you have mentioned, there is no information on when we will have them.

Regards,

Slava

I am not getting this error massive time, but at least twice a day. Do you want any additional system reports ?

Slava wrote:

Hello Everyone,

Thank you for sharing the experience with addressing the issue. I have reported it to the development team. It would be most useful if we had a system report from the computer where events 10010 are still being generated massively. Mark, I have just sent you a message with details on how to send system report to us.

Regards,

Slava

Fred, which DCOM error.  There is a very common one in Windows 10 and 8.1 (and possbly other versions) which is not related to Acronis.  DCOM errors can be triggered by lots of things.  The paticular one below still shows up on my system regularlly.  I have not found/seen any issues as a result though and it's not from Acronis so just wanted to point this out if it's the same one you're seeing a couple of times a day.  

This is the DCOM error I see - even after a fresh Windows 10 install, it shows up soon after...

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 There is a fix and it does work, but only temporarily and then the issue returns at some point.  It is reported in several Windows forums as well. 

Bobbo, Here is what I see at least twice a day

Date/Time : 5/20/2016 6:19:59 AM
Type      : 2    Error
Event ID  : 1000
Source    : Application Error
Description: Faulting application name: DllHost.exe, version: 10.0.10586.0, time stamp: 0x5632d89f
Faulting module name: ti_managers_proxy.dll, version: 19.0.0.6569, time stamp: 0x571fb192
Exception code: 0xc0000005
Fault offset: 0x0000a4b9
Faulting process id: 0x994
Faulting application start time: 0x01d1b29a4c4d3756
Faulting application path: C:\WINDOWS\system32\DllHost.exe
Faulting module path: C:\Program Files\Acronis\TrueImageHome\ti_managers_proxy.dll

I have read whare people recommend renaming that dll to dll.old which seems to me to be a bandaid. I'd like to know what the ti_managers_proxy.dll actually does - exception 0xc0000005 is memory access I believe, usually a bad/null pointer. 

I'm not entirely sure.  I see a lot of online posts about his with 2012/2013 - did you ugprade at some point - if so, maybe it's leftover and removing from control panel, running the 2016 clean tool, rebooting, downloading v6569 from the account and installing fresh with right click and "run as administrator" may fix this and other possible underlying errors from past upgrades that may be lurking. 

If you don't want to do that just yset, a few times in my online searches today, I came across people mentioning fixes that worked for them..

1) Try to re-register the .dll with regsvr32 from an elevated command prompt. I tried from my machine and was able to register successfully using resvr32.exe from C:\Windows\system32 and C:\Windows\syswow64.  AFter registering with both, reboot, run a backup and see if the errors return or not.

2) A few people mentioned they got this error after disabling the Acronis Sync Service - is yours running or is it disabled?  If it's not running, try enabling and see if the errors still appear if #1 doesn't fix it.  

3) If it is running already, try changing the start type from automatic to automatic delayed as others reported that they got the error if Acronis tried to start the sync service before other Windows services had fully loaded.  

http://www.sevenforums.com/bsod-help-support/220537-com-surrogate-stopp…

I believe, and confirm, this occurs when my USB Drive is not attached and this failure is caused by a startup configuration as part of Acronis to detect it.  I observed this because I attach, then detach my backup drive only after I do a backup.  I have left it attached, and these errors do not occur.  I leave it detached, just in case, considering the number of exploits revealed by wikileaks in their Vault 7 releases; that, plus the number of ransomware exploits in the wild.

Apparently the dll continues to attempt connecting to the device until it times out. Fortunately (?) I time out after around 22 tries. But, it occurs everytime I boot and the device is not connected.

There is or used to be a setting in Acronis where I could tell it to only back up when the removable media is connected; but, I con't find that setting anymore, and so can't say what my default is, or whether this affects the errors or not.  But, I have no doubt it's related to Acronis.

Don't let the Acronis status of Beginner fool ya; I've been a systems analyst since the first Microsoft OS.

Lately, I've seen this happen; but only rarely, even if the media is attached. But, on the last date this occurred, I was doing some troubleshooting on the system for other minor errors, and did a restart, which is a full boot, instead of the normally defaulted, quick boot.  I'll work on checking this out to see if it's related to the quick start or not.

BTW I am running Acronis TI 2016; might be worth an upgrade if it's fixed in 2017 :-)

I had this problem once before. I did the rename thing and it worked. It started again with Win 10 update 1803.

I attempted to do the rename again and now get a windows "need permission to change file" error. Kind of up the game a little. Appears that a fix is needed before we start uninstall and reinstall. Acronis needs to look at what was programed and figure out what is stopping the administrator from having the privileges required to make changes. I did all the normal security stuff and got nowhere.

Hello Rob,

If you are using Acronis True Image 2018, make sure, Acronis Active Protection is turned off prior making changes, see Managing Acronis Active Protection. Otherwise this component will protects the program internals from any external modification attempts.