ti_managers_proxy.dll error
Once a day I get this:
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: 0x12a4
Faulting application start time: 0x01d1b0cba5593b4c
Faulting application path: C:\WINDOWS\system32\DllHost.exe
Faulting module path: C:\Program Files\Acronis\TrueImageHome\ti_managers_proxy.dll
Report Id: a25e41e1-934d-44c9-b3b6-1f50815c60fa
Faulting package full name:
Faulting package-relative application ID:


- Se connecter pour poster des commentaires

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.
- Se connecter pour poster des commentaires