Skip to main content

Acronis True Image process constant high CPU usage. Any idea how to fix this?

Thread needs solution

Hello:

Please take a look at the screengrab attached to this post. As you can see the Acronis True Image process constantly uses 16% CPU on my desktop and high disk usage. Note that the backup was not going on at that point in time. This happens if I start this process: "C:\Program Files (x86)\Acronis\TrueImageHome\TrueImage.exe" and can be stopped only if I kill that process (like I showed in the screengrab.)

Any idea how to fix this?

PS. I have version 2014 installed.

Attachment Size
acronis_process_cpu_hog.gif 576.32 KB
0 Users found this helpful

I would advise using Windows chkdsk /r command on the disk to check for and repair errors on the disk. If you have hidden partitions on your disk as view in Windows Disk Management then you will need to temporarily assign drive letters to those partitions and run chkdsk /r on those as well.

Link to chkdsk command: https://technet.microsoft.com/en-us/library/bb491051.aspx
The chkdsk command should be run from a command prompt with admin privileges.

Link to Assigning drive letters Win 7: http://windows.microsoft.com/en-us/windows/change-add-remove-drive-lett…

Thanks for your reply, but just from curiosity, why would I want to run chkdsk? My disk works just fine. As you see in the task manager screenshot that I made the only culprit is the True Image UI client process that for some reason continues to use up CPU & disk even after I close it.

TI scans your hard drive as a normal part or its operation on your machine. If your disk has any errors on it such as corrupted file system errors or bad sectors these abnormalities may not be evident in day to day use but still do exist. If corruption does exist then this will cause TI to continue scanning your disk attempting to complete the read of your disk. What you see is activity from the app in task manager or event viewer even though you are not using the app. So running chkdsk can help in determining that corruption is not the case. It would also be wise to visit your drive manufacturer support site and download any diagnostic repair utility and run that as well as those apps sometimes find problems not detected by chkdsk. Another tool you can run is Windows built in system file checker. From an admin command prompt run the command sfc /scannow on your primary system partition and let windows scan itself for errors.

If the above finds no issues then you have another issue which can be investigated but it is best to cover the basic health of the disk and file system first.