WSUS Crashed after HOTFIX Installation

WSUS Crashed after HOTFIX Installation.

• Fix the DCOM issue - Check for DistributedCOM event 10016 in the System Event log for APPID for example {B292921D-AF50-400C-9B75-0C57A7F29BA1}

1. If you have Windows Server 2008 R2, you have to give yourself permission to change the settings of the Component Service by looking for the APPID in the windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID. Then change the permissions of the Key by taking ownership of the object and give Full Permissions to the local Administrator-Group. After that you can change the DCOM Permissions in the Component Services.
2. Open Administrative Tools > Component Services
3. Within Component Services, open Computers > My Computer > DCOM Config
4. Find the NAP Agent Service, right-click it, and open Properties.
5. Under the security tab, hit "Edit..." under the Launch and Activation Permissions section.
6. Give the SYSTEM user allow for Local Launch.

• Enable Named Pipes for the local SQL Server Express install - Check for MSSQL$MICROSOFT##SSEE event 18456 in the Application event log

1. Open the Sql Server Configuration Manager (Start > Programs > Microsoft SQL Server 2008 R2 > Configuration Tools)
2. SQL Server Network Configuration  > Protocols for MICROSOFT##SSEE
3. Open Properties for Named Pipes and set Enabled to Yes.

• Put the SUSDB database back into multi-user mode (might not be necessary, but I did it)

1. Open a command prompt as administrator and run "iisreset /stop"
2. Stop the "Update Services" service if running (it usually isn't since it's broken at this point)
3. Open SQL Server Management Studio as Administrator (Start > Programs > Microsoft SQL Server 2008 R2)
4. Under Server type, select "Database Engine", for server name, use "\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query", and for Authentication use "Windows Authentication". Click Connect.
5. Look at your SUSDB (Databases > SUSDB). If it is in single-user mode, open its properties, go to the Options screen, and set the Restrict Access setting to "MULTI_USER". Let it reset connections if needed.
6. Reboot your server (might not be necessary, but I figured it was best to play it safe)
7. You might see a lot of MSSQL$MICROSOFT##SSEE event 33002 in the logs after the reboot, but you can ignore these for now since the patch "should" fix it in a bit.

• Extract necessary files from 2720211 installer

1. Download the KB2720211 installer for your architecture from Microsoft for example (http://support.microsoft.com/kb/2720211)
2. Extract WUSSetup.msp from the installer by running the installer with the /extract parameter (example: "WSUS-KB2720211-x64.exe /extract")
3. With 7-zip, open WUSSetup.msp and extract "PCW_CAB_SUS".
4. With 7-zip, open "PCW_CAB_SUS" and extract "DbCert", "DbCertDll", and "DbCertSql".
5. Rename those files to "WSUSSignDb.cer", "WSUSSignDb.dll", and "WSUSSignDb.sql", respectively.
6. On your WSUS server, navigate to "C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\SchemaSig" and copy the extracted "WSUSSignDb.cer" and "WSUSSignDb.dll" to it. Make a backup copy of the two existing versions, just in case.
7. On your WSUS server, navigate to "C:\Program Files\Update Services\Database" and copy the extracted "WSUSSignDb.sql" to it. Make a backup copy of any existing versions of the file.

At this point, you should (cross your fingers!) be able to try reinstalling the 2720211 patch and see if it finishes. If it does, your WSUS should be back to normal.
I hope it works for you!