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

Reply
  • 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

Children
  • 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 Ted Bundy,

    Is this a new installation you are referring to,  or has the issue started all of a sudden?

    If the issue occurs while installing Sophos:
    Is that key present in your system? Was there a previous installation of Sophos?

    If yes to either, please perform a full backup of the registry and manually remove the HitmanPro entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HitmanPro.Alert. I would also recommend to look for any other hitmanpro keys under the uninstall location as well, and remove them.
    After that, re-try installing Sophos. 

    If the problems persist (or the above steps do not apply, and rebooting does not help), you may need to file a case with support and provide SDU logs to see what may be blocking hitmanpro from installing.
    I can also take a look at your SDU logs if you would like to DM those to me first.

    Regards,

  • 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,

  • No it's not a new installation. It's a broken installation. So i completely uninstalled sophos & reinstalled. The continually reboots is because that key was missing! 

    I manually created the key and the continual reboots have now stopped.

  • I have around 100 of these errors - Failed to install hmpa64: a reboot is required before the installation can succeed.

    Have tried numerous reboots, reinstalls, turning tp off and updating from the client. 

    Uninstall and reinstall is the only thing that seems to clear it.  Although I still have to manually acknowledge the error in the Console.

    Seems a bit drastic.  Does anyone know of a quicker or easier fix.

  • Hi NikkiR,

    Please have a look at my response here and let me know if any of that makes a difference for your issue.

    Another suggestion would be to look at your registry for any pending file rename operations.

    Can you please provide more info regarding any Hitman Pro errors in your AutoUpdate log?

    Regards,
    Barb.-

  • We are looking at getting intercept x licence refunded, quicker than re-installing on 80 machines. 

  • Hi ChrisWhiting,

    Understood. If you change your mind, or have any other questions, please do not hesitate to reply here, or send me a PM. 

    I am very sorry for any inconveniences this may have caused. 

    Regards,