Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Uninstalling WSUS on Primary Site server causing HTTP Error 500

Posted on March 28, 2014March 28, 2014 by Jörgen Nilsson

I have ran into this a couple of times now when moving site roles in Configuration Manager 2012. When uninstalling the WSUS server components from in this case the Primary Site server to move it to a dedicated server instead the Management Point on the Primary Site server started giving HTTP Error 500 Internal Server Error:

RemoveWSUS1

This was caused by the removal of the WSUS role on the server which removed almost all the files installed by the Windows Update Services but not the configuration written in the ApplicationHost.config file. The Applicationhost.config file tries to call the .dll installed by the WSUS Server but no longer exists on the system.

From the Applicationhost.config file:

<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true” dll=”C:\Windows\system32\inetsrv\suscomp.dll” staticCompressionLevel=”10″ dynamicCompressionLevel=”0″ />

<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true” dll=”C:\Program Files\Update Services\Webservices\suscomp.dll” staticCompressionLevel=”10″ dynamicCompressionLevel=”0″ />

Running the following command will remove all references to the module installed by WSUS.

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

After that the Management Point is up and running again.

40 thoughts on “Uninstalling WSUS on Primary Site server causing HTTP Error 500”

  1. Denis says:
    May 7, 2014 at 11:13 pm

    Thank you. It solved our problem.

    Reply
  2. Satoru Nasu says:
    October 31, 2014 at 8:34 am

    Nice post, thank you.
    I could uninstall WSUS from Windows Server 2012 R2 Essentials safely.

    Reply
  3. Dave says:
    February 4, 2015 at 6:07 pm

    Made the mistake of fooling around on our production Site Server. Installed WSUS and then removed it. The next day I realized clients weren’t getting their policies. I knew it was the removal of SUS that did it. I was panicking and thought I was going to have to do a restore. Ran this command and it fixed the issue beautifully. Thanks a lot!!

    Reply
  4. Alexey Rotman says:
    March 27, 2015 at 7:53 pm

    Thank you!!!
    It solved our problem.
    Windows Server 2012 R2 Essentials

    Reply
  5. Mike C says:
    April 10, 2015 at 10:19 am

    Very very useful post, required to resolve a very critical issue caused by WSUS removal!!!

    Thanks for taking the time to help others.

    Reply
  6. Mike C says:
    April 10, 2015 at 10:26 am

    Also worth mentioning that the Application Catalog failed with http 500 due to WSUS removal also. The above fix resolved same.

    Reply
  7. GerardvSt says:
    June 12, 2015 at 8:07 am

    You saved my day! 🙂 Thanks a lot!

    Reply
  8. Zelto says:
    November 10, 2015 at 8:09 pm

    I was facing exactly this issue.
    Perfect solution. Thank you!!!

    Reply
  9. Scoot says:
    January 25, 2016 at 8:38 pm

    Thank you!
    Saved our day.
    I installed WSUS on our production 2012r2 Essentials server and thought it was great! But then I could not get reporting to work, and did not like the resources it was consuming on the only server in house that does a few other roles as well (Quickbooks db and Mongo db). Thought it would be smart to uninstall, and was confronted with this lovely 500!
    Thanks!

    Reply
  10. Najeeb says:
    February 4, 2016 at 2:04 pm

    Thank you . It worked for me

    Reply
  11. Lee says:
    March 15, 2016 at 3:07 pm

    Thanks, saved me a load of time working this out.

    Reply
  12. Kenny says:
    March 22, 2016 at 1:55 pm

    Brilliant fix. Thanks very much

    Reply
  13. Ashley John says:
    May 23, 2016 at 3:21 pm

    Had an issue with WSUS uninstall, the install finished fine, I restarted the server and RWA no longer accessible (error 500). The above fixed fantastically well!
    MANY MANY THANKS!!!

    Reply
  14. John says:
    June 18, 2016 at 5:58 pm

    This fixed us right up, THANK YOU!!!

    Reply
  15. Garrett says:
    September 19, 2016 at 11:30 pm

    Thank you for this helpful post! Are there any considerations to be made for deleting SUSDB? In our case, we won’t be migrating it to a different SQL instance. Thanks again!

    Reply
  16. Logan says:
    September 29, 2016 at 6:33 pm

    Thanks, this worked flawlessly to fix a Server Essentials Connector 500 issue.

    Reply
  17. Sebastian says:
    December 27, 2016 at 3:40 pm

    Great solution, thank you very much! This saved our day(s).

    Reply
  18. Janne says:
    February 14, 2017 at 1:21 pm

    I have been struggling with this problem and just gave up and installed WSUS again.
    Now I will try our solution.

    Regards Janne

    Reply
  19. Shun says:
    March 2, 2017 at 6:47 am

    Thank you!
    You saved me.

    Reply
  20. Vern says:
    April 25, 2017 at 12:01 am

    Thanks for this..saved my day!!

    Reply
  21. Ahmed says:
    July 5, 2017 at 4:32 am

    when I run the command I get this message
    “ERROR ( message:Cannot find requested collection element. )”

    please help , thanks

    Reply
  22. Charles Katzke says:
    July 6, 2017 at 12:04 pm

    Thank you this was exactly my problem.

    Reply
  23. Eddie says:
    May 4, 2018 at 1:15 am

    For the record, this solution also works with Windows Server 2016! After I uninstalled WSUS, it broke my web server, and it was driving me crazy. Running the appcmd cleared up the error right away. Thanks for the fix!

    Reply
  24. Russ says:
    May 31, 2018 at 1:55 am

    I recommend fixing this properly otherwise you will see a huge increase in WSUS traffic due to no compression being used. 10:1 difference. I’ll blog it soon. Search for configmgrgeekspeak suscomp.dll in a week or two.

    Reply
    1. Russ says:
      May 31, 2018 at 2:00 am

      PS disregard my comment above if you’re permanently removing WSUS from the server you run the command on for good.

      Reply
  25. Milena says:
    June 29, 2018 at 12:15 pm

    Thank you!
    You saved me.
    Perfect solution.

    Reply
  26. Keith says:
    September 19, 2018 at 11:59 am

    Thank you so much – spent the last 2 days trying to fix this!

    Reply
  27. Sangeeta says:
    November 19, 2018 at 5:54 pm

    Thanks for this, after spending ages Googling, your fix saved the day.

    Reply
  28. Bar says:
    December 3, 2018 at 10:58 am

    Only worked for me when running it with extra quotes around the name parameter
    .\appcmd.exe set config -section:system.webServer/httpCompression “/-[name=’xpress’]”

    Reply
  29. Srdjan says:
    December 7, 2018 at 7:44 pm

    I Can’t thank you enough for this. I was on the verge to reinstall SCCM (WS 2016), but luckily i have found this.
    Thank you very much!!!!
    I was unable to install sccm client on devices, in SCCM console, clients showing as active but grayed out…
    I owe you one beer if you ever visit Serbia. 🙂

    Cheers,

    Reply
  30. Hamish says:
    January 27, 2019 at 9:08 pm

    Thank you very much

    Reply
  31. Kevin M (Seattle) says:
    April 2, 2019 at 8:07 pm

    I’m using SCCM 1810 with my WSUS on a Windows Server 2016 VM. This is what did the trick for me:
    cd C:\Windows\System32\inetsrv
    .\appcmd.exe set config -section:system.webServer/httpCompression “/-[name=’xpress’]”

    I had to ensure the single quotes were correct. Double check them if you are like me and copy and paste them.

    I sincerely appreciate everyone who posts these forms of solutions. I have been working on my WSUS issues for over three weeks now and this did the trick for me. Thanks everyone

    Reply
  32. Christian says:
    May 15, 2019 at 12:33 pm

    Another thank you from me. I had removed the SUP and WSUS role, and then started getting Management Point and Multicast Service Point errors. The fix above worked perfectly. SCCM 1810 on Server 2012 R2.

    Reply
  33. Raf says:
    June 5, 2019 at 6:35 pm

    omg you saved me! Thank you!

    Reply
  34. Arun Kumar says:
    January 13, 2020 at 5:19 pm

    Hi,

    I am getting error same like as image shown at above.
    Please help to us.

    Reply
  35. Ram says:
    January 21, 2020 at 4:46 pm

    Thank you so much !! You saved the my time and Work.
    This worked like charm
    Cmd > Run as admin
    and executed the script you mentioned resolved my issue

    Reply
  36. Dani says:
    February 14, 2020 at 10:06 am

    Thanks a million.. Just work strait!!

    Reply
  37. NM says:
    July 9, 2020 at 5:36 pm

    Thanks a lot. Your article helped me in fixing the issue.

    Reply
  38. Berrel says:
    September 14, 2020 at 11:39 am

    Unbelievable it’s still not fixed. This is a broken uninstaller. MS should fix it…
    And IIS should produce a more helpful error description.

    Reply
  39. Anibal Guzman says:
    November 8, 2021 at 3:34 pm

    thanks this helped me today, I migrate the wsus role to another server, the original is still holding the management point role and freaked out when I saw that 500 internal error, running this command fixed it. Thanks

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
All code is provided "AS-IS" with no warranties.

Tweets by ccmexec

Recent Posts

  • Windows Servicing, Personal Teams and Success.cmd
  • Windows MDM Security Baseline – Settings Catalog
  • Configuring MS Edge Security Baseline v107 using Settings Catalog
  • Configuring Desktop App Installer using CSP and script?!
  • Customizing Taskbar and Start in Windows 11 22h2 with PowerShell

©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT