Cannot assign a drive letter to a partition from the backup archive
When I try to mount an archive, I get the above error.
Windows 7
Thank you for your assistance.
I am still getting the same error. This was not a problem when I first installed v.2012, but became a problem later.
I am able to access files in the archive and move them to other locations.
I have not and will not try to recover the disk and system (I would only do this in an emergency). Since I am unable to Mount the archive, I am concerned that it will fail, if a system recovery is necessary. I use other back up methods for my data.
Is there some way to determine whether the backup will recover the system without actually performing a recovery?
Well, you can boot from the recovery CD and restore a couple of files from the backup. It that works, you have a high level of confidence the backup can be used for recovery.
Since other factors can play (different disk, different size, etc.) nothing can really test it thorougly except an actual recovery... Don't worry, we all live with some uncertainty in this area, and others :-)
If rebooting the computer doesn't solve your issue, if setting it up as read only/read-write doesn't make any difference, you can:
- try to mount from the recovery CD,
- use ATI from Windows to convert it to VHD and the attache the VHD as a disk using disk management.
But of course, this is not as convenient as simply mounting the TIB file in Windows...
Double-clicking on the TIB file and exploring it is a fair test.
Pat,
Thank you. Uncertainty is the bane of my existence. :)
Exploring the TIB works.
I do not understand why the TIBs I create can no longer be mounted, as in the past. Perhaps I have an improper setting, or Acronis is not working properly.
If your Antivirus or anti-malware programs have a temporary shutoff, try closing those programs before attempting to mount. eSet has been reported to cause issues for some.
Also, some users report success using the read/write mode.
I found that my backup set was inexplicably missing a number. For example, backup16, backup17, backup19 with no number 18.
I verified from the logs that the missing number was never created.
I renamed the last one to the missing number and I was able to mount.
If the missing number weren't the next-to-last number, you'd probably need to renumber all those following the missing one.
Windows 7 Acronis True Image 2016
I experienced the same issue. The image I was trying to mount is on an external hard drive. To resolve the problem I used diskmgmt.msc and changed the drive letter from "M" to "F". After that, True Image successfully assigned a drive letter and I was able to explore the image too.
I would like to point out the drive letter being set as "M" is not the issue as I have another drive with the drive letter set as "O" and I was able to mount any image on that drive without any issue.
If this works for you please post accordingly as this would be very interesting.