Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 12513 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

Exploit Protection. Installed and yet keeps coming up with errors saying PC Needs restarting for Hitman Pro Install to work.

StephanieGelder

Hi.

Since Installing Hitman Pro/Exploit Protection.  I have lots of PC's coming up in my SEC 5.5.0 console with errors like this.

This PC had Exploit Protection installed two or three months ago.  I look on the PC and it shows it fully installed right click and update, does 8 updates happily, go into Sophos and it says Exploit protection is installed and yet I am still getting errors on the console saying it needs a reboot.  Is this because it's had an update that need a reboot, which it will get at the end of today, but if so then that's really annoying as these won't clear automatically and i'd need to spend my life keep looking at these meaningless errors just to check.

 



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

    Hello StephanieGelder,

    EXP is quite soft-spoken on the endpoint. For whatever reason it needs a reboot to upgrade (I see the previous 3.6.8 - guess it also says so on the endpoint) - so the error isn't meaningless. I'm not sure though whether it's that prominent (a 0x00000067) the first days after the upgrade became available. Didn't notice in the console when 3.6.9 came out - it just had rather friendly Restart required ... instead of Failed to install .... Wonder what's in the AutoUpdate Status history. 

    Christian

Reply
  • 0

    Hello StephanieGelder,

    EXP is quite soft-spoken on the endpoint. For whatever reason it needs a reboot to upgrade (I see the previous 3.6.8 - guess it also says so on the endpoint) - so the error isn't meaningless. I'm not sure though whether it's that prominent (a 0x00000067) the first days after the upgrade became available. Didn't notice in the console when 3.6.9 came out - it just had rather friendly Restart required ... instead of Failed to install .... Wonder what's in the AutoUpdate Status history. 

    Christian

Children
  • 0 in reply to QC

    About 10% of our devices have this same error!

    The PC's are shutdown at the end of each day and restarted in the morning. 

     

  • 0 in reply to StephanieGelder

    Hello StephanieGelder,

    what does the HitmanPro Alert install log in %windir%\Temp\ say?

    Christian

  • 0 in reply to StephanieGelder

    a 2017-10-31 12:07:56.378 [19972:17488] - Beginning install
    a 2017-10-31 12:07:56.378 [19972:17488] - Executing step: Validate it is NextGen endpoint
    a 2017-10-31 12:07:56.378 [19972:17488] - Executing step: Validate the user is an admin
    a 2017-10-31 12:07:56.378 [19972:17488] - Executing step: Validate that HMPA is not pending reboot
    w 2017-10-31 12:07:56.378 [19972:17488] - Validation failed
    a 2017-10-31 12:07:56.378 [19972:17488] - Reboot required by execute step: Validate that HMPA is not pending reboot
    w 2017-10-31 12:07:56.378 [19972:17488] - Failed step: Validate that HMPA is not pending reboot, rolling back previous steps
    a 2017-10-31 12:07:56.378 [19972:17488] - Rolling back step: Validate the user is an admin
    a 2017-10-31 12:07:56.378 [19972:17488] - Rolling back step: Validate it is NextGen endpoint
    w 2017-10-31 12:07:56.378 [19972:17488] - Failed composite step
    e 2017-10-31 12:07:56.378 [19972:17488] - A reboot is required before the installation can proceed

     

    I restarted the pc whilst I was there and it still did the same.  It ran it again with exact same messages.

    There is no other pending update / install on the PC itself.

    41 of our PC's have this error on the console.

  • +1 in reply to StephanieGelder

    Hello StephanieGelder,

    can't say what HMPA checks at the validation step - might or might not be the VolatileFlags.

    Christian

  • 0 in reply to QC

    DAMN, that worked :)

    So it was 32bit.  I went in and there were two Volatile Flags both set to 1.

    Changed both of them to 0. 

     

    I tried again no difference, but I then restarted the PC and restarting it with those set to 0 did it.

    But I have 41 pc's like this spread over 4 sites :(

     

    Hurrah, there is a fix, BOOO it's this.

     

Unfiltered HTML