[German]Here is a collection of potentially helpful information for administrators about installation issues related to microcode update KB4346084 (Windows 10 V1803) and the issue of missing Servicing Stack Update (SSU) for KB3177467 (Windows 7 SP1 and server counterparts). Microcode Update KB41000347 also breaks Overclocking on Haswell-E-CPUs.
Windows 7: Missing SSU causes error 0x8000FFFF
In August and September 2018 Microsoft released several Rollup Updates for Windows 7 SP1 (see Patchday: Updates for Windows 7/8.1/Server Sept. 11, 2018). On some Windows 7 SP1 systems and some Windows Server counterparts, the installation error 0x8000FFFF occurred when installing the rollup updates. I had already addressed this issues and the root cause for installation error 0x8000FFFF in update KB4457144 (Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1) within my blog post Patchday issues with updates & WSUS (September 11, 2018). The root cause was a missing Servicing Stack (SSU) update KB3177467 from September 2016.
If you installed the missing SSU KB3177467 from September 2016, you could also install the rollup updates for August and September 2018. But not every administrator noticed this, especially if he neither reads here within my blog or at askwoody.com.
So THAT’s why we had problems with this month’s Win7 Monthly Rollup throwing error 0x8000FFFF. John Wilcox has a good explainer on the Windows IT Pro blog. https://t.co/CTKCf3VmAl
— Woody Leonhard (@woodyleonhard) 21. September 2018
Woody Leonhard noticed, that Microsoft has published on September 21, 2018 the article Windows 7 servicing stack updates: managing change and appreciating cumulative updates – containing information about this issue. The quintessence of this lengthy article, or what is relevant for administrators:
- Microsoft has done some homework and updated the KB articles to include the SSU KB3177467 as required for installing the rollup updates.
- Microsoft has decided to reissue the SSU KB3177467 (dated September 20, 2016) as of October 2018-Patchday (October 9, 2018) and mark it as a security update.
The new Servicing Stack Update will be released to ensure that users of the affected systems do not encounter these specific installation errors again in the future. This update will be marked as “Security” and not just “Critical”. This is to ensure that the update is also installed on machines whose administrators only allow security updates to be installed. This will let you know or, in case of doubt, read the article Windows 7 servicing stack updates: managing change and appreciating cumulative updates.
Microcode Update KB346084 install issues
I’ve blogged also about the Intel Microcode Update KB4346084 in the mid of August 2018 within the article Intel Microcode Updates KB4346084, KB4346085, KB4346086, KB4346087, KB434608 (August 20/21, 2018). A few days ago I came across this thread at German site administrator.de. An administrator has facing the situation, that the update could not be installed on some of his machines. He wrote:
Why can this update be installed on various systems, while it refuses to install on other, identical systems (same CPU, board, bios, OS build)? Got the message ‘The update is not suitable for your computer.’ I’m helpless, don’t have a clue. Somebody else observed the same? Edit: I just booted on an affected system with a Windows2Go USB stick and was able to install the patch there without any problems – so there’s nothing wrong with the hardware.
At the time I read the thread, there was still little feedback available. German blog reader Bernhard Diener then posted on September 20, 2018 a comment (within my German blog), notifying me, that the root cause has been found (thanks for that). Here is the translated text:
Summarized: The Spectre SSB Microcode Patch KB4346084 cannot be installed if the Spectre BTI Patch KB4100347 has been installed before. But you only need one, the newer 4346084, which helps for both variants.
And the thread creator at administrator.de wrote within an additional post (free translated):
So, it has indeed been explained, and the solution is most astonishing: Microsoft’s own Microcode Update KB4100347 (remedy against Spectre BTI) is the cause. If this has already been installed, the newer microcode update KB4346084 cannot even be installed; and, it loses its function and protective effect in any case!
Microsoft… never has this pointed out. I will notify Microsoft about this. Fortunately, on affected systems, uninstalling kb4100347 is enough to solve the install issue – the protection against Spectre BTI remains with update KB4346084!
Maybe it will help one of those affected. Windows patching seems to be a pure adventure. Or what’s your opinion?
KB4100347 kills Overclocking on Broadwell-E
It seems that users who running board with overclocked Broadwell-E processors are receiving an unwelcome surprise with microcode update KB4100347. On reddit.com and also in ASUS forum are contributions reporting, that update KB4100347 breaks overclocking at Broadwell-E CPUs.
Warning: Windows Update KB4100347 Breaks Broadwell-E OverclockingI just got around to installing a handful of updates from the past week on my computer, and upon rebooting I realised that the overclock on my Core i7-6800K was no longer applying. I figured it might be because of the microcode updates, and sure enough, that appears to be exactly the case.…
Later a few users have pointed out that KB4346084 resolved this issue. And the reddit.com poster confirmed this. Uninstalling KB4100347 and installing update KB4346084 instead might resolved the issue.
Adobe Flash Player version 184.108.40.206 released
Microsoft Office-Updates (September 4, 2018)
Microsoft Security Update Summary September 11, 2018
Patchday: Updates for Windows 7/8.1/Server Sept. 11, 2018
Patchday Windows 10-Updates (September 11, 2018)
Patchday Microsoft Office Updates (September 11, 2018)
Microsoft Patchday: Other Updates September 11, 2018
Cookies helps to fund this blog: Cookie settings