WSUS on Server 2016 vs WSUS on Server 2008 R2 RRS feed

  • Question

  • Hello All

    I have an interesting setup.

    I installed Server2016 from scratch (on a Hyper-V VM), and added the WSUS with WID role. The WSUS MMC kept on bombing out, after a bit of forward and backwards I found that I had to increase the private memory pool for WSUS in IIS. This was duly done, but WSUS MMC still kept on bombing out.

    The next thing I did was to download SQL Server 2012 Express.

    I deleted the whole WSUS setup including the database and downloaded files.

    Then I installed SQL Express, and reinstalled WSUS using SQL Express as the DB server.

    It worked beautifully. But this is not ideal due to the size limitation in SQL Express.

    This caused me to delete the Server 2016 WSUS VM, and replace it with a Server2008 R2 VM, also with the WSUS and WID role. (Windows Integrated Database)

    And the WSUS MMC is working properly, no crashes at all.

    Am I right to believe that the WID on Server2016 may have an internal issue and cause problems with WSUS, since it seems to be pointing to just that. I may be wrong though.



    Tuesday, October 2, 2018 11:00 AM

All replies

  • Don't use SQL Express - See the appropriate title in my blog post here:


    WID is much better for WSUS.

    I would say that the INSTANCE of the initial database for WSUS (SUSDB) may have had an issue on your original install of WSUS. You should be able to reinstall it using the WID and it should be fine.

    You would want to use my guide on a complete removal and reinstall if you choose to go that route.


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

    Tuesday, October 2, 2018 7:56 PM
  • Hi,

    Adam give a good idea for this issue. You may try to use the following resolution for WSUS crashing:

    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.
    Wednesday, October 3, 2018 2:54 AM