Active10 months ago
Anyone know of a way to completely wipe WSUS of updates and start again?
Installing and Configuring Windows Server Update Services with Windows Server 2016 Core. Install Windows Server Update Services (WSUS). You can also clean up the WSUS database manually using the Server Cleanup Wizard found in Options. The new Windows Update Cleanup installs and plugs in to the standard Windows 7 Disk Cleanup wizard maintenance utility. Once installed, Windows Update Cleanup becomes just another option you can choose in the wizard. Of course, there are a couple caveats: After cleanup you may be unable to roll back to a superseded update.
It seems as if I have loads of language packs and assorted rubbish in the list which we do not need. Having now removed all the unwanted Products, Classifications and Languages what I would like to do is completely clean out the WSUS database and start again. It appears that uninstalling the reinstalling the WSUS role does not help they are all still there. Have also tried the Server Cleanup wizard which seems to be mostly a waste of time, it didn't clean up any of the updates I was hoping it would remove.
I haven't yet installed any of these on a machines yet so if only I could work out how I could completely wipe all listed updates and start again but according to my new reduced Products list.
Thanks, Nick
- The tool will conduct preliminary checks and test the communication between the WSUS Server and the client machine. Once the tool has completed the tests it will display the results in the console window. The Windows Server Update Services Client Diagnostic tool is provided AS IS. No product support is available for this tool.
- Troubleshooting WSUS 3.0 SP2 on windows server,- In the post we will see steps to troubleshoot WSUS 3.0 SP2 related issues. Windows Installer logs that information.
- Let’s learn how to clean up WSUS content folder. You could always search and decline all updates you don’t want and then run the Server Cleanup Wizard, but its PITA. My WSUS folder went from 75 GB to 20 GB so I’m happy. 2,797 views How To Clean Up WSUS; 793 views Windows 2016 Migration.
1,1801111 gold badges3131 silver badges5151 bronze badges
3 Answers
To re-install WSUS with a clean database i.e. no previous configuration:
Run Windows Powershell as Administrator and use the following commands:
Uninstall-WindowsFeature -Name UpdateServices,Windows-Internal-Database -Restart
- Post restart, delete EVERYTHING in the
C:WindowsWID
(for Win 2012 r2) folder. - Then run the following command to re-install WSUS:
![Msicuu2.exe Msicuu2.exe](/uploads/1/2/6/4/126450921/722419759.png)
This only works on PowerShell 3 or higher.
More info here: Microsoft TechNet: Removing Server Roles and Features
More info here: Microsoft TechNet: Removing Server Roles and Features
DamoDamo
Answer now found, just posting this for the benefit of anyone else who might come across this problem.
It seems that uninstalling
WSUS
and WID Database
option does not actually remove the WID database.- The WID database can be removed by uninstalling the
Windows Internal Database
feature. - You will also need to manually delete the file
C:windowsWIDDatasusdb.mdf
before re-installing everything again.
1,1801111 gold badges3131 silver badges5151 bronze badges
![Windows Installer Cleanup Utility Wsus Console Windows Installer Cleanup Utility Wsus Console](/uploads/1/2/6/4/126450921/817608827.jpg)
There is now an official blog post out:
- TechNet Blogs: 2016-10-18, Meghan Stewart, Recreating the SUSDB and WSUS Content folder for a Windows Server 2012 based WSUS computer (Archived here.)
This is my unofficial summary of the official blog post:
- stop-service WSUSService, W3SVC
- connect with SQL Server Management Studio (SSMS).
- Use SSMS to backup SUSDB
- Use SSMS to delete SUSDB
- Rename content directory
- Recreate content directory
- start-service WSUSService, W3SVC
- Run Program FilesUpdate ServicesTools.Wsusutil.exe postinstall (see blog for command line parameters)
- Done.
For WS2012/WS2012R2:Connecting to the Windows Internal Database requires the use of a Named Pipes connection. The connection string you want is:
.pipeMICROSOFT##WIDtsqlquery
For WS2003/WS2008/WS2008R2:Connecting to the Windows Internal Database requires the use of a Named Pipes connection. The connection string you want is:
.pipeMSSQL$MICROSOFT##SSEEsqlquery
StackzOfZtuffStackzOfZtuff
Windows Installer Cleanup Utility Download
protected by Community♦Sep 8 '15 at 17:06
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Would you like to answer one of these unanswered questions instead?