EventID 1000:Faulting module name: ti_managers_proxy.dll, version: 20.0.0.5554
Today, a manual hard reboot was required to get back into Window 10 Pro 64-bit built version 14393.351 after it experienced an issue with the ti_managers_proxy.dll.
I experienced it twice today and on both cases Windows Explorer became completely unresponsive. I use True Image 2017, built 5554.
The error log entry generated is:
Description
Faulting Application Path: C:\Windows\SysWOW64\dllhost.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: DllHost.exe
Application Version: 10.0.14393.0
Application Timestamp: 5789917a
Fault Module Name: ti_managers_proxy.dll
Fault Module Version: 20.0.0.5554
Fault Module Timestamp: 57d82470
Exception Code: c0000005
Exception Offset: 0000a488
OS Version: 10.0.14393.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 1572
Additional Information 2: 1572663cfd08cc42af8c978a8af25d80
Additional Information 3: 8329
Additional Information 4: 832928ed5b63edb20088427e54b7c20b
Extra information about the problem
Bucket ID: f604bb04a2b25b15dff82142106f130b (108411677005)
I tried to find information on this issue in this forum e.g.:
There are three solutions mentioned in this forum:
- Cleanly remove and re-install True Image 2017 (see: https://kb.acronis.com/content/48668)
- Rename the ti_managers_proxy.dll file into e.g. ti_managers_proxy.dll.old
- Install a fixed ti_managers_proxy.dll (see: https://forum.acronis.com/forum/38423)
Option 3 is meant for True Image 2013 and refers to an old file i.e. 16.0.0.5817.
I will remove and reinstall True Image 2017 and see if the problems will be solved.
In the meantime, I have the following questions for this forum:
- Am I the only one with this issue (again) right now?
- Is the problem known to Acronis engineers? If so, is there or will there be a fix?
- What happens when I rename the ti_managers_proxy.dll, will True Image function properly for e.g. local backups? If so, why do we need it?
Cheers,
Dave


- Log in to post comments

Thank you for your response. A Support Ticket has been raised.
As the problem persists, I renamed the ti_managers_proxy.dll and rebooted.
If I have any news worth sharing on this issue, I will post it here.
Cheers,
Dave
- Log in to post comments

Had a long lasting support ticket, which was closed because I was unable to create a crash dump of the dll. So I used the work-around. Now I use a new PC and this issue seems no longer relevant.
- Log in to post comments

Dave, thanks for providing the update on this long running issue, sorry that you didn't find a more satisfactory solution from your support ticket but guess the developers also struggled without having more information to work with or having other users reporting the same issue.
Hope your new PC continues to work well for you.
- Log in to post comments

Dear Steve,
My pleasure. I like to close my topics whenever possible.
The Acronis support staff were struggling with this issue as well. They were very helpful, kind and professional.
The new machine works very well, thank you.
Unfortunately, I ran into a recovery issue with TI 2017 (see in this forum). I hope that be can be sorted out.
I am an Acronis user since version 8. As an advanced user, I like to tinker with my system, knowing TI has my back.
Cheers,
Dave
- Log in to post comments