Salta al contenuto principale

Trueimage.exe and scheduler Problem

Thread needs solution

Hi,

every time I boot my PC, a trueimage.exe starts running and consumes about 20% of my CPU and is doing someting for about 5 to 10 Minutes. The application itself does not start, but just a service, visible in the taskmanager and with procmon.

I didn't schedule anything, but that application blocks my PC nevertheless. As I dared to stop the new sheduler the application informs me that I stopped the scheduler and that I did wrong and should activate it again striaght away! ... no mom, why should I?

Anyway, trueimage exe does not care about that and runs everytrime after I boot my PC again. So I couldn't see how to stop that from the application, and killed it with the taskmanager ... silence :-)

What does the service truimage.exe do after the start and how can I keep it from starting and blocking my PC?

To the developers: As I willingly stoped the scheduler, you don't need to annoy me with an exclamation mark in the Application that it is in fact deactivated and offer me to revise this !

I DON'T WANT TO USE THE SHEDULER, got it?

regards

Andreas Wieneke

0 Users found this helpful

Andreas,

I assume you are not using the Non-stop backup option and also not using the Sync-Agent option. If true, stop both services and change the properties on both to "Manual".

I also assume that you have 2012-7119 installed and do not need the "Scan for backups at startup" option which can be disabled.
Check this link and change the scan to disabled or unchecked.
http://forum.acronis.com/forum/31895

Reboot your computer and see if the issue remains. The scheduler service will be started automatically via defaults.
---------------------------------------------------

If that did not cure the issue, then search for the "script" folder--probably located at one of these spots

win7- "C:\ProgramData\Acronis\TrueImageHome\Scripts"

XP Prp "C:\Documents and Settings\All Users\Application Data\Acronis\TrueImageHome\Scripts\"

Temporarily move all the scripts into another folder (any name) and reboot and see the problem continues.

Afterwards, move the scripts contents back into the original scripts folder.

My thinking of the scripts folder is that you may have some scripts or even rogue scripts which may be attempting to validate each time you boot.

Let us know the whatever results you get.