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.
Regards
Emil
