Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 26 replies
  • Subscribers 20 subscribers
  • Views 99376 views
  • Users 0 members are here
Options
Suggested
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.

Howiedog

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

    In the scenario where there is an update to HMPA, but the computer has yet to be restarted you get in the log:

    "C:\Windows\Temp\Sophos HitmanPro Alert install log 20171122T230432.txt"

    a 2017-11-22 23:04:32.256 [11076:8656] - Beginning install
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate it is NextGen endpoint
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate the user is an admin
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate that HMPA is not pending reboot
    w 2017-11-22 23:04:32.256 [11076:8656] - Validation failed
    a 2017-11-22 23:04:32.256 [11076:8656] - Reboot required by execute step: Validate that HMPA is not pending reboot
    w 2017-11-22 23:04:32.256 [11076:8656] - Failed step: Validate that HMPA is not pending reboot, rolling back previous steps
    a 2017-11-22 23:04:32.256 [11076:8656] - Rolling back step: Validate the user is an admin
    a 2017-11-22 23:04:32.256 [11076:8656] - Rolling back step: Validate it is NextGen endpoint
    w 2017-11-22 23:04:32.256 [11076:8656] - Failed composite step
    e 2017-11-22 23:04:32.256 [11076:8656] - A reboot is required before the installation can proceed

    You get a popup saying the computer needs to be restarted.



    HMPA upgrades work by setting up pending rename operations to delete the existing files and copy the new ones into place on restart.  

    Regards,

    Jak

Reply
  • 0

    In the scenario where there is an update to HMPA, but the computer has yet to be restarted you get in the log:

    "C:\Windows\Temp\Sophos HitmanPro Alert install log 20171122T230432.txt"

    a 2017-11-22 23:04:32.256 [11076:8656] - Beginning install
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate it is NextGen endpoint
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate the user is an admin
    a 2017-11-22 23:04:32.256 [11076:8656] - Executing step: Validate that HMPA is not pending reboot
    w 2017-11-22 23:04:32.256 [11076:8656] - Validation failed
    a 2017-11-22 23:04:32.256 [11076:8656] - Reboot required by execute step: Validate that HMPA is not pending reboot
    w 2017-11-22 23:04:32.256 [11076:8656] - Failed step: Validate that HMPA is not pending reboot, rolling back previous steps
    a 2017-11-22 23:04:32.256 [11076:8656] - Rolling back step: Validate the user is an admin
    a 2017-11-22 23:04:32.256 [11076:8656] - Rolling back step: Validate it is NextGen endpoint
    w 2017-11-22 23:04:32.256 [11076:8656] - Failed composite step
    e 2017-11-22 23:04:32.256 [11076:8656] - A reboot is required before the installation can proceed

    You get a popup saying the computer needs to be restarted.



    HMPA upgrades work by setting up pending rename operations to delete the existing files and copy the new ones into place on restart.  

    Regards,

    Jak

Children
No Data
Unfiltered HTML