WSUS Installation Fails with No Specified Error and ‘Tools’ Folder is Missing after WSUS Installation


  • When installing WSUS through the Add Roles and Features Wizard (ARW), the Post-Installation task fails and the generated log folder (*.tmp) is empty, AND
  • The Tools folder is missing after WSUS was installed. Note: By default, the Tools folder is installed to the following location: %SystemDrive%\Program Files\Update Services\Tools


This behavior has been seen when:

  • Uninstalling WSUS
  • Manually deleting WSUS folder: %SystemDrive%\Program Files\Update Services
  • Manually deleting WSUS registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services
  • Re-installing WSUS


Root Cause

When uninstalling WSUS Role via ARW the “API and PowerShell cmdlets” feature is not uninstalled by default (unless explicitly selected by the user). Deleting the remaining WSUS folders and registry keys leaves the server in a bad state and the re-installation fails because it is expecting this feature to be already installed.



Uninstall all the WSUS roles and features and re-install WSUS.


Workaround 1: To uninstall WSUS roles and features using Windows PowerShell

  1. In PowerShell, review features installed by calling: Get-WindowsFeature UpdateServices*
  2. To remove features, call: Uninstall-WindowsFeature <featureName>


Workaround 2: To uninstall WSUS roles and features using the Server Manager Console

In Server Manager, launch Remove Roles and Features Wizard (RRW), unselect items to be uninstalled, and complete the Wizard:

  1. In Server Roles tab unselect ‘Windows Server Update Services’ option
  2. In Features tab unselect ‘Remote Server Administration Tools -> Role Administration Tools -> Windows Server Update Services Tools’ option


We recommend restarting the server to ensure that all WSUS components are removed. After uninstalling WSUS roles and features, you may reinstall the WSUS roles and features.


To reinstall WSUS, launch the Add Roles and Features Wizard and then select the “Windows Server Update Services” option. You may optionally reinstall the Windows Server Update Services Tools. After the ARW completes successfully, you may run the WSUS post-installation tasks.

Comments (18)

  1. very good article indeed thank you

  2. Garrett Dumas says:

    This worked for me. Thanks.

  3. Anonymous says:

    227 Microsoft Team blogs searched, 58 blogs have new articles. 225 new articles found searching from

  4. Andrew says:

    Thank you very much. I was trying to do a clean reinstall of WSUS ran into this problem after uninstalling and doing the manual deletions. Your work arounds took me a couple ties because I when I clicked remove WSUS in the ARW it has a pop up windows to remove features related to WSUS. I though this was your step 2 but it is not. I still needed to do your step 2 and once I did it worked. Thank you again this has fix several days of frustrations

  5. Abhay says:

    Awesome, it took forever to find out root cause. Thank you for article

  6. William says:

    Guys for some reason I am unable to install WSUS on my Server 2012 R2. It keeps error-ing out saying Post Installation Failed. This is a brand new server, new install. The only thing on it is Symantec. What am I doing wrong? I got machines I cannot update…so

  7. Daniel says:

    Hey, thanks for this. I was losing my mind trying to figure it out when I saw the damn .tmp’s were empty. HOW COULD ANY PROGRAM ALLOW BLANK LOG FILES TO GET CREATED BAAAHHH.

    Thanks though, man!

  8. Peter says:

    Unfortunately this doesn’t work for me. I found wsutil via a search on th eOS, manually created the Tools directory and placed wsutil in the directory. Installation via command line worked fine, but the installation did not create a console? What to do?

  9. hiphop says:

    thank you Hiphop, Rap, Ceza, sagopa, Kolera Hiphop, Rap, Gekko G Animasyon

  10. pansadi says:

    Thanks for the its much appreciated..

  11. E says:

    THANK YOU!! This is the solution that I’ve been looking for! Now, if I can only figure out why my clients are not showing up in WSUS, I’ll be ecstatic!

  12. anonymouscommenter says:

    Thanks, this has been driving me up the wall

  13. Paddy says:

    Thanks, this has been driving me up the wall

  14. seedyj says:

    Old but gold thanks for this

  15. Hethu says:

    I wasted days trying to find a cause. Thanks for the excellent post!

  16. Heresh says:

    HI, I have a different issue.
    The “Post-deployment configuration” cannot start since WSUS is trying to use a user which doesn’t have any rights.
    When adding the user with rights to the “Wsus Service” and then running the configuration the configuration still uses the wrong user.
    Any idea of how I can change the user for the configuration?

    A printout from the log file:
    2016-08-05 11:06:03 CreateDefaultSubscription failed. Exception: System.Data.SqlClient.SqlException (0x80131904): Login failed for user ‘XXX\WIN-WSUS-01$’.

    There is no user in XXX domain with that name. I have created a user in the domain and added it to “logon” tab in services and everything is correct there

    1. The post-install operation works on the database, so the user running it must be an administrator of the SUSDB. Whether it’s SQL or WID, if they cannot access and modify the SUSDB, then post-install will not work as expected.

Skip to main content