Skip to main content

Problem Fixed Manually - Have Sent This Message to Acronis Support - Just A Suggestion - 1st Issue

Thread needs solution

Hello,

I recently had an issue that caused me quite a problem... it resulted in my having to make drives persistent, and uninstall/re-install Acronis True Image 2016. Quite an ordeal... since, I had to literally remove all registry entries related to Acronis True Image and all files on the computer related to True Image... otherwise, when I re-installed, the issue of Acronis Archive holding a seized drive letter continued... six hours to fix this issue.

It relates to the inability to set the Drive Letter of the Acronis Archive on the local computer one is using. My network drives, one of which was named M:, were not set as persistent in Windows. Hence, when I was in another office, which had a problem connecting to my M: network drive, Acronis Archive took over that drive letter, and THEN refused to let go.

This could all be avoided if one could direct the drive letter that the Acronis Achive on the local computer is to use, and/or provide a way to change the drive letter that Acronis Archive on the local computer is using, after it siezes a drive letter.

Anyway, this is just a suggestion. I have--like I said--made my network drives persistent. And, Acronis Archive is using drive letter H:, which is not a drive letter I had assigned to any other drive (local or network). Hopefully, the peristent setting of the network drives will prevent Acronis Archive from assuming any of my network drive letters in cases where those drives are not available in the future.

Thank you and best regards,

Cameron

0 Users found this helpful

Hello, Cameron.

When you're saying that the mapping of one of the network drives to the letter M: was not persistent you mean that you had to manually map the network drive after each reboot, is that correct? So when the letter M: was free (not mapped) you logged into your acronis account and True Image mapped it to Acronis Archive. Please correct me if I got something wrong.

Actually nevermind, I've reproduced the described scenario and the issue has been reported to the development team.