am_delta_patch_1.17?*.exe file Warning . .

Greetings from the GREAT LAND of Texas,

Every morning this file, am_delta_patch_1.17*.exe (the asterisk represents a very long alpha/numeric characters that change daily) is sent from Microsoft and Avast! FREE will not allow it through until I change from the recommended action to ALLOW the file to be downloaded. Have checked with Microsoft Community and it is a VALID file as an update to Microsoft Security Client. There is not any method of changing the way Avast! handles this file.

How do I change the way Avast! approves this file so it can be downloaded and installed?

If you have avast installed then you should not have MSE on the same system.

You again? I have a 64 bit system and have always run Avast! FREE, Microsoft Security Client, WinPatrol, MBAM, EMET, SBS&D v2 all at the same time without any problem.

Do we do the THREATS again?

What in the world are you talking about ???

It’s plain and simple! you cant have two av’s on the same system as you have noticed since avast is detecting MSE’s signature updates.

If you don’t want to listen to common sense then that is your problem ::slight_smile:

I have, MSC, MBAM, SBS&D, Avast FREE, WinPatrol, EMET, SAS all running on my system and they work together just fine. Even run scans with them all at the same time without any problem. Just Avast alerting me to STOP the download of updates for MSC every single day, which I do not as that is part of Microsoft’s O/S. MSC is Microsoft Securty CLient v2.x; MBAM is MalwareBytesAntiMalware v2.0.2.x; SBS&D is Spybot Search & Destroy v2.x’ EMET is Enhanced Mitigation Experience Toolkit v4.1; SAS is Super Anti Spyware v5.7.x. All latest updates and working just fine, except for the pain in the NECK Avast reporting the file from Microsoft Technet is a danger to my system when it is just an update.

Your other software mentioned isn’t Anti-Virus software so is of no concern, in repeating my self again “only one AV per system” otherwise you’ll end up with problems like you are seeing now and it’s lucky you haven’t seen worse.

Not unusual for an AV to detect another AV’s signatures since they look like a virus, keep one and ditch the other.

@ NTxLS,

You may not want to hear it, but CraigB is correct. Competitor a/v signatures that are contained in an update file can be detected by another a/v solution as that is one of the ways real-time detection works. Keep Microsoft Security Client if that is what you prefer.

I’d drop MSC, SBSD and SAS.

What exactly does avast! report about that file?