Windows Explorer rt. click context menu/Explore takes MINUTES to open ANY folder after TIH2012 and Plus are installed
After upgrading from ATIH 2011 and Plus to 2012 and Plus, any attempt to use windows (XP Pro) right click context menu/Explore takes minutes to open the folder. This occurs whether ATIH is open or not - it appears to be bad code in the Acronis context handler(s) - see http://windowsxp.mvps.org/slowrightclick.htm for how I managed to fix it temporarily using ShellExView, until a fix from Acronis appears.
I emailed Support about this several days ago - no response as yet.
I should add that when ATIH 2012 is uninstalled, the problem vanishes 0 Rt. Click - Explore in Windows context menu opens a folder immediately. Guess I'll go back to 2011 version.
- Anmelden, um Kommentare verfassen zu können
Magic! That worked. Tricky to find in Help/Manual where to make that change, but no matter. You saved my bacon!
- Anmelden, um Kommentare verfassen zu können
I see no mention of this issue being addressed in the new version. Is anyone listening in tech support? I uninstalled my (purchased) 2012 and went back to 2011 because of this issue and others (though my memory fails me on the 'others' details!)
- Anmelden, um Kommentare verfassen zu können
Just recently I began having a problem where right click and select "search" would hang for about a minute before showing the search window. It turned out to be ATH2012 context handler.
There's also a problem with outlook e-mail backup where outlook has to be restarted because ATH2012 closed the file to make the backup. That prevents scheduling the backup. Have to run manually so I can unload Outlook first and then restart it after.
- Anmelden, um Kommentare verfassen zu können
I find the problem exists it TIH 2013 also. I have been trying to track it down for more than a week now. Trying to open "My Computer" (Computer Win 7) of the Network desktop icon causes this to happen, only it never opens - just sits there. This is not all the time, but maybe 25%. I will try disabling the windows shell items and see what happens.
- Anmelden, um Kommentare verfassen zu können
I believe this is a symptom of the "com surrogate" error. Acronis issued a fix for it, which is here on the forums. I'll see if I can find it, or you can search.
- Anmelden, um Kommentare verfassen zu können