執行以下命令：C:\Program Files\Update Services\Tools\wsusutil postinstall /servicing
參考：http://www.urtech.ca/2016/08/solved-wsus-server-will-not-launch-after-august-patch-cycle-including-kb3159706/
To allow WSUS (and presumably SCCM) to support Windows 10 Anniversary, Microsoft released a patch last month which blew up a number of WSUS servers. They have now released KB3159706 which is supposed to fix that problem and support Windows 10 Anniversary. This patch installs on WSUS servers through the normal Windows Update process so even if you are not running Windows 10 or care about Anniversary, you will receive that patch. The problem is that it REQUIRES a number of MANUAL steps to complete the install and if you don’t, your WSUS console will not launch.
You can read https://support.microsoft.com/en-us/kb/3159706 and https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ for full details but it boils down to:
- Run a patch cycle on the server that host your WSUS, reboot and then ensure that KB3159706 is installed
- From an elevated command prompt run: “C:\Program Files\Update Services\Tools\wsusutil.exe” postinstall /servicing This takes more than a few seconds to complete.
- SERVER MANAGER > ROLES & FEATURES > .NET FRAMEWORK 4.5 FEATURES > add HTTP ACTIVATION
- Restart WSUS SERVICE
- Launch the WSUS console and all should be well
- If you are using SSL on the WSUS you need to read the bottom of KB3159706
- If you check your WSUS > OPTIONS > PRODUCTS AND CLASSIFICATIONS, UPGRADES should now be listed and function correctly