Skip to main content

Problem reading a True Image 2016 archive

Thread needs solution

Reading an archive has become impossible?

I click on the archive I want to look into and it strats opening, but also opens a lot of similar windows.

When I wand to get into the archive it ceaselessly tries to open new windows. It has become impossible to get my data back!

What is happening with True Image 2016. I was used to True Image 2014 and I ciuld read my archives very easily. NOT NOW!!!!

0 Users found this helpful

Welcome to these user forums.

Please can you provide some more background information here - has this been working without problem previously, and if so, has anything changed recently that may have contributed to this problem?

What version of Windows are you running?
What build version of ATIH 2016 do you have?  The lastest build is 6571 - check your Account page in the GUI.

How are you opening your backup files - I assume that you mean this when you use 'archive'?
Are you doing this from within the ATIH 2016 GUI?
Are you using Windows Explorer?
Are you double-clicking on the .TIB file in Explorer?
Are you taking the option for TrueImageHome >> Mount in Explorer?

In the past I had been using True Image 2014.

I was making archives (backups) of two kinds: one of disk C and one of disk D. My system and programs are on C and my data is on D. Safe and sure. Both Backups were if the Incremental style, with a Full being made every 20 or 25th day.

I installed Windows 10 amnd decided to use the newer True Image 2014. I was able to restore the complete Disk C and it was very useful if I did something wrong during the installation of Windows 10. That said, I have always been using the Disk D backups as a safety if some of my data should be compared with earlier data (or versions of the same program, for example). I do some programming. Ha ha!

What I had to do was to click on the .tib archive and the disk" was opening and I could get every tidbit of file I wanted and I copied it to the location I wanted.

UNFORTUNATELY, now I cannot anymore, because the .tib archive opens the "disk iocon" but refuses to go farther than that, except that it opens repeatedly the same windows containing the same .tib archive files. AND I cannot acess my files anymore...

As for the "Mount" I never had to use that in the past. I used it. It works fine, BUT it is clumsy to use because I have to mount every time ... GRR!

 

But thanks for showing me the "way"

 

ATI 2014 predates Windows 10 [I think] - so it might be wise to upgrade to ATI 2016, the latest version.  And if you cannot do that, try uninstalling and reinstalling ATI 2014.  The 'mount' function is easier to use for navigating the file structure since a mounted drive appears in Windows Explorer like any other drive - even though it is a Virtual Drive created by the Acronis software - yet the system treats it like a normal drive.  Now, IF you retrieve individual files and folders on a regular basis, what I'd recommend is mounting the drive everytime you login to Windows - it won't be any drain on resources and will merely appear as another drive letter in Windows Explorer and in all of the dialog boxes which allow the user to access files.  Only difference is, a mounted drive is readonly - you can read from it but of course cannot write to it since it is not a real drive, but only a recorded image representing a snapshot of your drive at a given point in time.  Hope that helps.  One other thought:  most software that will run on Windows 8 will run on Windows 10.  So, hopefully ATI 2014, which is fully compatible with Windows 8, can also run with full functionality on Windows 10.

Some are reporting that 2014 works with Windows 10, but it's not officially supported.  Windows 10 support was not introduced until the last release in Acronis 2015 which is the same year Windows 10 was released in beta (July 2015).  Each Windows 10 "update" makes it less likely to be usable as well since the OS keeps changing - especially as we've seen (or heard, or read) with the new crop of issues from the Windows Anniversay "update" (which, like other Windows 10 updates, is really a full OS upgrade/install). 

I'm sure the offline recovery media and taking full backups while the drive is idle and/or restoring in the same manner is fine since it's all just data, but the application working inside of Windows is where the compatibility becomes an issue.  

44112: Acronis True Image 2014: Supported Operating Systems

OK I can mount an image (backup)

BUT muy backups are in the following way:

- ONE entire backup followed by daily INCREMENTAL backups.

If I mount the INITIAL backup (which I can mount) I can only access the FIRST DATA

If I try to mount the last INCREMENTAL archive I always get the "Affectation de lettre impossible à la partition contenue dans la sauvegarde." message!!!! NOT VERY USEFUL it is!!! The only data I can access is the OLD DATA, not the LATEST archived data. Very annoying and time consuming!!!

How do I get the latest archived data???

NOTE: THe same problem arises if I try to mount ANY INCREMENTAL archive, not just the FIRST INCREMENTAL archive

Can I clarify which version of ATIH you are using here, in your initial post you spoke of ATIH 2016, then later you spoke about ATIH 2014 - which one of these are you using when you have a problem mounting .TIB files?

If it is ATIH 2016 then please see post: https://forum.acronis.com/forum/116874?page=1#comment-374611 and download the zip file referenced there and extract the tib_mounter_setup_2637.msi patch installer file.  Right-click on this MSI file and take the option to Install - this will fix known problems with mounting TIB files for 2016.

If you are using ATIH 2014 with Windows 10 then sorry but I cannot help you further as this is not a supported combination and while it may work it has not been tested and may produce unpredictable behaviour such as this problem.

Yup - I'd try the tibmounter patch first (http://forum.acronis.com/forum/116874?page=1#comment-374611

If that doesn't do it, I've had luck with kooky behavior when double clicking .tibs (not mounting), by following the directions here (even though it's for a specific behavior, it has fixed other similar issus for me too):

https://forum.acronis.com/forum/117232#comment-359062