Microsoft Security Essentials definition 1.249.211.0 appears over and over again

Topic

New Reply

Got an email from @twbartender: Since 8/19 I’ve been having almost daily issues with Microsoft Security Essentials Definition Updates that keep reintr
[See the full post at: Microsoft Security Essentials definition 1.249.211.0 appears over and over again]

2 users thanked author for this post.

twbartender, AJNorth

Reply | Quote

Replies

I’m having exactly the same problem on 2 Win7 Pro sp1 x64 machines. I haven’t tried hiding 1.249.211.0. The only other thing I would add is that when I open Microsoft Security Essentials, nothing at all seems to be wrong. It always says the latest update was successfully installed (i.e., never says 1.249.211.0 was just installed except for the one time a couple weeks ago when 1.249.211.0 was actually the new update that was supposed to be installed).

I had a similar issue about 6 months ago with one of my machines where MSE would say a definition update was successfully installed but WU would say the same update was not. There was no offending “old” update involved, though, at that time. The only other thing I remember is that there was about a 2 minute time stamp discrepancy between MSE and WU. I DO NOT have that discrepancy now with the 1.249.211.0 issue. Eventually the issue from 6 months ago just sort of worked itself out without my doing anything.

(Edit) One other thing. I can SUCCESSFULLY install an update that WU says was unsuccessful by doing a manual definition update in MSE. WU will then report the update as being successfully installed. So, basically, that’s been my workaround; I let MSE/WU do what ever it does around 6:00pm every day. Then I go back in and redo the update manually and run another scan. A pain in the neck but it works.

Reply | Quote

I noticed an old MSE update being listed in Windows Updates over the last couple of days, in addition to the latest one. I don’t recall its number but I think it was dated 25th August. It hasn’t bothered me as I never install MSE updates from Windows Updates and only install them using the  MSE Update option. Once I’ve done that either manually (not often) or as part of the daily scan any MSE updates disappear from Windows Updates automatically.

However, checking my Windows Updates history I see that on most but not all days since 19th August there has been one failed MSE update together with a successfully installed one, sometimes the successful one has the same definition number, sometimes not. Clearly something’s not quite right.

Reply | Quote

I never install definition updates from WU, either. I always do it from MSE either manually or MSE does it automatically. Either way, though when you “View Update History” in WU, you see the definition update listed as either being successfully or unsuccessfully installed.

In a sense here, I guess one of the real questions is which is right, WU or MSE? If it’s MSE, then I’m relatively happy since then the definition update has been successfully installed.

Reply | Quote

In a Win 7 Pro x64 rig, I have WU turned off, so manually check for updates to MSE from within itself several times a day.

However, every few days, it appears to download the update(s), then during installation kicks out an error to the effect that the download time had been exceeded — even though the definition numbers almost always change (along with the definition’s creation time). In such instances, re-checking for updates (after waiting for MSE’s activity to cease via Process Explorer) will actually produce a change very rarely (perhaps one time in twenty).

Running WU at 1549 PT displayed file version 1.251.344.0 for MSE (the previous check had been about seventy-five minutes earlier; version 1.251.140.0 was installed). I updated MSE from within itself.

So, as an experiment I just ran WU again — and up popped version 1.249.211.0; imagine that. After hiding that update and re-running WU, the result was that there were no updates available (MSE concurred). (Are we having fun, yet?)

1 user thanked author for this post.

HiFlyer

Reply | Quote

Same with me Win 7 X64 SP1, Home premium.  I`m also  getting the failed then successful a number of times with others.  When you check  your update history.  MS is getting tired of  everyone staying with 7 so they are doing this to get us to switch to 10.

1 user thanked author for this post.

HiFlyer

Reply | Quote

I, too, have three repeats but I am up to 1.251.271.0 as of August 29.  I am going to keep track of the last number installed and take nothing but the next.

1 user thanked author for this post.

HiFlyer

Reply | Quote

Just downloaded and installed up 1.251.347.0 and there were no other updates on the list.  All the updates that people are getting I am not. Haven’t had any windows or office updates in about a month.

Reply | Quote

Yep appears regularly here (9 times) on Win7Prox86 just hid it this morning, did a check just now and it hasnt reappeared. Lack of it hasnt broken anything and all the other Security come in on a nearly daily basis. Hence I hid it.

Reply | Quote

On Win7-64 Pro SP! (on Group B) I have had Definitions Update for MSE 1.249.211 successfully install 12 times since July 25.  Plus I was on vacation for 9 of those days so nothing was installed during that time as the PC was off.  I have also had 6 bad installs that finish saying successful, but then show up in the Action Center as failed updates in the past 2 weeks.

 

This is a list of the installs of ONLY 249.211.

Reply | Quote

Before tonight’s usual 6:00pm update and scan, I hid the 1.249.211.0 update in WU. Everything appears to be back to normal; i.e., 1.249.211.0 did not reinstall. So, while hiding 1.249.211.0 probably didn’t actually fix anything, at least it appears to have gotten rid of an annoying symptom.

Reply | Quote

On Win7-64 Pro SP1 (on Group B). I just let MSE do its thing and update itself, I seldom get involved. MSE 1.249.211 has been successfully installed 10 times since July 26. After the first install of 1.249.211 the second install was 3 weeks later, August 18th. After every install of 1.249.211 there has been an additional different definition that fails. The first failed definition on July 26 had an error code of 80070670, since then they have all had an error code of 80070650. I just did a WU check and there was a different definition available and I installed it. Waited a couple minutes, ran another WU check and 1.249.211 showed up, I hid it. If that doesn’t work I’ll run the Windows Update Troubleshooter. I’ll check tomorrow night and if it continues being a pain I’ll update my post.

<menu id=”userscript-search-by-image” type=”context”></menu>

<menu id=”userscript-search-by-image” type=”context”></menu>

Reply | Quote

All good here on Win 8.1 Home x64, no duplicated instances seen

Reply | Quote

Only used MSE briefly at W7 installation in order to patch system, then moved to a reliable AV.
The same methodology in using IE to download another browser

Windows - commercial by definition and now function...

1 user thanked author for this post.

HiFlyer

Reply | Quote

Has this only been seen in MSE on Win7? No instances of this showing up in Defender on W10?

1 user thanked author for this post.

HiFlyer

Reply | Quote

Win7 pro here. This is happening to me and I didn’t notice (I update manualy) according to my history it started in 19/8. Since everybody says hiding it works i’ll try that out

Reply | Quote

The date you mentioned is interesting to me because on my computer, beginning one day earlier than on yours, all of a sudden any number of MSE updates failed. That has never, ever happened before. To be honest, I never look at Update History unless I’m doing the monthly updates (I’m a Group B manual install user). All of a sudden, in addition to the one MSE update that is showing up again and again as having successfully installed, but continues to keep installing itself, I have updates that didn’t install. So much for all these tech companies that insist on more and more H-1B visas.

Reply | Quote

I seem to have the 1.249.211.0 recurrence problem.
But it looks like there are quite a few definition failures.
The top 1.251.379.0 definition was manually installed.
When does MSE auto install definitions? I don’t see a settings option to control that.
W7 Home Premium SP1 64 bit

 

Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A

HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A

Reply | Quote

I had a repeat today upon bootup.  I checked the Action Center and also the WU installed updates and saw that 1.251.379 had failed to install.  I ran a manual update from inside MSE which is usually successful in these cases.  Install was successful.

I did notice however that during the manually initialed install, it appeared to do a fast second install.  Upon checking the installed updates, sure enough the update 1.249.211 had also installed.  MSE however show the allegedly failed install of 1.251.379 as successful but with the original date time stamp.

I then ran WU.  It showed that in addition to the routine monthly rollup and the previews, it was saying the 1.251.379 was in the chute for installation.  I unchecked everything except the MSE definition and ran the install.  It was very fast.  I opened MSE and saw that the date/time of the install was back at the time of the original install in para 1 above.

I then re-ran WU.  The same updates appeared, but now included MSE definitions of 1.249.211.  I decided to hide it.  Waiting to see what will happen.

For me the MSE updates at least once a day (depending on what time of day I boot the PC).  I will monitor it and do a clean install of MSE if the issue 211 continues.  I do not believe it is a MSE glitch, but actually a WU glitch.

I have had minor MSE issues in the past that re-install cured.  I know some distain MSE, but at least it’s fixes have not required a full reinstall of Windows like happened in the past with both McAfee and the old Norton.

Reply | Quote

I find it very confusing.

In Windows Update history tonight it shows both 1.251.379.0 and 1.249.211.0 having been installed today, the former unsuccessfully and the latter successfully, at the same time. However, on the MSE Update screen it shows the current version installed at that time as being 1.251.379.0. That is presumably the version the daily scan ran with at that time.

I’m confused as to whether the problem is with MSE or Windows Update. I tend, on balance, to trust the former more than the latter.

Reply | Quote

I do NOT have Windows Update running. MSE on my Windows 7 system updates itself.

My observations:

Filtering for event 2000 in the System Event Log, I see successful updates listed in pairs (two nearly identical event 2000 entries, one of which says Signature Type: Antivirus and one of which says Signature Type: AntiSpyware) once or twice per day. Interspersed with these are event 2001 errors showing that Windows Update was not available to do the update. This means that MSE got the data itself, without fuss or muss…

Working backward a few entries from the most recent, which was this morning:

9/1/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.363.0
Previous Signature Version: 1.251.344.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

9/1/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.363.0
Previous Signature Version: 1.251.344.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/31/2017 7:29:39 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.344.0
Previous Signature Version: 1.251.298.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/31/2017 7:29:39 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.344.0
Previous Signature Version: 1.251.298.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/31/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.298.0
Previous Signature Version: 1.251.282.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/31/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.298.0
Previous Signature Version: 1.251.282.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/30/2017 7:29:38 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.282.0
Previous Signature Version: 1.251.252.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/30/2017 7:29:38 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.282.0
Previous Signature Version: 1.251.252.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/30/2017 4:11:32 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.252.0
Previous Signature Version: 1.251.232.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/30/2017 4:11:32 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.252.0
Previous Signature Version: 1.251.232.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/29/2017 7:29:38 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.232.0
Previous Signature Version: 1.251.192.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/29/2017 7:29:38 PM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.232.0
Previous Signature Version: 1.251.192.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/29/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.192.0
Previous Signature Version: 1.251.185.0
Signature Type: AntiSpyware
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

8/29/2017 4:11:33 AM
Microsoft Antimalware signature version has been updated.
Current Signature Version: 1.251.192.0
Previous Signature Version: 1.251.185.0
Signature Type: AntiVirus
Update Type: Delta
User: NT AUTHORITY\NETWORK SERVICE
Current Engine Version: 1.1.14104.0
Previous Engine Version: 1.1.14104.0

This looks like a logical progression up the numerical sequence to me (keeping in mind the most recent entry is on top).

Last time the Current Engine Version changed was from 1.1.14003.0 to 1.1.14104.0 on August 24. Nothing special was initiated on that date.

A search of my entire System Event Log turns up no entry containing 1.249.211.0 at all.

What do you see in your System Event log?

I guess I have to ask: Why would you want to keep the Windows Update service enabled?

-Noel

2 users thanked author for this post.

Great Lake Bunyip, AJNorth

Reply | Quote

It looks you have 2 updates per day at essentially the exact same time each day. Those times differ from my update times (I have one update per day) so it’s not surprising that we have different definitions that have been updated, right? Probably not everybody got 1.249.211.0.

Going back to 8/28/2017 my definition updates are (earliest to latest): 173, 187,236,272,279,290,347,379. These values are ‘x’ in 1.251.x.0. So we have a different set of definitions that were updated.

I have WU set at “check for updates but let me choose whether to download and install”. Hey, it works for me as I’ve never had an unwanted update rammed down my machine, and that setting has never been changed “on its own”. So, while I don’t like WU, I’ve found it does a credible job finding updates in general for me.

As for the System Event Log, I’ll just admit my ignorance. I’ve stumbled upon it before but offhand I don’t know how to look at it. The logs I have come across usually have more info than I know what to do with or understand.

EDIT I changed 1.249.x.0 to 1.251.x.0, the latter of which I meant above.

Reply | Quote

Noel:  Thanks for the reminder of the System Event Log.

Here is what I found.  20 Event ID 2001 events (Errors) Between 6/21/2017 and 9/1/2017

13 were time outs during the search stages; (5 on antispyware; 5 on antivirus; 3 on Network Inspection Service)
7 were fatal errors during installation (the 7 on antivirus)

The 7 fatal errors started on 8/20, always on a full update.  There were no delta update errors and 38 successful installs.  There were 2 successful full installs.

Interestingly, as you mentioned the events were in pairs, AV and ASW.  From 8/26 on the cycle was one failure followed by 2 pairs of successes.

I now have to do an overlay of the MSE Signature version 1.249.211 incidents to see how that repetitive install figures in the pattern and if it follows or preceeds an error.

I have viewed these logs before, but this is the first time I did a lot of filtering.  Thanks.  A powerful tool.

Your post also revealed I should have been more specific on my WU status.  I have WU set to Never Check, but the service is set automatic (delayed start).

1 user thanked author for this post.

Noel Carboni

Reply | Quote

Just my 2c worth. I have had the same problem. Yesterday (1 Aug Sydney OZ) I checked logs on my 2 PCs and found errors as stated. Scanned for updates and MSE 1.249.211.0 appeared again. I hid it on both machines and installed a later update. Since then no problems. I have also ceased doing manual updates of MSE. Running W7 Home Premium 64x fully updated software including KB4034664.

Reply | Quote

 

I want to preface this by saying that I usually let MSE automatically install the definitions.
I think it usually happens late in the afternoon.
Once in a while I will manually install.
Sometimes, I notice that definitions are updated twice in one day.

I came to askwoody yesterday to see about any change in ms-defcon and saw the MSE issue, so I deceided to check if I had it, and I did.

When I checked “review update history” , I was having the same problems with multiple failed/successful MSE 1.249.211.0, and others that were mentioned in above posts.
NOTE: The first failed MSE update was 1.249.17.0 on 7/20.

I ran a Windows Update and 1.249.211.0 appeared again.
I hid it. (1.249.211.0)
I did another MSE update but not through Windows Update.
Checked my review update history and 1.251.387 successfully installed.
This morning I ran a Windows update first to see if 1.249.211.0 would show up again.
It did not.
I ran a MSE update.  1.251.409.0 installed successfully. (which is the latest version according MS  https://www.microsoft.com/en-us/wdsi/definitions
Went back and ran another Windows update and 1.249.211.0 did not come up.
Checked review update history and confirmed that 1.251.409.0 installed successfully.

So here is where my MSE stands.

 

 

Reply | Quote

Win7 Pro x64.  On my production  machine, I usually perform manual updates of MSE definitions online, perhaps twice a day at times which suit me.  I have an experimental machine which is not usually internet-facing (and commonly not switched on at all);  mostly, when I want to update its MSE definitions, I use the production machine to download “the most recent definitions” from the relevant MS page and save the file (mpam-fe.exe) to a USB drive, move the USB drive to the experimental machine, install that, and only then will I connect the experimental machine to the internet.

My production machine exhibited the “multiple 1.249.211.0” problem.  Apparently cured by going into Windows Update, searching for updates, hide 1.249.211.0 if offered.  Apparently ok now, but I am not convinced.  Production machine is now up to 1.251.427.0 according to MSE.

On the experimental machine (which was up-to-date as of yesterday, specifically MSE definitions were 1.251.406.0), I just now ran Windows Update — which said there were no MSE-related updates available.  I knew there ought to be 1.251.427.0, or at least something later than 406, so I went ahead and ran MSE update to see what happened.  GRRR: 1.249.211.0 downloaded and installed (well, something downloaded and installed according to the MSE progress bar).  But MSE still says the installed definitions are 406 (yesterday’s); Windows Update says 249.211 installed successfully.  The experimental machine did not get 251.427, or any of today’s definition sets.

Incidentally, the experimental machine did not exhibit the “multiple 249.211” problem yesterday:  but my hypothesis is that it will do tomorrow.

Something is badly broken.  Can I trust any of this (rhetoric)?

Hugh McFarlane

Reply | Quote

For me the hiding of MSE definition 1.249.211.0 continues to work as a way of preventing it from reappearing for re-installation  in WU.

Yesterday I went searching the internet to see how many others have been experiencing this 1.249.211.0 issue. I was surprised to find that there are very few threads out there that have either mentioned or addressed the issue.

What I did find is that the 1.249.211.0 definition is being offered in the Microsoft Update Catalog… I found it by using either KB2310138 or definitions as the search term. The KB2310138 search produced a total of 7 definition entries starting with, 1.251.427.0 at 692.7 MB, updated 9/3/17, and ending with the “1.249.211.0” definition at 686.5 MB, updated 7/25/15.

My question is, out of all the definition updates produced between 7/25/15 and 9/3/17, why are these 7 definition updates the only ones offered for MSE in the catalog, especially 1.249.211.0?  As of this morning, definition 1.251.427.0 is being offered on WU, and is 8.2 MB in size. This is compared to the 692.7 MB size of the one offered in the Microsoft Update Catalog.

 

Reply | Quote

And out of those seven updates offered in the catalogue, six are dated yesterday or today, and only 1.249.211.0 is dated any earlier (and much earlier).  Something is wrong in the metadata of 1.249.211.0 (whatever I mean by that).

I think the gigantic size of any MSE definition set, shown in the catalogue, assumes that you have nothing to start from (such as after a fresh install of MSE).  WU, and MSE itself, manage to be much more selective when deciding what to download in order to bring yesterday’s version up to today’s;  about 8 MB for 1.251.427.0 seems reasonable (starting from a recent point);  695 MB for 1.251.428.0 seems outrageous even starting from zilch, given that mpam-fe.exe is about 150MB for a full install from scratch.

PS a re-install of MSE doesn’t fix the problem, and incidentally turns on Automatic Updates for everything else.  GRRR.

Hugh McFarlane

Reply | Quote

The difference in size from the updates and what is in the catalog is due to the fact that the majority of the MSE automatic updates are deltas, i.e., only what is new or changed, and not the entire signatures or definitions for antimalware, antivirus and network inspection signatures.

Look above to Noel Carboni’s post #131774 to see what he extracted from the Windows System Events log.  It shows mainly delta updates.

I have hidden MSE 1.249.211 and it has not reappeared and this specific problem has been stopped.

This link will allow you to download the MSE updates manually.

https://go.microsoft.com/fwlink/?LinkID=87341

Save them and then right click on them to see the details and it will give the version number.  The updates are generally 138K-239K in size.

 

@Hugh McFarlane:  This part is not really on topic for this thread, but I have reinstalled MSE a number of times (the last over 6 months ago), and it has never re-set my WU preferences.  I have WU set to Never Check (Group B), and it has remained that way.  My MSE still updates automatically, but nothing else does.  I also have the ‘install new versions automatically” in IE unchecked.

Reply | Quote

? says:
Thanks for all the input on the “211”. I’ve always had a hard time Googling anything of value about MSE problems. I see the “211” definition update installing repeatedly since 08/17/2017 on all machines, so I did the windows update for the latest definitions and then searched again and when “211” reappeared once again I hid it! It seemed to be re-installing over the latest engine? I have used MSE since it evolved from One Care back in 2008 0r 2009 and have had many instances of problems, but hey “it’s free”. (used to have viruses slip through the flash especially when my daughter was using MySpace and then Facebook). You will not catch me using Facebook, ever…Facebook is now depositing “Phils\Garagefonts, Inc.” in my %temp%\low folder (2 dat files) every time she logs on and eating up massive amounts if memory in IE 11. Probably shlepping off more personal info to the Ireland servers.

I also wonder what all the Telemetry Submissions are all about, seems like more than usual. I keep the last version of CCleaner to have the remove MSE files handy because it is fun to remove the Telemetry before Microsoft sucks it up. Not sure what it collects and sends. I think I have most of the other telemetry leaks plugged. I tried turning off spynet but it kills the real time scanning, oh bother.

Anyway, thanks for continuing to be the best place to spot and recommend fixes for the daily slip-ups from Redmond!

Now back to ubuntu

Reply | Quote

For what it’s worth, I’ve got 3 Win7 machines that had “the recurring 211 problem”. When the 211 update showed up in Windows Update, I hid it on all 3 machines and all 3 have been just fine since the hiding. “Fine” means that 211 has not tried to reinstall itself, and MSE and WU are consistent in what they are reporting as the latest installed definitions. So, while hiding 211 may not have actually fixed anything, the symptom has at least disappeared.

1 user thanked author for this post.

HiFlyer

Reply | Quote

DrBonzo wrote:

For what it’s worth, I’ve got 3 Win7 machines that had “the recurring 211 problem”. When the 211 update showed up in Windows Update, I hid it on all 3 machines and all 3 have been just fine since the hiding. “Fine” means that 211 has not tried to reinstall itself, and MSE and WU are consistent in what they are reporting as the latest installed definitions. So, while hiding 211 may not have actually fixed anything, the symptom has at least disappeared.

2 Win7SP1 x64 laptops (1 HP, 1Pro).

WinUpdate :  Nevercheck.   Manual update defintions via MSE 2x daily/

211 had been installed twice on both via direct MSE manually initiated updates (in July and Aug).  Ran WU on both laptops today after  installing Group B AKB200003 updates and was offered 211.  Hid both and ran again.  No sign of 211.  We’ll see what happens.

Reply | Quote

Noticed MS Defcon 2 was changed to 3 and to get the August patches installed.
I ran WU and WU showed:
2017-08 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034670)
2017-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034664)
Windows Malicious Software Removal Tool x64 – August 2017 (KB890830)
Definition Update for Microsoft Security Essentials – KB2310138 (Definition 1.251.513.0)

I hid all of the above, then I ran WU five more times and each time WU came back with another MSE Definition ending with Definition 1.251.491.0.
I also hid all the MSE Definitions.
1.249.211.0 did not ever showed up.
I have WU set to never check for updates.

Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A

HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A

Reply | Quote

Update on the above Post.
I checked off all the MSE definitions and ran WU, WU returned with one MSE Definition KB2310138,  1.251.513.0.
It installed successfully, ran WU again, WU came back with MSE KB2310138 1.249.211.0
I hid it, I will see what happens.

Ran WU again, WU shows “There are no updates available for your computer”.

Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A

HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A

Reply | Quote

2017-08 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034670) is an UNCHECKED OPTIONAL patch. UNCHECKED means it will not get installed. Please unhide it.

We are at MS-DEFCON 3, which means it is OK to go ahead and install the current August patches. Please unhide and install these August patches:
2017-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034664)
Windows Malicious Software Removal Tool x64 – August 2017 (KB890830)
Definition Update for Microsoft Security Essentials – KB2310138 (Definition 1.251.513.0)

There is a problem with MSE Definitions 1.249.211.0 – if it shows up again, hide it and leave it hidden.

Reply | Quote

PKCano,

I posted an update right before you posted a reply. (not sure if you read it)
Anyways 1.249.211.0 showed and I hid it, I will see what happens.
I will install current August patches as you suggested in your previous post.

Thanks for the info,

Sparky

 

Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A

HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A

Reply | Quote

I have only just discovered this thread, which perhaps got hidden when the site was down. I have for a while been perplexed by the recurrence of MSE 1.249.211.0, but not unduly concerned as I have nevertheless been able to get more recent updates to install (I update MSE manually on a daily basis). Next time I have WU turned on – which only happens about once a month – I’ll hide 1.249.211.0 and hope it goes away for good. Many thanks.

Reply | Quote

MS finally fixed the problem. You don’t have to hide 1.249.211.0 anymore as of today.

Reply | Quote

I noticed 1.249.211.0 didn’t pop up as usual yesterday…………………….but hardly dared hope………………….was going to wait and see if it came back to haunt me tomorrow!

Reply | Quote

Well:
68 days since first sighted problem.
Probably was 4days before Answers.Microsoft got the issue ‘elevated’.
Several online sources published before end of August.
Now 26Oct, so depending how you count 56 to 68 days to solve the issue.
Windows as a Service.

Reply | Quote

anonymous wrote:

MS finally fixed the problem. You don’t have to hide 1.249.211.0 anymore as of today.

I’ve been unable to locate any online documentation that confirms what you’ve indicated.  Has Microsoft posted any sort of statement indicating that problem has truly been fixed? If so, I’d appreciate it if you could post the link to that information.

Reply | Quote

I found

Reply | Quote