NET Security/Quality rollups KB 3210137, 3210138 pulled over conflict with SQL Server, Veritas backup

Topic

New Reply

The 3rd Tuesday “preview” rollout isn’t working the way it’s supposed to. UPDATE: Following up on comments posted on the patchmanagement.org mailing l
[See the full post at: NET Security/Quality rollups KB 3210137, 3210138 pulled over conflict with SQL Server, Veritas backup]

Reply | Quote

Replies

Just read the InfoWorld article and got another good laugh from the following —

“Surprisingly, Microsoft didn’t pick up the bug in its “Preview of Quality Rollup” phase, which put the patches out for testing in November. I didn’t see any notice about the problem until yesterday–a full week after the final, December versions of the patches appeared and a month after the bug first hit in the “Preview” phase.”

Surprisingly? Really? You’re too kind!

Reply | Quote

Maybe the bug wasn’t caught in the Preview is because everyone is avoiding the Previews!

Reply | Quote

Them gosh-durn unpaid beta testers ain’t testin’ what they’re s’posed to be testin’.

Reply | Quote

Yesterday I noticed an Optional Updated for two of my Windows 7 machines,
Name:INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80
Size: 67KB

Once again the More information/Support information links will give you nothing. Just wondering if I should install it.

Thank you!

Reply | Quote

Do you have a KB number?

Reply | Quote

Thank you for your response, but it does not have a KB, it seems like a INTEL update for hardware. Very strange

Reply | Quote

It could be something that Intel is distributing. Where do you see it? In Windows Update? If so, what is the exact name?

Reply | Quote

Woody, I saw it when I checked for Windows Updates manually. The full name is:

INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80
Size: 67KB

That PC has an Intel motherboard. Also at work too, wit another PC with the same motherboard. It seems like a hardware/driver update.

Reply | Quote

Others are confused by this one:

http://www.drwindows.de/windows-8-allgemein/122529-optionales-windows-update-intel-system.html

Reply | Quote

Haha, yeah, you could be right!

Reply | Quote

My general rule of thumb pertaining to MS provided hardware drivers is if it ain’t broke don’t break it.

Get Intel drivers from Intel, NOT Microsoft.

Reply | Quote

What’s interesting to me here is a little logical thing. We established, last week, the only “security” update to .net Framework was to 4.6.2. So, what seems to have happen here is last week’s big .net security and quality roll-up “broke” what was previously a stable 4.5.2. This would suggest, and I underscore suggest, the problem is not in the security portion of the KB, as there was none, but the quality roll-up portion. I am not in the computer business, so all I am doing is raising a logical suggestion.

Reply | Quote

It was in my WU as an Optional this morning as well. This is how it reads: INTEL-System-8/19/2016 12:00:00AM-10.1.2.80 67KB

Reply | Quote

boy, am I glad for defcon…
still patiently waiting for green b4 installing anything!

Reply | Quote

We’ve had two pulled patches, at least two missing “Preview” patches, and an unannounced hotfix so far this month. Probably a good reason to wait a bit.

Reply | Quote

Looks like it’s some sort of driver update for Intel chipsets.

In Swedish:

http://www.sweclockers.com/forum/trad/1458219-windows-update-valfri-intel-system-8-19-2016-120000-am-10-1-2-80-67kb

http://www.sweclockers.com/forum/trad/1458218-ska-man-kopa-ett-gtx-1080-nu-eller-vanta-pa-1100-serien

http://www.sweclockers.com/forum/trad/1458221-vanda-pa-nataggskablarna-dum-ide

No idea why it isn’t prevalent in the US, but you’re safe to simply ignore it.

Reply | Quote

Looks likely to me.

Reply | Quote

I got that one also. There is no KB number, it’s listed exactly as above: INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80. Underneath the name is: INTEL System driver update released in August 2016. No info available through More information/Support information. Anybody know what it is?

Reply | Quote

No idea, but I’m seeing reports in Swedish, and “b” just logged a post in German.

Reply | Quote

Thx

Reply | Quote

Showed up in mine, too: Win 7 Home Premium 64 bit

WU won’t let me cut and paste, but it says:
>>INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80

>> INTEL System driver update released in August 2016

Size is 67 KB

I searched the Intel site and could not find anything on this update. Hmm.

Reply | Quote

Which patches have been pulled?

Reply | Quote

Woody, I am asking because I don’t see any of them pulled in WSUS.
I read your update after posting and this seems to clarify it. 🙂

Reply | Quote

Ends up they haven’t been pulled. The two KBs mentioned, 3210137 and 38, were never released as independent patches – at least, they weren’t released independently on WSUS, as best I can tell. They were rolled into KB 3205403 and 3205404, respectively and THOSE patches were, and are, available. They’re the ones that came out on WSUS.

Making the situation even more complex, only the .NET 4.5.2 part of KB 3205403 and 3205404 have the bug. I have no idea how Microsoft’s going to fix it. Probably wait until next month and overwrite the 4.5.2 pieces then. In the interim, SQL users need to go through the manual fix.

Further confusing things: Veritas recommends removing KB 3210137 and 38. It isn’t clear to me if those appear individually on some Windows 8.1 computers. Do you know?

These interlocking KB numbers have my head swimming.

That’s why I had the article pulled from InfoWorld. I need to rework it.

Reply | Quote

I cannot find KB3210137 and KB3210138 on WSUS neither as available nor expired. There are probably included in the rollups as you said.
This confirms that the Enterprise customers, unlike popular belief, do not get preferential treatment and the bugs affecting them are not fixed immediately.
I have nothing to do with Windows 8.1, the closest which I use regularly being Windows 2012 R2 which I will check later. Noel uses Windows 8.1 and he can provide better input than me about this issue.

Reply | Quote

They weren’t pulled from WSUS, but I’m still scratching my head. I’ll run a test on Win 8.1 overnight.

Reply | Quote

I can’t see those patches on fully patched systems. It may be because I have .NET Framework 4.6.2 installed where those patches do not apply.

Reply | Quote

Windows 2012 R2 systems, should be the same for Windows 8.1.

Reply | Quote

Yeah, I’m struggling with setting up a clean 8.1 machine with 4.5.2. Check for updates took overnight, and it still hasn’t stopped. Argh.

Reply | Quote

I have downloaded KB3210137 from the Microsoft Update Catalog for storage, although I have no intention of installing it myself.

It is still available from Microsoft Update Catalog, as part of KB3205404. When you click download on KB3205404, you will see several updates to download, and one of them is KB3210137.

Reply | Quote

Thanks!

Reply | Quote

@Woody:

Is KB3205404 (Important update listed in the MS updates) SAFE to install? Cannot seem to find an answer on this question.

Thank you for current information – – – I don’t see anything else here.

Reply | Quote