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

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 ?

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

Anak said:

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.

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.

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

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.