Acronis CPHO Build 40173 intermittently not properly loading with Windows 11
Windows 11 22H2 Build 22621.963 Begun sometime after Acronis CPHO Build 40173. Acronis intermittently will not properly load. I suspect the problem may lie with CyberProtectHomeOfficeMonitor.exe?? Systray icon does not load, and I happen to know when the problem occurs because I monitor CPU temp and when temp is above normal at after Windows start up, every time it turns out Acronis has not loaded properly...as if trying load but can't quite get the job done? A quick restart of Windows and Acronis loads properly. I have nothing new except for whatever housekeeping Windows 11 does periodically. This is getting annoying. Help.
Thank you! I will follow your suggestion and see if it helps.
BAD NEWS! Unfortunately --- a clean reinstall of Acronis CPHO Build 40173 did NOT resolve the issue. Even as I type this, apparently some parts of the program are unable to properly start up with Windows 11....as if stuck and trying because I note process [CyberProtectHomeOfficeMonitor.exe] in Taskmgr active and that's why my CPU temp is not normal after all of Windows loads. Once I do a restart of Windows, pretty sure that will clear the way and Acronis will load properly. Again...this did not happen in build before 40173 (if that has anything to do with it?).
I would recommend raising this direct with Acronis Support so that they can investigate what the cause may be?
You might try running the Windows system file checker to check for any corrupted system files. Using and admin command prompt type:
SFC /Scannow
This might take a while to complete. If errors and found and corrected you will be informed of that. If you get such a message then run the command again and again until you are informed that no corruption is found.
Only as a very temp "fix", I've disabled CyberProtectHomeOfficeMonitor.exe from starting up with Windows. All is quiet.
I will attempt to reach out to Acronis Support directly. Thank you!!
@Enchantech Thank you! I do this rather regularly and no corruption. In fact, Windows 11 has been on its best behavior in a good while...except for CyberProtectHomeOfficeMonitor.exe "occasionally" not loading properly. If it weren't for HWinfo64 monitoring CPU temp, I wouldn't have been suspicious until it was time to do a backup. I've written twice directly to SUPPORT and the second dispatch included Acronis SystemReport and an uploaded copy of the file CyberProtectHomeOfficeMonitor.exe. Yesterday I was finally contacted by a human being from support who wanted to start all over with screenshots of this and that, and some process file, and visual proof that Windows Defender/Malwarebytes are disabled, etc, etc. I had already stated that I'm NOT receiving any error messages (not even in Eventvwr). I blame myself, really. I just don't have the patience for this rigmarole. I will just live with the problem - 1. or 2. I can manually disable the loading of CyberProtectHomeOfficeMonitor.exe. My bet is this problem will eventually self-resolve either with the next Windows update or with the next build of Acronis CPHO. Again...thank you all and Happy Holidays and Merry Christmas!
bcool,
This is an educated guess on my part however, the process CyberProtectHomeOfficeMonitor.exe is akin to the previous TrueImageMonitor.exe process. Both of these use network port 58101 to communicate with Acronis servers while the process runs.
I suspect that during this communication period many things are going on at once which contribute to your high CPU temp and usage while the process does its thing. My theory is that a scan and update to malware detection files is occuring as well as system disk scanning for a number of things like location of backup files and those files status, and who knows what else is happening.
My suggestion here would be to allow the process to run and do not use you computer until it has finished. This may take a long time if the process has never completed before which appears to be the case here. Once the process completes and CPU usage a temps return to normal levels you likely will not see this behavior again unless your computer remains unused for an extended time period in which case the process will need additional time to catch up to the current date.