multiple processes continue after closing program
I've noticed that after closing TI there are three copies of "truimage.exe *32" still active in the process tab of Windows task Manager. They are using cpu time but nothing seems to be happening. Is this normal and why is it happening? Thanks
If you find the GUI won't open kill two of the processes in Task Manager.
Thanks Colin.
Pat
I'm not using either and I've done some further testing and found that at times after doing a number of operations the "truimage.exe *32" process/es don't terminate when I close the program. The operations are apparently finished from the indications in the GUI but the processes continue after closing the program.
I have the exact same problem.
A repair install of 2013 might solve whatever it is that is causing the two GUI entries.
Colin, do you mean to say the "two processes in the Task Manager"?
Nothing is showing as running in the Windows GUI, but multiple rows of TrueImage are all churning away in the Task Manager Processes tab
Colin, do you mean to say the "two processes in the Task Manager"?
Nothing is showing as running in the Windows GUI, but multiple rows of TrueImage are all churning away in the Task Manager Processes tab
Yes in Task Manager, delete these and the GUI will then start when clicked.
I've tried a complete reinstallation many times and it works for a while then The program breaks and hangs up with the please wait sign.
In reply to Jacqueline Hill's, me as well.
Using Process Explorer I can see the TrueImage.exe process using around 24% CPU time quasi permanently.
And chunks of 45s of I/O at 40M/s (mostly reading) spaced every 15s.
I put some screen shots in attachment.
Logging off then on do the job though.
Did someone find a solution not mention in this forum thread since then?
Any fix on this? I can re-create this issue on ATIH 2014 as well
I see the same thing on ATIH 2014. The TrueImage.exe process unloads the backups have completed prior to closing the window. If I close the window while a backup is still running or if I the console while a backup is running. No matter what, wait for backup completion or leave it open for 30 minutes post backup, closing the console results in the TrueImage.exe process left running consuming 40-50% CPU. If I re-open the console a new process starts and is left open upon closing the console.
Once the console process is orphaned, the only way to clear the processes are logging off or killing each process via task manager. This is running on Windows 7 64 bit, I have disabled my AV and as many other processes as possible
You might consider adding a batch file to the TrueiImage Post Command function.
The batch file would execute the shutdown command instead of using the TrueImage shutdown.
Many others have found this works.
Click on signature link 1 below and browses to index item #3-RA.
I was not trying to shutdown my computer after the backup completed. The issue I have is if I open the ATIH 2014 console while a scheduled backup is running to check the status of the job, after closing the console the "trueimage.exe *32" process continues to run consuming both CPU and memory resources even after the backup job has completed. If I open the console again, another "trueimage.exe *32" process opens in task manager and stays active after closing the console.
It seems like once a "trueimage.exe *32" process is stuck in memory, any further copies opened will also orphan another copy of the "trueimage.exe *32" process.
I have uninstalled and reinstalled ATIH 2014, uninstalled, ran 2014 cleanup and re-installed, same issue.
I just tried this on a brand new VM and it doesn't occur. There must be something on my home system that is interfering with ATIH 2014 not closing properly. You can disregard this issue as it is specific to my PC.
Thank you any way
Peter
Peter, this is exactly the problem I have been having. Thank you for describing it so clearly. You are not the only one that is having it!
Wish you were alone Peter.. same multiple [trueimage.exe]s problem with ATIH2014 and WinXP.SP3 {huge groan}.
On another WinXP.SP3 computer everything runs fun.
The only difference between the bad computer ATIH2014 setup and the good one is, after install on the bad computer, I did a settings import of the good computer's settings export.
Woo-hoo found the problem!
For some ungawdly reason ATIH insists on searching your ENTIRE system for any/all TIB and VHD files. Upon finding a file of this type, it registers it to that Backup/Recovery list.
In my situation, there was a very old TIB (True Image Backup) file on a USB drive that [trueimage.exe] has a problem handling. Because of this anomaly, [trueimage.exe] just sits there trying over and over and over to read the errant file.. completely decimating CPU cycles.
When this errant file problem happens and you close [trueimage.exe].. [trueimage.exe] is NOT kind enough to close this search and register thread.. so it keeps on running.
Making matters worse, if / when you open [trueimage.exe] again.. [trueimage.exe] sees that the search and register process has not been done.. so it starts a whole new thread all over again. This new thread also hangs on the errant file.. and the CPU now takes an additional pounding.
The means to correct this problem is to either delete or rename (I add an extension.. eg. 'mybackup.tibsave') the errant TIB that is hanging the discovery process.
Tip1: Leave the ATIH2014 GUI running while you do this.. when you go to rename/delete Windows will not allow you, stating the file is in use - this is the file causing the hangup.
Tip2: Go to VoidTools.com and download "Search Everything". "Search Everything" is free and is an excellent utility. Once "Search Everything is installed it will index all of your files and give you the ability to search quickly. After "Search Everything"'s index is built.. search for *.TIB and all of your backups will appear. Rename the extensions of the TIB files found (eg. 'whateverbackup.tibsave'). Remember, if you have [trueimage.exe] running and it is doing file discovery, Windows will NOT allow you to rename the file that [trueimage.exe] is hung on. This un-renameable TIB is corrupt - Reboot and Rename -or- Delete it. Once you have eliminated the bad TIB, rename everything back to the way it originally was. NB: You can use "search Everything" to find all of the ".tibsave" files and then rename them to *.tib".
Thank you to everyone for writing.
B.
(WHY CAN'T THIS SEARCH BE A BUTTON CLICK OPTION?!?!?!?!)
VoidTools (Search Everything) URL:
http://www.voidtools.com/
Many thanks Bill
I felt complelled to reply to your post as I tried your advised solution which has worked perfectly and resolved my problem running Acronis Home 2012.
This issue has been bugging me for ages but only had time until now, to do work arounds and not look for a full on fix.
I found the files/folder that I couldn't rename so stopped all TrueImage.exe processes (2 instances running which were running at 25+ CPU).
renamed all suspected TIB files in one problematic folder then rebooted computer
Now no instances of Tueimage.exe running and no demon temp files being created any more, BONUS!!!
Now only one Trueimage.exe process running after Acronis is started, which when idle, nows run at 00 CPU as I would expect.
Now when I close Acronis, the Trueimage.exe process stops soon after in Task Manager, as I would expect.
AWESOME!!
Thanks again and wishing you the Very Best :)
Dave