Microsoft Security Essentials Client Update Package - KB2754296

[Anak]

Microsoft has released an update for Microsoft Security Essentials which offers performance enhancements and some new functionality within the program.

To receive this update, follow these steps:

Source: Microsoft Security Essentials Update - September 2012

The user can follow the steps there or as I found it through Windows Updates.

My old version:


New:


Not sure why, but the new version does not include the Security Essentials Version line at the top of the System Information box.

 

[NoN]

Same here for the AntiMalware Client Version missing but we do not have the same either.

I've got:
Network Inspection System Engine Version: 2.1.8600.0
Network Inspection System Definition Version: 15.11.0.0

 

[Anak]

The only difference I see is I run Home Premium, and you have Pro.

I wonder if that has any bearing with the NIS versions being different ?

 

[NoN]

If it could be a difference, maybe for x32 and x64 based system, but the version type of the OS...?

 

[ignatzatsonic]

I have Home Premium 64-bit and my screen agrees with NoN in post 2.

 

[NoN]

The only difference I see is I run Home Premium, and you have Pro.

I wonder if that has any bearing with the NIS versions being different ?

It could be because you stayed at AntiVirus Definition 1.125.xxx and there was major updates like 1.133.xxx & 1.135.xxx & now 1.137.xxx before you updated.

 

[Anak]

I don't know NoN.

I found some other differences here: MSE Prerelease Version 4.1.522.0 - Microsoft Answers

Take note of rhabdomantist's answer at the bottom of his post:

Microsoft Security Essentials 4.1.0522.0
http://www.microsoft.com/en-us/download/details.aspx?id=5201
You should be able to do an over the top install.
Note the different version number (4.1.0522.0 vs 4.1.522.0) Haven't confirmed it yet but there seems to be an error.

Source: MSE Prerelease Version 4.1.522.0 - Microsoft Answers

My update said nothing of a "pre-release"


I see your recent post, let me explain, that 1.125 is the AVD version I had when I updated MSE client the last time back in April.
It is the "old version"

I was up to AVD1.137 when this Sept. client update came in.

MSE on my XP box doesn't even have NIS listed. :shock:

 

[kpo6969]

I checked for WU last nite and I got it as an important update.

 

[NoN]

Perhaps uninstall the actual MSE version, then download it again and do a windows update, could fix to newer network version engine?

 

[Anak]

That would be what to try to see if it would correct the NIS version.

But, before I do that I'm going to let it ride for a few days to see if any other updates for MSE come down the pipe.
There is even that version mix-up, is it .0552 or .552 or is that just a typo?

MS Security must have been working their butts off with the out of cycle IE update, and now the MSE client update so I'm not surprised that there would be some snafus.

 

[xxxdannyxxx]

I did an over the top update through windows update to this version


Now every time it updates it installs the same database version (Im on hourly updates):huh:


Going to uninstall and try it fresh

EDIT- And now I have this and all seems well


Danny

 

[NoN]

I did an over the top update through windows update to this version
View attachment 233779

Now every time it updates it installs the same database version (Im on hourly updates):huh:
View attachment 233780

Going to uninstall and try it fresh

EDIT- And now I have this and all seems well
View attachment 233787

Danny

An hour of Hiccup!!!!

 

[Anak]

I'm not having the problem danny had, but in downloading MSE just in case, I have noticed the File version is 4.1.522.0, and the Product version is 4.1.0522.0.

If you download MSE you can find it under properties >details tab.

NoN, guess what?

WU ran an MSE update on me, and I think I match yours now.

 

[NoN]

I'm not having the problem danny had, but in downloading MSE just in case, I have noticed the File version is 4.1.522.0, and the Product version is 4.1.0522.0.

If you download MSE you can find it under properties >details tab.

NoN, guess what?

WU ran an MSE update on me, and I think I match yours now.
View attachment 233815

Tricky MSE...it needed to be refreshed only!

 

[King Arthur]

Think I'll give this update some time to un-confuse itself, I don't feel like potentially diagnosing an update gone awry at the moment.

 

[Anak]

Think I'll give this update some time to un-confuse itself, I don't feel like potentially diagnosing an update gone awry at the moment.

While you are certainly within your rights to hesitate in upgrading MSE, I would think it prudent to do so now.

Some questions:

• I presume you have Windows Updates (WU) set to check, but let you decide?

• Do you already have the Client update in your list of available updates?

Some thoughts:

• Your present version of MSE should continue to accept the Anti-Virus Definitions (AVD), but if you wait too long you may start to see AVD update failures in your Update History.

• If you do decide to update you may want to un-install MSE first before updating, that helped in danny's situation.

• I did an over-the-top, and within a few hours with a new update to MSE's AVD, MSE straightened itself out.

• I have tried searching for a plausible reason for the confusion, but haven't had any luck so far, so I'm going to contact our resident malware expert (Jacee) to see if she can shed any light on this.

 

[King Arthur]

Some questions:

• I presume you have Windows Updates (WU) set to check, but let you decide?

• Do you already have the Client update in your list of available updates?

1. Negative. I have Windows Update set to manual, I hate automatic updates of any sort (barring AV definition updates out of neccesity from their nature).
2. No clue, I haven't bothered to check. I probably wouldn't have known there was a client update for MSE if it wasn't for this topic.

Some thoughts:

• Your present version of MSE should continue to accept the Anti-Virus Definitions (AVD), but if you wait too long you may start to see AVD update failures in your Update History.

• If you do decide to update you may want to un-install MSE first before updating, that helped in danny's situation.

• I did an over-the-top, and within a few hours with a new update to MSE's AVD, MSE straightened itself out.

• I have tried searching for a plausible reason for the confusion, but haven't had any luck so far, so I'm going to contact our resident malware expert (Jacee) to see if she can shed any light on this.

1. Yeah, if I start to get update failures I'll grab the new client. If nothing else, that'd be a good sign I gave enough time for MSE to un-confuse itself.
2. I'll keep it in mind, as I recall MSE was very tidy about cleaning up after itself anyway.
3. Good to know.
4. Information is always good, here's hoping he can shed light on this seemingly minor issue.

As the old saying goes, don't fix what's not broken. Normally I'd grab updates like this ASAP, but if there are some issues at hand then I'm not one to go in and "fix" (and potentially break!) something that ain't broke in the first place.

 

[NoN]

I was a bit young at that time but:

May 1977:

Bert Lance believes he can save Uncle Sam billions $ if he can get the government to adopt a simple motto: "If it ain't broke, don't fix it." He explains: "That's the trouble with government: Fixing things that aren't broken and not fixing things that are broken."
​

Your computer isn't a government. it is a machine that needs to be maintained whatsoever!
​