{"id":6957,"date":"2018-09-12T09:54:42","date_gmt":"2018-09-12T07:54:42","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=6957"},"modified":"2023-07-19T17:09:42","modified_gmt":"2023-07-19T15:09:42","slug":"patchday-issues-with-updates-wsus-september-11-2018","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/09\/12\/patchday-issues-with-updates-wsus-september-11-2018\/","title":{"rendered":"Patchday issues with updates & WSUS (September 11, 2018)"},"content":{"rendered":"

\"Windows[German<\/a>]As of September 11, 2018, Microsoft has released a new batch of updates for Windows and other products. Update KB4457144 for Windows 7 SP1 may issue error 0x8000FFFF. Addendum:<\/strong> The reason for this error and a simple fix has been found. KB4457128 for Windows 10 version 1803 is installed twice if necessary, and WSUS has detection problems.<\/p>\n

<\/p>\n

\"\"Here's an overview of what I've seen so far. The article will be updated if necessary.<\/p>\n

Error 0x8000FFFF (Update KB4457144; Windows 7 SP1)<\/h2>\n

Update KB4457144<\/a> (Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1) addresses some bugs and updates the shell, kernel, Hyper-V, network components and more.<\/p>\n

Woody Leonhard reported at askwoody<\/a>, that this update triggers the error 0x8000FFFF during installation. The error does not occur on all systems, but I found several confirmations at askwoody.com.<\/p>\n

Error code 0x8000FFFF stands for E_UNEXPECTED, an unspecified but serious error, that leads to the installation abort. Within my old German blog post Windows 7 Service Pack 1 Troubleshooting-Tipps<\/a> I had mentioned malware infections as a root cause. So my advice is, the system should be checked with external scanners as a precaution. But also damaged system files can be the cause for this error. Here I recommend to check the system for corrupted system files with sfc \/scannow<\/em> (see that part within my blog post Check and repair Windows system files and component store<\/a>).<\/p>\n

Root cause: Missing Servicing Stack Update KB3177467<\/h3>\n

It's fascinating how sometimes the pictures fall into a puzzle. Within my German blog I got today a comment<\/a>:<\/p>\n

und hier wurde pl\u00f6tzlich, win7, nach Install monthly-roll KB4457144, das KB3177467 (Servicing stack update for Win 7, September 20, 2016) angeboten.\u00a0h\u00e4? afaik war das bereits seit Monaten\/Jahren installiert, noch jemand mit sowas?<\/p>\n

Translation:\u00a0and here suddenly, win7, after install monthly-roll KB4457144, the KB3177467 (Servicing stack update for Win 7, September 20, 2016) was offered. huh? afaik was that already installed for months\/years, anyone else with something like that?<\/p><\/blockquote>\n

Windows Update noticed that a Servicing Stack Update from September 2016 is missing. At Askwoody there is this post<\/a> in the forum in which a user writes:<\/p>\n

Patch KB4457144 will be installed after installing Stack Update \"Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1 \u2013 Windows Server 2008 R2 SP1 \u2013 KB3177467 (x64)\" for 2008 R2 OS<\/p><\/blockquote>\n

And there is a feedback from Microsoft Premier Support with the hint to install the SSU:<\/p>\n

install Servicing Stack KB3177467 (September 2016), restart computer, install KB4457144.<\/p>\n

KB3177467 ist pre-requisite for KB4457144<\/p><\/blockquote>\n

This is now also mentioned in the comments given within my German blog. Thank you to everyone who participated in finding a solution.<\/p>\n

WSUS: .NET updates detection errors<\/h2>\n

Woody Leonhard pointed out to Twitter that he has received reports of detection problems for .NET framework updates in WSUS.<\/p>\n

\n

Detection logic problems on WSUS servers for .NET patches KB 4457914, 4457915, 4457916, 4457917 and 4457919. Showing as installed, when they are definitely not installed. https:\/\/t.co\/vUEoUUvOKM<\/a><\/p>\n

\u2014 Woody Leonhard (@woodyleonhard) 11. September 2018<\/a><\/p><\/blockquote>\n