Help "Down"grading to v8.0

I have made a few restores with 9.0 but when it completes successfully I always feel lucky. I want to revert to 8.0. I tried this before but I got odd behavior when using 8.0 that was probably attributable to going back in versions. The main problem was that the CPU would go 100% each time I ended the application until I killed the process.
I could use some advice on how to completely uninstall v 9.0 before I reinstall 8.0. I'm using WinXP SP2. Last time I used Add/Remove Programs to uninstall (restarted) then deleted the Acronis folders under both my profile and the "all users" profile. I ran into problems.
Where else should I look for vestiges of 9.0?

 

You have a few options.

1.) Use the Restore function of XP to go back to a day before Ver 9 was installed.

2.) Use a Registry cleaner to remove orphaned parts of the Registry.

3.) Use RegEdit to manually remove anything named Acronis from the registry.

Afterwards, you can then reinstall ver. 8.

 

Hello Bill U,

Thank you for choosing Acronis Disk Backup Software.

Please be aware that since most of the knows problems of Acronis True Image 9.0 has already been investigated and fixed, I would recommend you to use Acronis True Image 9.0. Especially since it works fine for you.

In case you encounter any problem while using the latest build (2302) of Acronis True Image 9.0 please report it on this forum or submit a request for technical support. We will certainly try to help you in resolving any issues.

If you want to go back to the older version of the program anyway then please do the following in order to uninstall Acronis True Image manually:

- Delete Acronis Secure Zone either through the wizard or manually;

- Delete "snapman" from the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} -> UpperFilters

- Delete "snapman" and "timounter" from the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} -> UpperFilters

- Run Device Manager and delete Acronis Image Archive Explorer;

- Delete "snapman", "timounter" and "tifsfilter" from the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

- Delete "TrueImage" value from the following registry keys:

HKEY_LOCAL_MACHINE\Software\Acronis\Autopart (can be absent)
HKEY_LOCAL_MACHINE\Software\Acronis\CDRecord
HKEY_LOCAL_MACHINE\Software\Acronis\Schedule2
HKEY_LOCAL_MACHINE\Software\Acronis\SnapAPI
HKEY_LOCAL_MACHINE\Software\Acronis\Snapman
HKEY_LOCAL_MACHINE\Software\Acronis\VBus

- Delete the Windows\System32\autoprnt.exe file, if it exists;

- Delete the following folders:

Program Files\Common Files\Acronis\CDRecord
Program Files\Common Files\Acronis\Drivers

- Download the schedmgr.exe file;
- Open the command prompt (Start -> Run -> cmd);
- Run the following command in the folder you saved the file to:
schedmgr service uninstall
- Open Task Manager and stop the following processes: schedhlp.exe, TrueImageMonitor.exe;
- Delete the Program Files\Common Files\Acronis\Schedule2 folder;

- Delete the desktop icon and Start menu shortcuts;

- Delete the Program Files\Common Files\Acronis folder;
- Delete the Program Files\Acronis\TrueImage folder;
- Delete the Program Files\Acronis folder;

- Delete "TrueImage Monitor" value from the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

- Delete the following keys in HKEY_CLASSES_ROOT:

.tib
.tis
tibfile
tisfile

- Delete the following registry keys:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\TrueImage

HKEY_LOCAL_MACHINE\Software\Acronis (you may need to grant full control permission to yourself to delete this key)
HKEY_CURRENT_USER\Software\Acronis

- Reboot the computer.

Install Acronis True Image 8.0 then and see if the problem still persists.

If the problem still persists then please download the latest version of Acronis drivers for Acronis True Image 8.0 and install it with disabled logging.

If that does not help then enable logging by running the Acronis drivers installation package once again, reproduce the problem and collect the c:\snapapi.log file.

Please also create Acronis Report and Windows System Information as it is described in Acronis Help Post.

Submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Alexey Popov

 

With all the reports of bugs, and the current level of user dissatisfaction, I'm very surprised to hear you say, "Please be aware that since most of the knows problems of Acronis True Image 9.0 has already been investigated and fixed, I would recommend you to use Acronis True Image 9.0." If, in fact, 9.0.2302 is at a level that Acronis deems acceptable, I'll surely be looking for a refund.

 

Alexey,
Thanks for the response, I'll make use of the directions. However I would NOT be doing this if v. 9.0 was "working fine" for me.
I have spent a significant amount of time troubleshooting and finding workarounds for software that I just upgraded to. With build 2302 I'm at a point where:
I can schedule a backup and it runs sometimes and sometimes it doesn't. I've chosen not to troubleshoot this, I am using a different backup solution.
I make a boot partition image and it doesn't verify under Windows but it does with the boot disk. So do I trust it to be there when I need it, or not?
I go to restore an image that I've restored previously and it stops halfway through and tells me that it's corrupted. But the third time I tried it, it worked.
I go to restore an image and I choose verify first. Halfway through the verify it tells me that it's corrupted but inexplicably it has already destroyed the boot partition.

I now find myself booting from my v. 8.0 bootdisk to make "emergency" backups because I'm not sure if I'll be lucky the next time I use v. 9.0. Any application that begins by deleting the boot partition of my hard drive needs to have my confidence that it will finish the job. I don't trust v. 9.0, so I'm going back to what I can trust. I may or may not try v. 9.0 again in the future.

Thanks again, Bill

 

Hello Bill U,

I'm really sorry that you displeased with the work of Acronis software.

Nevertheless, if you will decide to troubleshoot any of the problems you listed above then please do the following:

- Download schedmgr.exe application;

- Open the command prompt (Start -> Run -> cmd);

- Run the following command in the folder the schedmgr.exe file was saved to:

schedmgr get report > schedreport.txt

- Collect schedreport.txt;

- Run Acronis Schedule Manager program (schedmgr.exe) once more;

- Issue the following command:

set logflags support

- Schedule backup creation once again;

- Wait until the scheduled backup will fail;

- Collect the log file schedul2.log that is placed in the \Program Files\Common Files\Acronis\Schedule2 folder;

Please also create Acronis Report and Windows System Information as it is described in Acronis Help Post.

Submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with the solution.

First of all, please make sure that you use the latest build of Acronis True Image 9.0.

If the problem still persists with the latest build of Acronis True Image 9.0 then please provide me with the following information:

- Where do you store this particular image?

- Describe actions taken before the problem appears step-by-step.

The point is that Acronis True Image 9.0 created incorrect image restoration scenario: it deleted partition first and only after that verified the image. This problem has already been investigated and fixed since build 2290. Please accept our apologies for the current inconvenience.

Thank you.
--
Alexey Popov