Win 7 fails to boot after use of Cleanup Utility
I am trying to get rid of traces of Trueimage Home 2011 as they are stopped the installation of other software.
I did the normal uninstall and found some Startup Services remained: Scheduler2 and Timemounter Moniter. I have disabled these.
I then used the latest Cleanup Utility, with Devcon.exe installed, and followed the script to remove the registry values for snapman*, tdrpman*, timounter in the registry references given.
When I rebooted the boot failed.
Windows 7 diagnostic could not find a root cause, so I had to go back to previous restore point.
Back to the start!
Is there a solution to this, please?
- Accedi per poter commentare
I have no system image as Windows Backup has recently developed different errors. Files are backup, though.
When rebooting after using the Cleanup utility the Windows 7 flags logo froze and then I got a blue screen which passed too quickly to read. Then I was asked to restart in a diagnostic mode.
- Accedi per poter commentare
I meant a backup image with TI. You can boot to the TI CD and create one if you don't want to (or can't) create one in Windows. I recommend creating a backup image in case you run into further problems and System Restore doesn't work.
On the Windows "Safe Mode Menu" there is an option to disable the automatic reboot on errors. This would allow you to see the BSOD code. I suspect that the problem is the snapman driver not being removed properly.
- Accedi per poter commentare
I don't have a TI image backup or any TI software installed. I still have my original downloaded Trueimage Home 11 installation programme but I am unwilling to reinstall unless there is no other option in trying to clear out TI traces.
I can locate the snapman driver.
Should I disable (rename) the driver and then run the cleanup utility, or run the cleanup, check for the driver, and if there rename to disable it and then reboot?
- Accedi per poter commentare
Further to my comments: I have rerun the cleanup utility and the looked at the Registry to see what it had done. There are still lots of references to Acronis there.
I noticed that the Runonce entry to delete the drivers had "system" in the path and not "System". I corrected the capitalizaion and continued with the cleanup process.
On reboot this time there was no problem and the drivers have been removed.
I suppose I will have the cleanup the rest of the Registry manually to remove other Acronis references.
Thanks for your comments.
- Accedi per poter commentare