Problem exploring backups - TI not remembering "last" location
I have backups going back to Ti "version 5". I can explorer all backups just fine BUT ONLY if I am logged in under the administrators name that installed TI 2016. I have the latest 2016 update BTW. If I log in under another administrator account then every time I explorer the TI backup I am asked to locate the last backup file.
This is windows 10x64 and both of the administrator accounts are mine but the account I installed and activated TI 2016 was the so called microsoft account that I have to enter my email into so as to get microsofts blessing. The other administrator account is the original windows 7 account that I upgraded from windows 7 to the free windows 10 on the first day WIN10 it came out.
It is extremely inconvient to have to have to tell TI2016 where the backup file is located EVERY TIME I ACCESS THE SAME BACKUP and I dont recall having to do this with TI2013.
BACKUPFILE.TIB -> "C DRIVE" -> USERS -> USERNAME -> DOCUMENTS -> "DOCUMENT I WANT TO RETREIVE": I have to click on the same backup file name 6 times before I can access that document as your program seems to have short term memory loss.
It appears that TI2016 is attempting to save the name of the backup on the property list of the installer and not the property list of the user and permission to save it is denied. That is just a guess but it is more believable than your program not liking that I didnt use the login that microsoft wants me to use.
Anyway, it would be nice if you could look into this and fix it.
TIA!!!
Two things - 1) make sure your admin account is in the "administrators' group and "backup operator's group. If not in both, add it to them and reboot.
2) I would also clear the tibmount cache under both profiles (if you can) and then reboot as well. Tibmount cache issues can cause strange behavior with things like (cannot locate volume 1, or double clicking a .tib and nothing happening, maybe it's part of the cause in this case too).
https://forum.acronis.com/forum/117232#comment-359062
delete the files in (if it says you can't delete them, they are in use so reboot first.
%userprofile\AppData\Local\VirtualStore\ProgramData\Acronis\TrueImageHome\Database
Solved by a clean install of windows 10. I did get with tech support who were very helpful but there were other problems with my 7 to 10 upgrade, not just with Acronis TI. Tech support called me personally after I reported it as fixed which I appreciate. I dont recall every getting a call from Nero or Microsoft following a problem.
Joseph, thanks for the update / feedback. Sometimes a clean install of the OS is needed - have just gone through the same with a Windows 7 system for a friend as the problems it presented defied all logic! Clean install and fixed! Great to hear that you got a call from Acronis Tech Support too on this!
Glad all is well Joseph. I'm also really happy Acronis reached back out to follow-up.
Yeah, upgrades (of any kind) arent' guaranteed to always go well. Unfortunately, I suspect over-the-top-OS upgrades are the root of many issues in the forums. There are people who upgraded from XP to 7 to 8 to 8.1 to 10, to 10 anniversary or some combination over who knows what time frame. With each upgrade, settings, apps, etc. become more at risk of running into trouble - trouble that may already be there, but not identified until the upgrade tries to access those files and can't handle them properly.
In a a business IT shop, standard practice is usually to reload and OS from scratch with each new version and most offices will wait several months (or longer) before upgrading, and often skip versions (for instance Vista and Windows 8) until something more stable and better comes along. Actually, until Windows 10, Enterprise editions for the PC OSes didn't evn allow upgrade options - it would say "no compatible OS found" if you tried with an enterprise installer disc.
At home, most people just expect the PC to turn on and work, but many have no idea how to maintain them or keep them running smooth. Even those of us who do, still run into strange issues from time to time which are better solved with clean installs than trying to find the culprit. If it takes more than 1-2 hours to trouble shoot and completely fix, and is causing enough headaches while broken, it's better to cut losses and rebuild from scratch and then restore data. A lot of people dread this though and end up wasting more time troublesthooing or wanting to find a fix.
Glad you were able to rebuild the OS without too much trouble and things are all running smoothly again.