Skip to main content

2010 Home remains in memory when closed

Thread needs solution

When closing Acronis it remains in memory avoiding a new acronis launch until it is killed with Task Manager. It is last version (6.053), at least the last version I have in my Acronis web page.

I attach a Threads capture if this can help to solve this. It's running under Windows 7 x64 RTM (Full patched). It seems Acronis is waiting some event in order to close itself...

Attachment Size
Capture.PNG 79.78 KB
Capture1.PNG 45.44 KB
0 Users found this helpful

Same problem here. ATI 2010, build 6053, Win7 64-bit.

UI goes away, but the TrueImage.exe *32 process remains until killed. Happens every time, not intermittent.

I also have this problem with the same build. Also happens every time. Killing the process and it restarts ok until closing again.

Reattempting to run the application initiates additional instances of TrueImage.,exe which also remain running.

Win7 Pro 32bit, ATI 2010 6053

EDIT: I decided to try and install the SnapAPI 503 drivers as mentioned and it appears (so far at least) to have solved the problem.

Yep, I have antoher related problem: when running, Acronis goes to 100% CPU usage.

In my case 25% because it is a Q4 processor. When closing it goes to 0% but remains in memory.

Snap Api: I think installing a patch for a internal windows stuff is a wrong solution. Acronis MUST solve their internal problem instead of patch windows.

However I'm going to test the Snap patch.

Snap API does not solves my issue.

It still uses 100% CPU and remains in memory.

Any other ideas?

Attachment Size
15404-86845.PNG 260.15 KB

Hello all,

Thank you very much for reporting the issue to us.

As soon as we found the first issue with this situation, when trueimage.exe process remains started even when the application is closed, we have reported it to our QA department. This task is now under investigation, I will keep you informed.

Please feel free to ask me if you have any additional questions.

Best regards,