Direkt zum Inhalt

Can't mount drive from TIB images

Thread needs solution

Hi - I can't seem to mount a TIB image to a Windows drive letter. The TI2017 drive mounting application starts up OK, but there isn't a drive letter assigned after the Acronis mounting application starts.

I can extract individual files from the TIB image when browsing with Windows Explorer.

Is there a fix for this?

Thanks

A

0 Users found this helpful

Alan, please check what build version of ATI 2017 you have installed - this should be #8058 for the latest build.

The ability to mount a .TIB image to a drive letter is provided by the Windows Shell Integration from when ATI is installed, so if this is not working, the first step should be to try a Repair Install.

To do a Repair Install, download the latest full installer program from your Acronis account then run this from an Administrator account over the top of your existing software (without uninstalling first).

Thanks, Steven - I did an ATI Repair Install as an Administrator. I also did a sfc /scannow to make sure the Win10 install was good.

I see the same thing happening ... When I select Acronis True Image >> Mount from the context menu for the TIB image file, I get an Administrator request from ATI, and then I briefly see a small Initializing ... pop-up window that disappears with nothing occurring afterwards.

Didn't an ATI mount request usually come up with a prompt window for which image drives should be mounted with associated drive letters? If "yes", I don't see that happening anymore.

Is there a way to do a mount through the ATI 2017 application, or is it only available as a context menu selection?

Alan, there is no way to do the mount through the ATI 2017 GUI interface that I can find - this has to be done via Explorer.

Please see KB 60522: Acronis True Image 2018: Windows services and processes (there is no 2017 version of this document but this should still hold true for 2017).

From the above KB document, check what Acronis Services and Processes are shown as active / running on your computer?

In particular, you should see the TibMounterMonitor process running in the Windows Task Manager display, and when you try to Mount a .TIB image, then you should also see the TrueImageTools process running as invoked by the Windows Shell Integration.

If you still have problems with Mounting the .TIB file, then try creating a new Administrator User Account and try again from that new account.

Thanks, Steve - I think you pointed me to the root of the issue. The "Acronis Drive" service isn't in my Services list. Not sure if there is an easy fix, since the "repair" I did earlier didn't fix this. Do you have any suggestions?

If I uninstall and then reinstall ATI2017, will I lose all my settings and configurations for my existing nightly backups? I would hate to start my backups again from scratch.

Alan, the 'Acronis Drive' service is not related to mounting .TIB images, this is purely used for the Acronis Mobile Backup feature of the product, so if you are not using this, the drive service isn't needed.

Before you try doing the uninstall / reinstall of ATI 2017, make a copy of your C:\ProgramData\Acronis\TrueImageHome\Scripts and Database folders - these hold your backup task configuration scripts and your backup history information.

Restore these folders back to the same path before doing the reinstall and your tasks should be still there after the install.

Hi - I tried a total uninstall / reinstall of ATI 2017, including running Acronis' CleanupTool.exe, and it didn't fix the problem. Mounting an image still starts partway up, then disappears.

The weird thing is, I was able to temporarily get the drives to mount by changing the mount drive from M: to Z: using the process in this KB article: https://kb.acronis.com/content/59584

Note: I did lose all my previous backup information, even though I pre-saved and restored C:\ProgramData\Acronis\TrueImageHome\Scripts and C:\ProgramData\Acronis\TrueImageHome\Database. Not a big deal, but it would have been easier if the configurations didn't get erased.

Alan, the Acronis Drive defaults to using drive M: (sometimes regardless of any other use of the same drive letter!) - there have been numerous complaints about this and the hoops needed to jump through to change this when it should be an option on the GUI settings page!

With ATI 2018 Acronis have added a new Backup and Restore option for saving task settings to a zip file to make it easier than have to manually save and restore the ProgramData folders.

OK, I may have identified an important piece of information.

I tried mounting a smaller ATI backup image from my backup NAS, and it failed again (as usual).

Then, as an experiment, I tried copying the same backup image from my NAS to a local drive ... and then tried to mount that using ATI.

And ... It worked!

Huh. That's sort of good - apparently it is possible for TI2017 to mount an image if it isn't on my network NAS device. However, since most of my images are about 100 GB, I can't copy those down to my local SSD just to recover a few files.

Not sure if there is a solution for mounting images from NAS drives.

The solution: The next step I took was to mount my NAS backup share folder as a drive letter on my PC. After that, I was able to mount / unmount my ATI backups fine when mounting through the drive letter.

Thanks for all the help!

Alan

Alan, thanks for giving us feedback on what you have found here, I am sure it will be useful for other users if they encounter a similar problem.