Repair Windows Server Update Services
Updated: March 24, 2009
Applies To: Windows SBS 2008
Problem One or more of the following:
- Updates are not being applied to the server that is running Windows SBS 2008 or to domain-joined client computers.
- On the Home tab, in the Network Essentials Summary, the Updates status is Not Available.
- On the Security tab, the Updates status does not display any data, or there are warning messages saying that update information cannot be obtained.
- After generating a report, on the Reports tab, if you click the report no data is displayed.
Solution Do the following:
- Verify that the following services are running. If any of them are not running, restart them. For instructions about how to verify whether a service is running and to restart it, see the procedure titled “To verify that a service is running” later in this document.
- Update Services
- Windows Internal Database (Microsoft##SSEE)
- World Wide Web Publishing Service
- Update Services
- Determine whether you have Internet connectivity: In the Windows SBS Console, click Network, click Connectivity, and then verify that the Internet Connection status is Connected. If it is not connected, click Fix my network, and then complete the wizard.
- Reinstall and reconfigure Windows Server Updates Services (WSUS). For instructions about how to do this, see the procedure titled “To manually recover Windows Server Update Services” later in this topic.
-
Click Start, click Administrative Tools, and then click Services.
-
On the User Account Control page, click Continue.
-
In the Services (Local) list, find the service that you want to verify, and then check its status. If it is stopped or paused, restart it by right-clicking it and then clicking Restart.
-
Click Start, click Control Panel, click Programs, and then click Programs and Features.
-
Verify whether Microsoft Windows Server Update Services <version x> is listed, where <version x> is the version that you are running (for example, 3.0 SP1). If it is listed, skip to Step 4.
-
Verify that a WSUS subdirectory does not exist on any of the server volumes. If there is a WSUS subdirectory, delete it, and then do the following:
- Create a directory called WSUS on the C: partition.
- Insert Windows SBS 2008 Disc 2 (Component Technologies for Server Repair) into the server that is running Windows SBS 2008.
- Open an elevated command line prompt, type
<DVD Drive>:\CMPNENTS\wsus\wsussetup.exe /q DEFAULT_WEBSITE=0 CREATE_DATABASE=1 CONTENT_LOCAL=1 CONTENT_DIR=C:\WSUS WYUKON_DATA_DIR=C:\WSUS, where <DVD Drive> is the DVD drive for the computer, and then press ENTER.
Note It may take up to 10 minutes for the process to finish.
- Create a directory called WSUS on the C: partition.
-
Apply the Windows SBS 2008 configuration settings for software updates by doing the following:
- Click Start, click Administrative Tools, and then click Microsoft Windows Server Update Services <version x>, where <version x> is the version that you are running (for example, 3.0 SP1).
- On the User Account Control page, click Continue.
- In Update Services, expand the name of the server that is running Windows SBS 2008, and then click Options.
- Click Products and Classifications, and then, on the Products tab, verify that all check boxes are selected.
- In the Products and Classifications dialog, click the Classifications tab, and then verify that the following check boxes are selected:
- Critical Updates
- Definition Updates
- Security Updates
- Service Packs
- Update Rollups
- Critical Updates
- Click OK.
- In Options, click Update Files and Languages, and then verify that Store update files locally on this server and Download update files to this server only when updates are approved are selected.
- Click the Update Languages tab, select Download updates only in these languages, and then verify that English is selected.
You can also select any additional languages that you want to use for synchronizing software updates. - Click OK.
- In Options, click Synchronization Schedule.
- In the Synchronization Schedule dialog, click Synchronize automatically, and then, in First synchronization, change the time to 10:00:00 P.M.
- Set the Synchronizations per day to 1, and then click OK.
- In Update Services, expand Computers, click All Computers, and then, in Actions, click Add Computer Group.
- In the Add Computer Group dialog, type Update Service Excluded Computers, and then click Add.
- In Actions, click Add Computer Group, type Update Services Client Computers, and then click Add.
- In Actions, click Add Computer Group, type Update Services Server Computers, and then click Add.
- Click Start, click Administrative Tools, and then click Microsoft Windows Server Update Services <version x>, where <version x> is the version that you are running (for example, 3.0 SP1).
-
Create three Group Policy objects by doing the following:
Note If any of these Group Policy objects already exists, do not recreate it, but verify its settings. - On the server that is running Windows SBS 2008, click Start, click Administrative Tools, and then click Group Policy Management.
- On the User Account Control page, click Continue.
- Expand Forest, expand Domains, and then expand the domain name of the server that is running Windows SBS 2008.
- Right-click Group Policy Objects, and then click New.
- Type Update Services Client Computers Policy, and then click OK.
- Right-click Group Policy Objects, and then click New.
- Type Update Services Common Settings Policy, and then click OK.
- Right-click Group Policy Objects, and then click New.
- Type Update Services Server Computers Policy, and then click OK.
- On the server that is running Windows SBS 2008, click Start, click Administrative Tools, and then click Group Policy Management.
-
Verify the Group Policy settings for Update Services Client Computers, Update Services Common Settings, and Update Services Server Computers by doing the following:
- Click the Update Services Client Computers Group Policy object, which you created, and then click the Settings tab.
- Right-click Computer Configuration, and then click Edit. The Group Policy Management Editor is displayed.
- Expand Computer Configuration, expand Policies, expand Administrative Templates, expand Windows Components, and then click Windows Update.
- Double-click Configure Automatic Updates, and then, in the Configure Automatic Updates Properties dialog, do the following:
- For Configure Automatic Updates, click Enabled.
- For Configure automatic updating, click 4 – Auto download and schedule the install.
- For Scheduled install day, click 0 – Every day.
- For Scheduled install time, click 03:00.
- Click OK.
- For Configure Automatic Updates, click Enabled.
- Close the Group Policy Management Editor.
- In the Group Policy Management Console, click the Update Services Common Settings Group Policy object, which you created, and then click the Settings tab.
- Right-click Computer Configuration, and then click Edit. The Group Policy Management Editor is displayed.
- Expand Computer Configuration, expand Policies, expand Administrative Templates, expand Windows Components, and then click Windows Update.
- Double-click Configure Automatic Updates, verify that Configure automatic updating is set to 2 – Notify for download and notify for install, and then click OK.
- Double-click Automatic Updates detection frequency, and then do the following:
- Click Enabled.
- For Check for updates at the following interval (hours), type 1.
- Click OK.
- Click Enabled.
- Double-click Allow non-administrators to receive update notifications, click Enabled, and then click OK.
- Double-click Allow Automatic Updates immediate installation, click Enabled, and then click OK.
- Double-click Delay Restart for scheduled installations, and then do the following:
- Click Enabled.
- For Wait the following period before proceeding with a scheduled restart, type 5.
- Click OK.
- Click Enabled.
- Double-click Specify intranet Microsoft update service location, and then do the following:
- Click Enabled.
- For Set the intranet update service for detecting updates, type http://<computername>:8530, where <computername> is the name of your server that is running Windows SBS 2008.
- For Set the intranet statistics server, type http://<computername>:8530, where <computername> is the name of your server that is running Windows SBS 2008.
- Click Enabled.
- Double-click No auto-restart with logged on users for scheduled automatic updates installations, click Disabled, and then click OK.
- Double-click Re-prompt for restart with scheduled installations, and then do the following:
- Click Enabled.
- For Wait the following period before prompting again with a scheduled restart (minutes), type 10.
- Click OK.
- Click Enabled.
- Double-click Reschedule Automatic Updates scheduled installations, and then do the following:
- Click Enabled.
- For Wait after system startup (minutes), type 1.
- Click OK.
- Click Enabled.
- Close the Group Policy Management Editor.
- In the Group Policy Management Console, click the Update Services Server Computers Group Policy object, which you created, and then click the Settings tab.
- Right-click Computer Configuration, and then click Edit. The Group Policy Management Editor is displayed.
- Expand Computer Configuration, expand Policies, expand Administrative Templates, expand Windows Components, and then click Windows Update.
- Double-click Configure Automatic Updates, verify that Configure automatic updating is set to 3 – Auto download and notify for install, and then click OK.
- Close the Group Policy Management Editor.
- Click the Update Services Client Computers Group Policy object, which you created, and then click the Settings tab.
-
In the Group Policy Management Console, do the following:
- In the tree pane, click the domain name.
- In Results, verify whether the Group Policy objects that you created in Step 5 are listed as Linked Group Policy Objects.
- If they are not linked, in the tree view, right-click the domain name, and then click Link an Existing GPO.
- Click one of the Group Policy objects that you created, and then click OK.
- Repeat Steps 7b-7d until all Group Policy objects are linked.
- In the tree pane, click the domain name.
To read the most recent version of this topic, see the Microsoft Web site (http://go.microsoft.com/FWLink/?LinkID=147048). The most recent version might contain additional information that was not available when Windows SBS 2008 was released.
I moved the WSUS Repository just after the installation of SBS 2008.
A year later I attempted the installation of WSUS 3.0 SP2 and it failed.
I completed this procedure and WSUS still did not work.
I was able to trace the problem down to the fact that WSUS, on the server after the failure and after executing this procedure, was configured to have the repository on the C:\ drive.
However, the IIS site was was still pointed to the location on the D:\ Drive.
I used the SBS Console->Server Storage Tab and moved the repository to the D:\ Drive.
- 6/20/2011
- Scotty Croy
- 5/31/2011
- TekkkTom
my issue is that i cant install or reinstall oder repair the corrupt wsus 3.0 sp1 installation on my sbs 2008..
here my log-file from last wsus test install (SP2):
2011-05-10 02:28:19 Success MWUSSetup Validating pre-requisites... 2011-05-10 02:28:19 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: Das System kann die angegebene Datei nicht finden.) 2011-05-10 02:28:19 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: Der Vorgang wurde erfolgreich beendet.) 2011-05-10 02:28:23 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9. 2011-05-10 02:28:23 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9. 2011-05-10 02:29:03 Success MWUSSetup Initializing installation details 2011-05-10 02:29:03 Success MWUSSetup Skipping Asp.Net install since not running on win2k3... 2011-05-10 02:29:03 Success MWUSSetup Installing wYukon using ocsetup 2011-05-10 02:29:03 Success MWUSSetup Windows Internal database is already installed on this machine 2011-05-10 02:29:03 Success MWUSSetup Installing WSUS... 2011-05-10 02:29:07 Success CustomActions.Dll Unable to get INSTALL_LANGUAGE property, calculating it... 2011-05-10 02:29:08 Success CustomActions.Dll Successfully set propery of WSUS admin groups' full names 2011-05-10 02:29:08 Success CustomActions.Dll .Net framework path: C:\Windows\Microsoft.NET\Framework64\v2.0.50727 2011-05-10 02:29:11 Success CustomActions.Dll Creating user group: WSUS-Berichterstatter with Description: WSUS-Administratoren, die nur Berichte auf dem Windows Server Update Services-Server ausführen können. 2011-05-10 02:29:11 Success CustomActions.Dll Creating WSUS-Berichterstatter user group 2011-05-10 02:29:12 Success CustomActions.Dll WSUS-Berichterstatter user group already exists 2011-05-10 02:29:12 Success CustomActions.Dll Successfully created WSUS-Berichterstatter user group 2011-05-10 02:29:12 Success CustomActions.Dll Creating user group: WSUS-Administratoren with Description: WSUS-Administratoren können den Windows Server Update Services-Server verwalten. 2011-05-10 02:29:12 Success CustomActions.Dll Creating WSUS-Administratoren user group 2011-05-10 02:29:12 Success CustomActions.Dll WSUS-Administratoren user group already exists 2011-05-10 02:29:12 Success CustomActions.Dll Successfully created WSUS-Administratoren user group 2011-05-10 02:29:12 Success CustomActions.Dll Successfully created WSUS user groups 2011-05-10 02:29:12 Success CustomActions.Dll Succesfully set binary SID property 2011-05-10 02:29:12 Success CustomActions.Dll Succesfully set binary SID property 2011-05-10 02:29:12 Success CustomActions.Dll Successfully set binary SID properties 2011-05-10 02:31:49 Error MWUSSetup InstallWsus: MWUS Installation Failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.) 2011-05-10 02:31:49 Error MWUSSetup CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.) 2011-05-10 02:31:49 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.) 2011-05-10 02:31:57 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.)
the first what ive done was to restore the folders "update services" and "WSUS" because they are corrupt. next what ive done is to manually creat the missing WSUS-Sites and Applications in IIS7. after reboot same problem. the service "update services" do not run after restart it.
whats wrong? i have tested all solutions ive found on google.
1) delete all wsus registry entries ive found
2) delete corrupt "update service" folder under program files
3) delete all wsus-iis-sites and content directory
4) reboot server
5) manually wsus-repair with this solution above
install faild with same failure
second ive tested:
1) delete all wsus registry entries ive found
2) uninstall sharepoint
3) uninstall windows internal database
4) reboot server
5) manually wsus install with this soultion above
normaly uninstall with server-manager or program and functions not possible
normaly install with add server-role not possible
my user have all needed permissions in the system
please help..
- 5/10/2011
- Richy_ABComputer
Installing WSUS SP2 failed and broke WSUS on the SBS 2008 Box.
When running through the repair;
1. The command comes back almost isntantly after entered in command prompt.
2. I can see the C:\WSUS contents being created and then shared.
a. After that, the folders appear to be deleted.
3. I can see the msiexec.exe process running.
a. Left running for 15minutes then returned and the processes was not longer running.
The problem.
1. WSUS appears to be completely uninstalled
2. Noted the following Error in Event viewer:
Log Name: Application
Source: MsiInstaller
Date: 15/12/2010 10:23:27 AM
Event ID: 11722
Task Category: None
Level: Error
Keywords: Classic
User: DOMAINNAME\servername
Computer: SERVERNAME.domain.local
Description:
Product: Microsoft Windows Server Update Services 3.0 SP1 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action PERF_COUNTER_INST, location: C:\Program Files\Update Services\Setup\HideConsoleApp.exe, command: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\InstallUtil.exe /LogFile="C:\Users\fwadmin\AppData\Local\Temp\2\WSUSCa_101215_1022.log" /ShowCallStack /WsusInstall /CategoryMessageFile="C:\Program Files\Update Services\Common\EventCategories.dll " "C:\Program Files\Update Services\Setup\bin\Microsoft.UpdateServices.Setup.CustomActions.dll
- 12/15/2010
- Rlib
- 8/11/2010
- tfoekens
- 8/16/2010
- Thomas Lee
- 10/31/2009
- Wayne Small
- 7/24/2010
- PKTSe7en
Does anyone know how to fix it now showing in SBS console ?
- 2/13/2010
- SGSMikeG
Upgrading to WSUS 3.0 from WSUS 2 0
When upgrading to WSUS 3.0 from WSUS 2.0, the configuration points to the port 8530. This causes a mismatch in the WSUS environment because other machines are configured to point to the original port (80) of this WSUS server. In this case, the WSUS 3.0 port should be switched back to 80 by using the following syntax.
Open cmd in admin mode and run:
C:\Program Files\Update Services\Tools>WSUSUtil.exe useCustomWebsite false
Open in the SBS2008 admin tool the update service applications and check if the services is available again.
Open in the SBS2008 console the security updates tab and check if behaves normal again.
Firstly the SP2 update broke down the WSUS 3.0 installation completely: Updates were no longer downloaded, SBS console could not retrieve any information (generated errors) and the event log showed some Update errors especially
HRESULT: 0x80244019. To fix this:
* Uninstall WSUS 3.0 SP2, and remove everything. You can leave the WSUS dir in place, as it will give an "in use error" when you try to delete it.
* Install WSUS 3.0. SP2 using the settings/parameters provided from step 4. in the section "To manually recover Windows Server Update Services" in the guide above.
NOTE1: you'll notice that you can skip a lot of steps, or use them to check the settings currently/already applied.
NOTE2: It will perform a new synchronisation, meaning it will download all needed updates again.
NOTE3: You might also want to check the permissions on the GPO's. Especially when you have to (re)create them from scratch
Update: After running the procedure, I was able to get the Update Services to open, but the SBS Console is still broken, so if you have the SBS Console Update "Not Available" error that I was having, this procedure did not solve that problem (after 3 hours of work and synchronization no less).
- 12/3/2009
- John Montgomery
- 12/3/2009
- John Montgomery
- 11/4/2009
- Geo de Maré
