For the second month in a row, McAfee and Sophos are having problems with the Win7/Server 2008 R2 Monthly Rollup and Security-only patches

Topic

New Reply

After the debacle last month, you’d think that McAfee and Sophos would’ve figured out a way to work with Microsoft’s monthly patches. Not so. Microsof
[See the full post at: For the second month in a row, McAfee and Sophos are having problems with the Win7/Server 2008 R2 Monthly Rollup and Security-only patches]

1 user thanked author for this post.

Elly

Reply | Quote

Replies

All fine on the Symantec side.

Reply | Quote

I have seen no problems with TrendMicro or BitDefender Free.

Reply | Quote

No Windows AV issues on hard metal installs:
MSE-Win7Prox86
Windows Defender-W8.1Prox64
BitDefender Free-W8.1Prox64

Windows - commercial by definition and now function...

Reply | Quote

I have Sophos Home Premium on 2 of my Windows 7 computers. I have no issues on these systems after installing the May monthly rollup. Last month Microsoft withheld the April updates on those system because of the problem then, even though Sophos Home Premium was not affected according to Sophos. Apparently Microsoft blocked all machines with Sophos installed, even when the specific Sophos version was not affected.

Reply | Quote

A lot of people complain about Norton.  I have it and use it all the time and never have a problem.

 

Reply | Quote

I get Norton via my ISP as part of my Internet Service subscription fee but I am only running it on one laptop out of the 4 that I own. It appears that my ISP failed to provide the proper install instructions for downloading once and installing that ISP’s Norton(5 device License version) across all of ny 4 laptops and I individually downloaded 4 different Norton install packages with 4 different licenses for my computers which I did starting with my newest laptop first and afterwards Norton prompty stealth uninstalled itself from my 3 older laptops.

So I’m running Microsoft Security Essentials on the older laptops. Both Norton(Symantec) and the ISPs that offer that ISP branded/bundled Norton Antivirus/Firewall variants need to hire the proper folks to document the nulti-device installation process and provide the proper downloadable Image file with detialed intructions on how to get Norton(5 device license) installed across up to 5 different devices.

The one thing that upsets me about Norton is that if you are running an older version that gets past its EOL, it will stealth uninstall itself with no notice or attempt to direct the user to download a newer version and my license should remain active as long as I’m with my ISP because the ISP’s branding is on the Norton Security Suite variant. So all that stealth uninstall Rudeness from Norton is what earns them disrespect. Also most Virus/Firewall software like Microsoft Security Essentials will animate the software’s trey Icon if that software is actively updating/doing whatever in the background but not Norton Securuty Suite. Microsoft’s security just needs to get a fuller feature set and a combined antivirus/firewall interface with options to warn the user if its actively blocking some attack via its real time protection. Norton has some nice warning settings for all sorts of events that may rate a popup warning from the Security Software.

Reply | Quote

Error on the Sophos page:

“Initial findings suggest that this relates to the below Microsoft Patches:

May 14, 2019—KB4499164 (Monthly Rollup)

May 14, 2019—KB4499165 (Security-only update)

We have currently only identified the issue on Windows 7 and Windows Server 2008 R2”

However, KB4499165 is a Windows 8.1/Windows Server 2012 R2 patch.

I think the KB is supposed to be KB4499175. However, I’ve just installed this patch onto a VMware VM running Server 2008 R2 + Sophos and not experienced any issues (Rebooted fine, not stuck at any stage).

2 users thanked author for this post.

Karlston, woody

Reply | Quote

This might be handy for the remaining McAfee users…

How To Uninstall McAfee Antivirus

Reply | Quote

I just want to know what change is so important it was necessary to fix on versions of Windows in extended release. What undocumented feature were these guys exploiting that is now being patched? Or what did Microsoft break because they weren’t doing quality testing to see if a mitigation for one thing might cause a problem for another thing?

Reply | Quote