Salta al contenuto principale

open TIB from windows explorer

Thread needs solution

Before I installed 2013 I could open tib files by double clicking on them in windows explorer and now with 2013 installed I can't. Is their setting I have to change or ?

0 Users found this helpful

This should still work with 2013 (works fine on all the systems I have 2013 installed on).
The first step to correct this would be to open the 2013 installer and run a repair installation.

Open TIB file with Explorer.
Used to with 2013 then it stopped. Now have 2014 and it still does not work. What am I updating for?

And...F-11--appears for about 1 second. At least it does not have a bunch of sqiggles added.

Harry,
TrueImage does work when you double click on a tib file.
As you had trouble with both 2013 and 2014, my recommendation (for what its worth) would be to use the TrueImage Cleanup utility (signature link below) and cleanup the residue of past Acronis installs and then reinstall fresh.

The cleanup utility has specific text instructions so do be sure and follow the instructioins such as listed in the "commond" section.
If you are using the Startup Recovery Manager, you should disable that before starting the cleanup.

Good luck.

I have the very same problem:

My .tib files will no longer open by doubling clicking them in Windows Explorer and the icons look like white paper. I tired editing Windows File Associations, but all this resulted in is Acronis app opening up. I use to be able to simply double-click my .tib files within Windows explorer and gain access to files within the .tib files. I uninstalled Acronis 2014 and re-installed, but still had the same problem. Then I uninstalled Acronis 2014 and run their Cleanup Tool for 2014 (atih_cleanup_tool_s_e), and fallowed all the instructions including the part about Regedit. Then downloaded the newest Acronis True Image 2014 (AcronisTrueImage2014_6688_en-US). Still same problem. Any help would be greatly appreciated. :)

btw: I found a post here on Acronis' site and spoke about adding the following (below), but all that caused was a BSOD. :(

UpperFilters
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Class\
{4D36E967-E325-11CE-BFC1-08002BE10318}
UpperFilters (PartMgr snapman)

HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Class\
{71A27CDD-812A-11D0-BEC7-08002BE2092F}
UpperFilters (VolSnap timounter snapman tdrpman