Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 15 subscribers
  • Views 5815 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: general error and machines not updating

Simon Peart

New to Sophos, migrating to Sophos Central from Kaspersky Endpoint Security, and quite a few of our machines seem to have issues with 'failed to install hmpa64: general error'.

The quick and easy resolution to this seems to be to get the machines having the issue to do a restart, however, it has to be a restart and doing a shutdown and a switch on doesn't make any difference.  

Is there a reason why it has to be a reboot and not a shutdown/switch on and once we've got everyone to do a restart, is this issue likely to come up again?



This thread was automatically locked due to age.
Parents
  • 0

    Hello Simon Peart,

    why it has to be a reboot and not a shutdown/switch on
    in a nutshell and simplified: HMPA injects a DLL into the processes it protects. It can do so only when a process starts. When Windows' Fast Startup is enabled the system isn't actually shut down, the user is logged of but everything else goes into hibernation. System processes aren't restarted in this case. Consequently HMPA can't protect them and like with some Windows updates a reboot (or a "real" shutdown and subsequent boot) is required to complete installation or (is this issue likely to come up again? - yes) an upgrade.

    Christian 

Reply
  • 0

    Hello Simon Peart,

    why it has to be a reboot and not a shutdown/switch on
    in a nutshell and simplified: HMPA injects a DLL into the processes it protects. It can do so only when a process starts. When Windows' Fast Startup is enabled the system isn't actually shut down, the user is logged of but everything else goes into hibernation. System processes aren't restarted in this case. Consequently HMPA can't protect them and like with some Windows updates a reboot (or a "real" shutdown and subsequent boot) is required to complete installation or (is this issue likely to come up again? - yes) an upgrade.

    Christian 

Children
  • 0 in reply to QC

    Thank you, did a batch file that runs reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /v HiberbootEnabled /t REG_DWORD /d 0 /f, this should turn it off.

    Will see if it works tomorrow, if it does, i'll roll it out to all of our clients via group policy.

Unfiltered HTML