WSUS Content folder still empty after running wsusutil.exe /RESET RRS feed

  • Question

  • I was trying to do a cleanup of updates on a 2008 R2 server. I followed the steps in this link https://blogs.technet.microsoft.com/gborger/2009/02/27/what-to-do-when-your-wsuscontent-folder-grows-too-large/ and have followed the steps of stopping the service and deleting content of WSUSContent folder, i then ran the reset command and started the service. I now cannot view any updates in WSUS as when I try to expand this I get Error: Connection Error. Also i would have expected content to start to re appear in the wsuscontent directory but this is not happening either. Any ideas appreciated.
    Monday, February 5, 2018 2:28 PM

All replies

  • Hi,

    After executing "Reset" command you may check the SQL related process  with high CPU usage :


    Take a look in Task Manager and you’ll see that the process “SQL Server Windows NT – 64 bit” is consuming all the CPU. This is because all database tables are being checked and any missing hotfixes are being marked for download.

    This could take up to 30-60 minutes to complete, depending on the Products and Classifications you have. When the CPU drops you’re ready to proceed.



    Please wait it for a while , then, sync again as the article above mentioned  .

    Best Regards,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 6, 2018 5:27 AM
  • As for your actual issue, be patient. Go away from it for a couple of DAYS... Just let it be. WSUS is slow. Trust that it's doing something... after a couple of days, go check - if you're still having issues, re-do the steps for the reset AFTER you restart the server.

    While I can't help you specifically with the process as Elton explained it well, I can offer an alternative after your WSUS system is back up. You wouldn't have had to run the wsusutil.exe reset command had you used WAM.

    Please have a look at the WSUS Automated Maintenance (WAM) system. It is an automated maintenance system for WSUS, the last system you'll ever need to maintain WSUS!


    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Adam Marshall, MCSE: Security
    Microsoft MVP - Windows and Devices for IT

    Tuesday, February 6, 2018 2:06 PM