Newsletter Archives
-
What’s wrong with the Win10 1709 January Delta package?
Just saw this from Bogdan Popa on Softpedia.
KB 4088776 — for the Win10 1709 March Cumulative Update — has been modified to include this warning:
Users with Windows 10 Version 1709 Enterprise that have installed the January 2018 Delta package may encounter failure issues when installing the February and March 2018 updates from the Microsoft Update Catalog. Specifically, the Windows 10, version 1709 February Delta Update may silently fail.
Microsoft is aware of this issue and has expired the following Windows 10 version 1709 Delta Update KBs on the Microsoft Catalog on March 13, 2018:
KB4056892 – January 2018
KB4074588 – February 2018
KB4088776 – March 2018
Microsoft recommends that users uninstall the Windows 10 version 1709 January KB4056892 Delta Update package and install the March 2018 full latest cumulative update, KB4088776. Customers may resume using Delta Update packages with the April 2018 Windows 10 version 1709 monthly cumulative update.
So… does anybody know what happened to the January Delta update?
-
Problem reported with KB4056892, the Win10 1709 delta update
Just got this from Fred Marshall:
Woody – KB4056892 [the Jan. 3 1709 cumulative update] seems to not have widespread impact. But we’ve been hammered. All 1709, all or almost all Intel, workstations. Some legacy software interaction but broader cause is filtering in. Have to reinstall Windows from scratch.
It’s not clear if he’s using the Cumulative Update or the Delta Update.
Anybody else having the same problem?
-
Microsoft yanks all of this month’s Windows patches for “devices with impacted AMD processors”
Let’s hear it for beta testing.
Early this morning, Microsoft officially announced that it was pulling all of this month’s Meltdown/Spectre patches for folks with AMD processors.
That’s just the tip of the iceberg.
Computerworld Woody on Windows.
UPDATE: Kevin Beaumont has a sobering report on the status of antivirus vendors cooperating (or not) with Microsoft:
this has been incredibly messy for everybody involved. My belief is organisations shouldn’t rush these patches out. They need to carefully test and see where they need to mitigate the vulnerability.
As I’ve said many, many times before, there’s no reason to install any of the patches yet. In spite of what you saw on TV, or read in the newspaper — or what you heard from a Windows security “expert.”
-
Reaffirming that we’re still at MS-DEFCON 2
There’s still no pressing reason to install the early crop of Patch Tuesday patches.
Computerworld Woody on Windows.
Correction: @teroalhonen notes that there’s no such thing as Win10 1511 LTSC. He’s right, my Computerworld article’s wrong. Win10 1511 is supported through April 2018, but only for Enterprise and Education editions.
But that brings up a related question. Why are the Surface firmware updates only going out to 1703 and 1709? What about 1607 and 1511? They’re both being supported.
UPDATE: We have a report of a BSOD with the Win7 32-bit patch. Details to follow.