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
  • I scripted some of the process if this will be helpful to anyone.  Just simple bat files for Win7.

    Log in as admin in safe mode and run bat file with these commands:

    sc config SAVService start= disabled

    sc config "Sophos AutoUpdate Service" start= disabled

    shutdown -r -t 0

     

    After reboot login as admin and run bat file with these:

    net stop wuauserv

    wusa.exe /uninstall /kb:4493472 /norestart

    sc config SAVService start= auto

    sc config "Sophos AutoUpdate Service" start= auto

    shutdown /r /t 0

     

    Stopping the windows update service may not be necessary in that second set of commands but I find that manual installation of OS updates is faster using that so I used it here.  There is a /quiet switch available for wusa.exe which you may want.  This command as given here asks you to confirm you want to remove the update (after working on it for some minutes) which of course you do but in the event it doesn't find it, this version tells you that too, whereas I am not sure the /quiet switch would.  I technically also use a pause command right before the reboot in mine so I can verify everything seemed to work correctly before I let it reboot.

    As stated this is for win7, if you wanted to use it on a different version of windows or windows server you could just change the problematic KB number to whatever is appropriate for that version.

  • Hello all,

    just in case someone is still struggling with endpoints running but showing errors like no On-Access scanning, update errors, SAV seemingly not installed, ... Running means at least being able to boot completely.
    I noticed that the updating errors were mainly caused by savservice.exe taking a long time to start (>15 minutes and even much longer). As our endpoints check for updates every 10 minutes I thought I should give increasing this interval a try. I put the mentioned exclusion for the SAV folder in place (can't say if it is needed), increased the schedule to 1 hour and waited. All affected machines (Win7, Win10, Server2k8R2) recovered without any other intervention. Can't say if they will also reboot without a problem but I assume they'll do.

    Christian

  • Can you explain how to extend the update check? Thanks!

Reply Children
No Data