Stop TrueImageHome 2013/2012 Startup Search for Backups: Cannot Stop

This issue has been a problem for 2013 since early beta versions were released. The behavior of "search for backups at startup" was changed in the 2013 versions, and the ability to "skip" the search for backups during install/first run was implemented. Additionally, the ability to remove the found items from the Backup and Recovery tab and then later "Scan for backups" to repopulate the list seems to be broken as well. I used to use this feature (with 2012) when exchanging external hard disks that contained backup image files, but once the list (on the Backup and Recovery tab) is cleared, the "scan for backups" will not pick up any of the backup files that have been found previously, and then removed from the list, without deleting some .xml files within the program to allow Acronis to rebuild the .xml files from scratch.

The issues with "search for backups on startup" have not been resolved to my satisfaction either.

I have had the same experience as you, random, unwanted, population of old backup files on the backup and recovery tab, even with "search for backups at startup" un-checked (turned off).

James,

Thanks for your response. It's nice to know that I'm not the only one experiencing the frustrations of these issues. Considering exactly how frustrating these problems are --- and how effectively, in my opinion, they cripple the usefulness of the software --- I'm amazed that more time hasn't been invested in solving them.

My preferred way to solve these issues would, of course, be to do away with the indexing of backups completely. I'd love it if there was, somewhere in the software, an option to return to a True Image 9-like interface where all the backup tracking was done manually by the user. I'd much rather handle the important details of where my data is and what's done with it than to have an automated process do it. Automation is great --- sometimes. Unfortunately, I highly doubt such a feature will ever appear. I profoundly miss how well 9 used to work. In my opinion, that version was the pinnacle of this software. It hasn't ever been nearly that good since.

Christian,

Not that this will solve the lingering issue, but once ATI has started scanning, let it complete the search. It can last a long time in particular if your disk has a lot of disks and/or ZIP files.

So could anyone say whether Acronis are trying to resolve this issue?
Thanks!

Pat,

Thanks for your response. Unfortunately, it's precisely because there's a long time taken in searching that this problem is as irritating as it is. It's not acceptable, in my opinion. I echo dadave's request for an update: Is this on Acronis's radar at all?

Thanks.

Christian,
Your problem is puzzling.
If you have the time, try a couple things.
Open the the scan setting in the top double cog wheel--upper right corner.
If scan enabled, the checkmark will be dark blue. If scan disabled, the checkmark will be greyed out.
If greyout out, click the checkmark ONCE to enable. and close TrueImage.
Open regedit (as administrator) and see if the scan settings changed to 1.
Eidt/modify the setting and change the /REG_DWORD 1 to 0 (it must be hexadecimal).
The final 0 setting should look the same in appearance as the other 0 settings in same setttings group.

To turn regedit as admin.
Start/programs/accessories/
Right click on Commnad prompt
Choose the Run As Adminsistrator option.

Once I have found the settings listing, I use the "Menu/Favorites and use the "Add to Fovorites" option so the setting is easy to find on future use.

In the 2013 version, I have not had a problem with the scan at startup. Sometimes, when I have done some tests and using the add to backup list, I do get the occasional unwanted scan but that is usually during the program and not at the startup of the program. The remove from list seems to work fairly well.

Is your install for all users?

Hi GroverH,

To try what you've suggested, I exactly replicated the steps I followed in my first post, up to and including step 10. Thereafter, I:

11) Checked on the status of the "Search for backups at startup" check mark; it was greyed-out;
12) Closed TI2013 and rebooted;
13) Went into RegEdit and verified that the "ScanComputerAtStartup" flag continued to be "0";
14) Started TI2013 again and verified that the check mark continued to be greyed-out;
15) Enabled the "Search for backups at startup" check mark as per your suggestion; it was set to the highlighted-blue state;
16) Closed TI2013;
17) Went into RegEdit, noting that, indeed, the "ScanComputerAtStartup" flag was now "1";
18) Manually set it back to zero;
19) Restarted TI2013 and noted that the check mark was once again greyed-out and that no backup scan began;
20) Once again set the check mark to the highlighted-blue state;
21) Closed TI2013;
22) Went into RegEdit, noting that, indeed, the "ScanComputerAtStartup" flag was now "1";
23) Started TI2013;
24) Noted that the check mark continued to be highlighted-blue and that a backup scan commenced.

Note that I run as administrator and that my install is default; I do not go into the advanced options option. The "Remove from the list" feature and its efficacy is moot; I don't want a list generated in the first place.

Christian,

I'm not sure where you are going with this thread.

This issue is not resolved in the current build of 2013.

According to your steps above in 20-24, you re-enabled the scan at startup and left the program set this way.

No matter what settings you use during install or afterward, True Image will at some (randomly) point re-populate the list with your backup files that it finds on your attached drives. This bug has not been squashed.

Chrstian,
Your step 18-19 completed my suggested testing which was to confirm that the registry settings were working.
As noted by my suggestions and by those of MVP James F, you want to leave your settings in the "do not scan for backups which is when the settings is greyed out or reg setting of hex 0.

James F and GroverH,

Thanks as usual for your thoughts.

Yes, I'm aware of how I left the software. Perhaps I should add that the final thing I did was to revert my OS to an older image on which 5551 was the TI version which was installed. I only installed 6514 as a test. I don't have "Search for backups at startup" enabled in that version.

In regard to where this thread is going, I want this issue on Acronis's "fix it soon" radar. I find it completely unacceptable that backups are searched for when that's exactly the behavior I don't want. How many more builds of TI2013 will be produced? Will 2014 soon be the supported version and will bug fixes then only be available to those who paid for 2014? That, too, would be completely unacceptable.

I agree with Christian S.

How do we get a reaction from Acronis on their priorities for fixing this bug?

It's going to be a month soon. Any comments from Acronis on this?

I am also experiencing a similar bug - This morning I made a full backup to an external hard drive and after the backup completed all other backups located on that drive were added to my backup list.

Search for backups on startup is not checked, and the registry value of ScanComputerAtStartup is correct at "0".

Is there another setting somewhere I am missing that might prevent this behavior?

Martin

Martin,

It doesn't seem to get any attention from Acronis, unfortunately. It's a brutal bug.

Hello everyone!

Sorry that answer took that long.

I have to inform you that to switch off automatic archive scanning you have to check two things:

1. As Mr. Schroeder already said, please take a look at registry key and value data here - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Acronis\TrueImageHome\Settings\ScanComputerAtStartup REG_DWORD entry and set value data to 0.

And one more thing: the xml file here - C:\ProgramData\Acronis\TrueImageHome\Database\archives.xml

on the top of the xml - ArchiveDatabase Flags="0" value should be = 0 not 1.

After that try to open True Image again and let us know please was it helpful or not.

Thanks for your attention and I apologize again.

Hi Sergey,

It would seem that little trick has solved the problem for me. Am I going to always have to go into the xml after every restore or will there be a fix for that? For the record, the xml setting had reverted to "1" on restoration of the test backup. I followed the steps I outlined in the very first posting of this thread when testing your suggestion, with the only change being that I checked the xml file before starting 6514 after the test backup and restore. It was after the restore that I found ArchiveDatabase Flags="1".

First: Thank you VERY MUCH for this. Second, do let us know if there's a "fix" coming so that we don't always have to "hack" our way into the xml.

Thanks again!

One more handy follow-up: The xml file trick actually solves the backup search problem in build 5551, too.

I still have one older xp machine. Where do I find this xml file, or otherwise the relevant setting?

Thanks.

I thought I was the only person on the planet still running XP.....

I found the file here:

C:\Documents and Settings\All Users\Application Data\Acronis\TrueImageHome\Database\archives.xml

Don't know what the relevant setting is but I found this:

<ArchiveDatabase Flags="0" generator="1336" ver_major="1" ver_minor="4">

Yes, Mr. Gross, you're absolutely correct. Thanks for your cooperation.

I have to inform everyone about this issue that that is normal behavior actually, "by default". I explain - after each restore program needs to search and find some old backups or I would even chains, for example you restored from one the backups in the chain previously created, but you've used only one of these backups and after restore we have to find another parts of this chain to make the whole chain functional.
And after FIRST Search value data became 0 again and you will not meet that problem until the next restore.

Of course I can image how annoying is this issue for you, and regarding this problem I apologize but I cannot give you any straight information about when something will change in it. It is some kind of special hardware behavior.

We can only hope for your understanding and we will be very glad and thankful if you let us know about your problems with that in the future.

Sergey,

AHHH! It's not a bug, it's a "feature". ;-}

Ok, ok, I just had to say that. In all seriousness, your explanation makes sense. Unfortunately, there seems to be a communication problem between the development and coding team, and the user. It seems pretty clear to me that when "Search for backups at startup" is NOT selected, that a backup search will NEVER commence. I highlight that the menu doesn't say "Search for backups at startup under only certain circumstances". Not searching is not searching. There's no implication that certain scenarios will be exceptions which, when entered, will enable the software to search.

It's pretty clear: The user who doesn't select the "Search for backups at startup" menu option does not want True Image to search for backups EVER.

It's Acronis's prerogative, I suppose, to outline the circumstances under which backup searches will occur and implement its software in light of these stipulations. It would benefit everyone, though, if these circumstances were made glaringly clear and that the menu options were a little more forthright. Knowing what we know now, my whole thread title would have been different, reading something like "How do I stop True Image from searching for backups after a restore?" Of course, we've got a (crude) answer to that now, but things might have been a little less frustrating for many of us had we been clearer on the behavior from the outset.

Now, with all do respect, if someone can show me where, in recent documentation, the "Search for backups at startup" behavior was described as you, Sergey, have, then I'll eat my shorts and settle in gracefully for the well-deserved volley of shouts to read the manual. As it stands, though, I don't think this behavior was documented anywhere.

To make a long story short, it is my opinion the Acronis ought to implement a setting whereby searches never occur, ever, no matter what. Any readers of this thread that agree with me are invited and encouraged to voice their opinions as such, I think.

Thanks again for your time, folks.

Christian Schroeder wrote:

To make a long story short, it is my opinion the Acronis ought to implement a setting whereby searches never occur, ever, no matter what.

I agree completely. The program should never add backup tasks to the list unless the user explicitly requested the search. Random searches/list increases still occur even with the latest version and the search was not initiated by the user.

Also, on the restore of a backup, the restore should assume the settings that were in effect at time of backup. The backup program should not be changing any setting that would cause the listing of backups into the main GUI if that listing was not there at time when the backup was created. A restore should be a restore---no changes. If the program needs to make internal adjustments which does not involve the listing of backups, that is understandable but not understandable if the display shows a listing of tasks not requested by the user.

Here is some past discussion on this topic. Random unrequested backup additions to the list still occur even using the latest release in both XP Pro and Win7-64.
http://forum.acronis.com/forum/33491

Seconded!

Agreed, fix this!!

I immensely agree. One should not have to search through many forumposts to 'really' disable the auto searchfunction through reg and xml hacks,
when there is an option in the software that states 'turn auto search off'! If it still searches (even by design) than to the user it still is a bug.
Please give option to really prevent search. Many users know what they are doing and don't want this.

TI is still a good enough tradeoff between disaster and functionality, but I hope Acronis keeps improving user experience, because I've had many hours of annoyance with them. Fortunately they also saved my butt many times, so, yeah...

Posting your comments into this posting has no guarantee of being seen by Acronis support or development personnel. You may want to add your comments into the feedback area or the future options suggestion.
Post #21 above lists a prior discussion on this topic and comments by Acronis.

http://forum.acronis.com/forum/35369
or
http://www.acronis.com/support/feedback.html

Hi GroverH,

I noticed that you made reference to this discussion in a post in the future suggestions discussion. I think we all appreciate that very much. I hope this doesn't fall on deaf ears at Acronis. I think users who are annoyed by this problem should continue to post their opinions here as it will make for a great means by which to assess exactly how many people are bothered by it. Now that it's referenced in a place Acronis looks, perhaps this discussion and "log" will have some effect. I further think that users ought to to take advantage of that feedback link that you provided. It takes just a moment to file feedback directly to Acronis! The more Acronis knows of this the better!