Skip to main content

Warning/tip about Installation Failure and Update Failure

Thread needs solution

FYI -- An installation failure, and subsequent update failures, on Windows 10 Pro (up to date) appear to be linked to my user TEMP and/or TMP folders assigned to a volume other than the "C" drive. The error message reads: "The system cannot move the file to a different disk drive." Upon my following the provided message link, Acronis reports "There is no information about this error available now." So for the purpose of installation of 2020 and #1 update, I guessed and successfully completed the installation and update upon my reassigning my TEMP and TMP environmental variables back to the default folders in "appdata". (At this moment, I have yet to check whether the product, once installed, runs with the environment variables set to a separate volume.) I conjecture that this is a lightweight error in the installation configuration or coding, but it should be addressed at minor cost - miniscule even - as part of a release of a professional commercial software product. Can this be considered a 'bug' that I ought to report and for which a ticket ought to be created, or is this mention of the condition enough to trigger consideration of a fix?

0 Users found this helpful

IT,

So you are saying that a Win 10 update moved your TEMP and TMP files which caused install failures of ATI or are you saying that the installation of ATI moved your TEMP and TMP folders and then gave the error message that lead you nowhere?

If Windows update did this then I would think MS would like to know that.

If ATI did this then I suspect that Acronis would like to know that.  In this case use the in app Feedback feature to report your findings.  You can also link to this thread if you desire.

I think he's saying that the system variables for temp and tmp are pointing to another drive, other than the OS drive and am assuming this was done manually and on purpose to keep the OS drive light and limit writes to it.  However, because temp and tmp were not on the OS drive, the installation failed as a result.  I would say that is a bug too.  However, if you have other system variables that redirect programdata or program files / program files (x86) to other drives as well, then that will definitely bork up ATI and likely prevent installation.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

We've fixed a similar issue in Acronis True Image 2016 Hotfix 3, no tickets for the same issue found after that. 

ITgreybeard, any chance you are upgrading from Acronis True Image 2016? If yes, I'd try the clean installation first. If the issue persists even with the clean instal, please send us Acronis system report via Feedback option available in the product.