Botched WSUS patch KB 3148812 still throws errors 80244019, 80244008, 8024401f

Topic

New Reply

And Microsoft just pulled the only documentation they had. InfoWorld Woody on Windows
[See the full post at: Botched WSUS patch KB 3148812 still throws errors 80244019, 80244008, 8024401f]

Reply | Quote

Replies

The new “documentation” is here. http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx

(Basically, their previous “advise” screwed more than it fixed.)

Reply | Quote

So, yesterday the Microsoft blog recommended doing 2 additional things post-install:
1. Running a command line post install
2. Installing an extra Windows 2012 R2 Feature which is HTTP Activation.

Now we are at the stage where:
– Users installing the patch and performing the first step cannot even uninstall the patch as it has already been deeply embedded in the WSUS database after running the extra command recommended by Microsoft. At the same time the patch still seems to break functionality. Those users/administrators now have to work with Microsoft directly to fix their environment, or wait for more news if they can afford the broken system for a while. This is generally an enterprise based system. It is interesting that yesterday we were told that there will be no re-release, that the code is very good quality etc.
– Users who did not follow the extra steps can gracefully uninstall the patch, although some comment on the blog that they have problems in doing so. It may also require restarting the system which in many cases is problematic in enterprises requiring additional approvals and a lot of red tape.

The second procedure about installing HTTP Activation is OK as it is regular Windows functionality and should be done either way for the future release of the patch.

While this affects a small number of readers here referring to a server product which offers an alternative way to perform Windows Update, it still shows how valuable Woody’s recommended best practices to wait and to not install new patches immediately are for most users, unless using test machines and willing to spend the time to do research.

Reply | Quote

From Steve Henry, the blog author: KB3148812 is being pulled later today to minimize further impact.

Reply | Quote

“KB3148812 is being pulled later today to minimize further impact.”

http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx

Reply | Quote

It is done now, at least from WSUS.

Reply | Quote

Yep, they pulled it.

Finally.

Reply | Quote

It looks like the replacement for pulled KB 3148812 has arrived. KB3159706 arrived today and has only shown up as applicable to my WSUS 4.0 servers. The patch is for Win 2012 and 2012R2.

But of course documentation is not yet available!

Reply | Quote

See https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

Reply | Quote