Skip to main content

After updating to Build 6559, the TrueImageMonitor.exe process does an APPCRASH upon boot.

Thread needs solution

Ever since I updated to the latest build (6559) the TrueImageMonitor.exe processing aborts with an APPCRASH (see attached screen shots).  I've done a system report, also attached.

Attachment Size
acronissystemreport.zip 11.36 MB
timonitor_1.png 44.49 KB
timonitor_2.png 46.02 KB
0 Users found this helpful

Mark, thank you for your forum post and the information attached.

I would recommend performing a clean install of ATIH 2016 build 6559 in order to eliminate any possible cause due to corruption or a bad file etc in the application when it was upgraded.

To do this, uninstall the program via the Control Panel (or use an uninstaller such as Revo).

Run the Acronis Cleanup Tool (link in my signature below), then restart the computer.

Reinstall the ATIH 2016 software (download a fresh copy from your Acronis Account if needed or if you don't have the 6559 build version installer).  Run the install as an Administrator (right-click on the installer to take this option).

Note: The cleanup tool will remove all your backup tasks and task history.  If you want to protect this information, then open C:\ProgramData\Acronis\TrueImageHome\ in Windows Explorer - this may be hidden on some systems - if so, go to the Folder option in the View pane and enable hidden files & folders).

Save a copy of the Database and Scripts folders to another location to restore back later.

Note 2: In order to restore the above folders & contents, you must stop all Acronis Services & Programs else you will encounter locked files in the Database folder.
 

http://forum.acronis.com/de/forum/9223#comment-23308

It is not a requirement to run, try disabling in msconfig or in Win10 taskmanager startup.  If functionality of the application is still acceptable to you, you can leave as is after that.  

Otherwise, once booted into Windows, you can manually try launching it and see if it still crashes as well (C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe).

If it runs then, perhaps something else is preventing it from loading at startup and it needs a delay or could put a shortcut on the desktop to manually run, or create a .bat file with the executable and tell it to run with Windows scheduled task at logon (which would occur hopefully after whatever may be blocking it from running at startup now... assuming it runs when you manually launch it after Windows has started up and has had some time to settle down).

Tried running the object manually and it failed the same way...

However, when I looked at the icon I noticed that the little shield (ADMIN bit set) was "missing", but was evident on all the other object files.  So for a wild guess, I altered the properties to "Run as Administrator" and "lo and behold" it started.  Rebooted my P/C and the object started, normally, as it was supposed to.  At this point, it would be my conjecture that the installer, for the 6559 update, is not setting the run bits correctly for Windows7 enviroments.

Mark,

That's very interesting.  Please if you have a moment, send your results to Acronis Support.  The best way to do this is by using the in app Feedback option which you will find in the Help section of the app (left side of GUI open book icon).  Provide a brief description of the occurence and include your attachments posted above.  The feedback will include another System Report and you should send both and I would mention that and why (one of error and one post error) in your description.  You should also reference this Forum thread.

Support needs to see this, there have been a good number of reports of crashes of the app after upgrade and I think your idea of the installer not performing as it should is probably accurate so engineering needs to have a look at that and your information will get them a long way in doing so.

Thanks for posting and glad to hear you got it sorted out.

Hello, Mark.

Have you by any chance already updated to the latest build - 6569? And if so, is the issue still there?