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

SAV service hangs after installing KB4493472

Hello,

Last night one of my Windows 2008R2 servers hung after installing Microsoft patch KB4493472. After initial examination I discovered that SAV service was logging lots of error messages in event log. Event IDs : 7022 (service hang), 80, 81, 83, 85, 82, 566, 608, 592.

The server became unresponsive, no rdp, no file share access, Ctrl Alt Delete not working.

I rebooted the server in to safe mode and disabled the Sophos services. After this, I was able to reboot normally. Then I uninstalled Sophos, rebooted and tried to install again but this time the installation didn't complete and the server hang again. I rebooted again in safe mode, disabled services, rebooted and uninstalled sophos again. After checking the Windows logs I realised that the server had installed update KB4493472 last night. I uninstalled the patch, rebooted and installed sophos again. This time there was no problem.

Currently we are trying to unauthorise KB4493472 on our update system.

Is there any known issues with KB4493472 on Windows Server 2008R2?

Thank You.



This thread was automatically locked due to age.
Parents
  • Absent of any information from Microsoft, I took a different approach initially, and I'm seeing some other after-effects.  I've been studying the results with a site that I support.  Here are my observations.

     

    - Initially, I recommended not interrupting the apparent hang duing Windows startup.  It was painful to wait, but eventually, the update process completed.

    - Despite recommending not forcing the systems off, I've found that some users did force power off systems, which I believe delayed the process from completing.

    - Restarting after waiting resulted an additional extended startup.

    - When the system finally allowed access - two additional problems were observed - MS Office and Office-connected programs would hang or report not responding.  I also saw some problems with offline synced folders.  By "Office-connected programs", I'm referring to software that may share libraries with MS Office.

    - Running a MS Office Quick Repair restored proper operation to MS Office and Office-connected programs.

    - For the offline synced folders, this may or may not be a related problem, but I had to move the offline synced folders to another share because the original share was not accessible for one user.

Reply
  • Absent of any information from Microsoft, I took a different approach initially, and I'm seeing some other after-effects.  I've been studying the results with a site that I support.  Here are my observations.

     

    - Initially, I recommended not interrupting the apparent hang duing Windows startup.  It was painful to wait, but eventually, the update process completed.

    - Despite recommending not forcing the systems off, I've found that some users did force power off systems, which I believe delayed the process from completing.

    - Restarting after waiting resulted an additional extended startup.

    - When the system finally allowed access - two additional problems were observed - MS Office and Office-connected programs would hang or report not responding.  I also saw some problems with offline synced folders.  By "Office-connected programs", I'm referring to software that may share libraries with MS Office.

    - Running a MS Office Quick Repair restored proper operation to MS Office and Office-connected programs.

    - For the offline synced folders, this may or may not be a related problem, but I had to move the offline synced folders to another share because the original share was not accessible for one user.

Children
No Data