Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed to install hmpa64: a reboot is required before the installation can succeed.

Ok..on numerous PC's when I am in Cloud.Console are showing this error in their respective Events tab.

Although this is an Event, do the Clients ever get a notification that they need a required reboot?

I have Sophos on my own desktop and I don't remember ever seeing a notice about required reboot to complete install.

If they do NOT get a notice, then how are they supposed to deal with this?? Is it up to me as Admin to monitor these events and take the required action?

 

Tks



This thread was automatically locked due to age.
Parents
  • I have an endless reboot as well. 

    Executing step: SetRegistryValue(HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HitmanPro.Alert, 64, SystemComponent, 1)
    Failed to open Registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HitmanPro.Alert, error 2
    A reboot is required before the installation can proceed

  • I don't really understand why reboots are still a monthly thing. Most endpoint products don't need constant reboots these days. 

    Also why does the server product rarely need reboots even though its the same tech?

  • Hello LRB,

    Some component updates do require reboots, however you can control how/when you receive them, in order test and prepare for applying them. Please have a look at this document for more details

    Server and Endpoints update differently, as they use different versions of the software (Server Standard/Advanced VS. Endpoint Standard/Advanced) .  The options listed above should help you control the updates.  

    Regards,

Reply Children
No Data