WSUS Broken after KB3148812 - fixed

[psydii]

After installing KB3148812 WSUS may not work properly. This is because some post install manual changes are required.

 

See What you need to know about KB3148812 - WSUS Product Team Blog - Site Home - TechNet Blogs for the steps you need to take.

 

The update increases WSUS compatability with Windows 10, and is required to maintain the ability to deploy updates after the 'anniversary' release.

Edited April 22, 2016 by psydii

[IanN]

Reading the comments after that blog I would argue that potentially this is still not fixed.

[kennysarmy]

Think I've just been caught out by this

[kennysarmy]

Just to update:

 

Installing KB 3159706 also bricked our WSUS.

 

If anyone knows of a fix let me know as for now I've had to uninstall that update and reboot to get WSUS console accessible again.

 

Regards

[kennysarmy]

Does anyone know if this fixed the issue post install of the KB

 

https://support.microsoft.com/en-us/kb/3159706

[Steve21]

Does anyone know if this fixed the issue post install of the KB

 

https://support.microsoft.com/en-us/kb/3159706

 

Worked on ours fine. Just make sure to do the extra bits after the install of the update

 

Steve

[andydis]

WSUS TIPS from my knowledgebase :-

 

If you have KB3148812 - remove it.

If you have KB3159706 - remove it.

 

increase the memory of the application pool:

https://blogs.technet.microsoft.com/configurationmgr/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors/

 

Server Cleanup crashes or takes forever:-

(Do them in correct order)

 

https://blogs.msdn.microsoft.com/jjameson/2009/03/28/wsus-server-cleanup-wizard-hangs-on-deleting-unused-updates/

[ajs]

Out of interest, why remove KB3159706 rather than following (or scripting) the post-install configuration items to allow the WSUS console to work again?

[KevinH]

Out of interest, why remove KB3159706 rather than following (or scripting) the post-install configuration items to allow the WSUS console to work again?

 

Removing it was a good strategy for people who aren't planning on Windows 10 and it was a "quick fix" for this update (and 8812) borking the universe - for those who's WSUS server didn't update from itself - or have blanket auto approval rules.

 

My WSUS server - gets its updates from WSUS, and the tragedy showed up on the web long before I would have approved either one, and the manual config actions had been documented and tested before I released it.

 

Long-term, best to just do the manual configuration - but for those who are riding 7 into the ground (count me as one) it is easier to just decline/hide.

[ajs]

Fair enough. I remember the initial panic at work when it first came out and the post-install steps hadn't been fully released/spotted.