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

Microsoft April 9 2019 update and Sophos Windows Server 2008 hanging issue.

 Our Windows 2008 servers suffered the problem of hanging while booting after applying the Microsoft April update (KB4493458).

Following the Sophos article:

https://community.sophos.com/kb/en-us/133945#Enterprise%20Console

I can confirm that these affected servers have the Recommended version of Sophos Anti-Virus for Windows as 10.8.2.363 VE3.74.1, but they still hang for approximately 30 minutes when starting up on "Applying Settings".

I have found the only way to eliminate this is to either remove the Microsoft update, or change the Sophos services to manual so that they don't start, then the server starts normally.

I thought that, according to the above article, that the problem was resolved with this version of Sophos.

Anyone else have this issue still?

Thanks,



This thread was automatically locked due to age.
Parents Reply Children
  • Hi Christian,

    Thanks for your assistance.

    I think the May Rollup for 2008 was KB4499149 and this update was also removed from this server.

    As I said previously, as soon as I apply the April one to the server, it causes the hanging issue and if I remove it, or disable Sophos, it's back to normal.

     

    Stuart

  • Hello Stuart,

    KB4499149 [...] was also removed
    It was already installed when the issues surfaced and both it and the April Rollup have been removed? It's a little bit murky and considering that it affected more than one vendor it's still not clear what contributes to the hang. When I applied the May Rollup to a Win7 Enterprise it seemed to be stuck (after the usual Reboot to install) at 30%, no change for more almost ten minutes, I was about to force it down when it suddenly rebooted by itself and afterwards everything was fine. No issues since then.

    Christian

  • I don't know if it makes any difference, but it is only affecting our Windows 2008 servers, not the 2008 R2 ones.