I have a brand new Windows 2019 running a basic WSUS install in a virtual machine with two Xeon 3.5 ghz vCPUs, 8 gig of memory.
It is a fully default WSUS install using the Windows Internal Database SQL server, and the default language and product options. I ran the synchronization. Nothing has been approved, no computers are joined. Everything is working normally.
I am unable to view the synchronization status because the Windows Internal Database SQL engine is taking too long to respond to the MMC snap-in.
How can the snap-in timeout be increased? I have thoroughly searched C:\Program Files\Update Services and I can not find any MMC configuration files where there is a timeout option that can be adjusted.
WSUS for Windows Server 2019 appears to be broken as designed.
,
Steps to reproduce:
1. Open WSUS MMC management snap-in. Open Task Manager, says 0-5% CPU load.
2. Click on Synchronizations in WSUS MMC.
3. It says at bottom "Loading synchronization history, 0% complete"
4. Windows task manager suddenly shows 50% CPU usage across the two vCPU's (really, just 100% load for 1 CPU).
5. After about 5 minutes pass, the MMC snap-in is unhappy and claims it can't reach WSUS. Task manager continues to show 50% CPU usage across the two vCPU's for several more minutes by SQLServr.exe.
6. WID-SQL server eventually finishes whatever it was doing, and Task Manager drops to about 0-5% system load.
7. Can't do anything with the MMC after the internal database has stopped chugging along for 7-10 minutes now. The only option available is to "Reset Server Node," which discards anything that has been retrieved so far.
8. Go back to Step 2 and do this all over again several more times. No change.
9. Stop VM, increase memory from 8 gb to 16 gb, start VM. This memory increase has no effect. The WSUS MMC still times out trying to load the synchronization history.
,
Is there any way to increase the Server 2019 WSUS MMC snap-in timeout, or am I being indirectly forced by Microsoft to buy a full license for Microsoft SQL Server, because the Windows internal database is too slow and low performance, to respond to the MMC
snap-in within 5 minutes?