Windows Update Hall of Shame
The Windows Update Hall of Shame
Occasionally, Windows updates can be really bad and really screw up your computers. Here's my list of the worst offenders. These are only bad because they really screw up when Sophos Antivirus is installed. Some of these are showstoppers for Microsoft Exchange.
KB4493472
This update can really interfere with Sophos antivirus. See the related story. https://community.sophos.com/products/endpoint-security-control/f/sophos-endpoint-software/112101/sav-service-hangs-after-installing-kb4493472 If you have Windows 7, or Windows Server 2008, expect real trouble if you allow this one.KB4499164
Once again, more issues caused by an update rollup. Causes Sophos Antivirus protected machines to hang and freeze. It appears that once again there are conflicts with Sophos and the most recent (MAY) patch Tuesday from Microsoft. www.theregister.co.uk/.../ "Its advice on what to do is pretty blunt: uninstall the Windows update. Specifically, revert KB4499164 (May's full-fat Patch Tuesday) and KB4499165, the security-only update. As regular readers know, the latest Patch Tuesday is intended to mitigate a pretty nasty vuln (CVE-2019-0708) which permits unauthenticated remote code execution through the medium of Remote Desktop Services. Sophos itself opined that it was "so serious that Microsoft has even released patches for its long-unsupported operating systems, Windows 2003 and XP"." Unfortunately, the new RDP worm bug needs this patch. See this: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708KB5007192
When applied to a Exchange Server 2016 with CU22 on Windows Server 2016, you will often find the IMAP service has failed frequently, and cannot be restarted. You have to reboot the entire server. Best to remove this update immediately.
KB4499175
A security only patch to fix the BlueKeep vulnerability. Get it from here: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4499175
FIPS Error on Exchange 2016 Due to Jan 1 2022 Update
Just as 2021 rolled over to 2022, we started seeing this on our Exchange 2016 servers. Read Peter Morrison's blog: this: https://petermorrissey.blogspot.com/2021/12/exchange-server-fips-fs-error.html and you will find out about "FIPS-FS Error 0x800706BE, 0x80010105" which causes the Anti-Malware module to fail and then messages get backed in the queue. While looking thru the Windows Application log, I found this on December 31, 2021 17:21 PST UTC-08 from source: FIPFS "The FIP-FS "Microsoft" Scan Engine failed to load. PID: 42960, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long." which appears to indicate an issue with the year 2022. As a result, the "Microsoft Exchange Transport" service failed. The temporary solution is to disable the AntiMalwareScanning service using the powershell script.
1) cd "C:\Program Files\Microsoft\Exchange Server\V15\Scripts"2) .\Disable-AntiMalwareScanning.ps3) open services.msc, then restart the "Microsoft Exchange Transport"
BlueKeep
Read about it: https://www.scmagazineuk.com/devastating-exploit-using-ticking-bomb-bluekeep-only-weeks-away/article/1587473Windows 7 for x64-based Systems Service Pack 1 | 4499164 | Monthly Rollup | Remote Code Execution | Critical |
4493472
| |
4499175 | Security Only |
bb
ReplyDeleteLooking for Comodo support, visit on sophos antivirus support
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteThis is a great post that you have shared with us. I appreciate you sharing such valuable information with us. If you use Sophos antivirus, and you are facing any kind of issue with it, then you should contact our Sophos Antivirus Support team.
ReplyDelete