Skip to main content

Cannot move file to another drive

Thread needs solution

It seems that a upgraded from ATI 2017 is a little bit too soon, to say the least.

- last tuesday (10-03) I installed the latest version of ATI 2018 over ATI 2017 and the installation failed ("cannot move file to another drive" - nobody knows which file and which drive). 

I ask help with a support ticket until now nothing happens.

Maybe some people overhere can help me, the installation on 2 other desktops was correctly only not on my HP laptop. I am running win10 pro with al updates

 

0 Users found this helpful

At this point, I believe your only option is to perform a clean install of ATI 2018.

Ekaterina Surkova has provided the steps necessary at the link below:

https://forum.acronis.com/forum/acronis-true-image-2017-forum/how-unins…

Regards,

FtrPilot

#FtRPilot thanx for the info but I already did this

I did a similar upgrade from ATI 2017 to 2018 on a Windows 10 system just a few days ago and all went fine first time.  Are you running the install from an Administrator level account?

Yes #Steve Smith as a admin, but on my other 2 PC's, laptop en desktop it works perfectly.

 

Thanks for confirming.  If you have already tried a clean install and still get this same problem then the only other recommendation is to open a Support Case directly with Acronis to have this problem investigated as there is little else we can offer from a user perspective.

I am assuming that you have either disabled (temporarily) or permitted the Acronis installer past any security software protection that you have in place here?  We have seen issues in earlier versions where security software prevented installation.

The other check-point are the installer logs in the C:\ProgramData\Acronis\ folder which can be viewed via the MVP Log Viewer tool (found via the Community Tools link below).

Yes, but I have on al the 3 systems the same security software. I opened a support case on last tuesday but maybe it is very busy because nothing happened until now, support asked for a few points in spite off that I  already send it to support.

Hope that the support case gathers more speed for you and you get a resolution to this issue.

Icecold,

Download the MVP log viewer and run it as administrator.  Look at the MSI installer logs which you can view using this tool.  See if you can find this error in the log as it may provide clues as to what is going wrong with your install.  You can also post the log here in the Forum for others to view and offer advise.  You will find the MVP log viewer tool HERE

In reply to by truwrikodrorow…

Yes #Steve Smith as a admin

I had the very same problem when upgrading from 2017 to 2018. Running from an administrator account was not enough. Right-click the installer program and "Run as an administrator". But maybe this is what you did ?

Yes this is what I did Run as an administrator

Hello Icecold,

Could you provide the support and us here the installation logs?

Here is how you can find them: https://kb.acronis.com/content/56655

They can also be located in C:\ProgramData\Acronis\TrueImageHome\Logs with the names starting from installer-numbersletters. The long log file is what you will be looking for.

 

After a cleanup and some repair actions like

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

sfc /scannow

The install off ATI 2018 works perfectly also i did a SD card in the slot dont now of this was neccesary but anyway everything works now.

Thanx for the support and help

 

In reply to by truwrikodrorow…

thank you for notifying!

I had the same message trying to install Acronis True Image 2019.

Thinking it really had to do with disk drive volumes, I tried to install from a command prompt on C: with TMP set to something on C: as well.

I reverted to version 2016 for a while, then resumed trying 2019.

I did an uninstall of 2016 and then read here https://kb.acronis.com/content/48668 about the registry for UpperFilters and LowerFilters. I found that my UpperFilters had fltsrv in there. I removed that, rebooted, and the 2019 install was successful!