Can't do anything with the MMC after the internal database has stopped chugging along for 7-10 minutes now.
WID-SQL server eventually finishes whatever it was doing, and Task Manager drops to about 0-5% system load.ħ. 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.Ħ. Windows task manager suddenly shows 50% CPU usage across the two vCPU's (really, just 100% load for 1 CPU).ĥ. It says at bottom "Loading synchronization history, 0% complete"Ĥ. WSUS for Windows Server 2019 appears to be broken as designed.ġ. 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. 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. Nothing has been approved, no computers are joined. It is a fully default WSUS install using the Windows Internal Database SQL server, and the default language and product options.
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.
0 kommentar(er)
