When time permits you might try booting, then F8 at startup and try Safe Mode and or Safe Mode with Networking to see if you can get further.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have 2 windows server 2019 std VM's running in VMware that after a reboot will not finish loading. I am stuck a black screen with white spinning dots.
I can connect to both servers via powershell and run commands. I can manage both via server manager from another server. In both cases services are running including MSSQL 2016. The SQL instance is functional.
However I cannot RDP or console into either server. Both are stuck at the white spinning dots. One has been at like this for over a week.
When time permits you might try booting, then F8 at startup and try Safe Mode and or Safe Mode with Networking to see if you can get further.
Maybe this one?
https://kb.vmware.com/s/article/2034627
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This is 100% the issue
https://eicee13.wordpress.com/2020/04/10/black-screen-when-booting-up-windows-server-2019/
As mentioned I created a GPO that modified the “Bypass Traverse Checking” setting.
I moved the server out of the OU that the GPO was assigned to and after 2 reboots the server came up.
I will do some more testing but I think this is it.
Troubleshooting:
Attempt to boot into Safe Mode: Black Screen. Doesnt ping. of course cant connect via remote powershell
Attempt to boot in Safe mode w/ networking: Black Screen. Doesnt ping. of course cant connect via remote powershell
Attempt to boot into Safe Mode w/ command prompt: Black Screen. Doesnt ping. of course cant connect via remote powershell
I've also tried: Via remote powershell:
DISM /Online /Cleanup-Image /RestoreHealth
SFC /scannow
Dism /Online /Cleanup-Image /revertpendingactions
None worked.
I am now looking into an article that mentions certain Group Policy setting "Bypass Traverse Checking" to be exact. I did create a GPO that changes this value. I changed this value as part of a configuration that was needed for a MSSQL 2016 ssis deploy package
https://eicee13.wordpress.com/2020/04/10/black-screen-when-booting-up-windows-server-2019/
I'll see what this article has to say and report back
Hello
Thank you for your question and reaching out. I can understand you are having issues related to accessing VM console.
It can be due to Windows update stuck and displaying black or blank screen.
remotely execute command (with WMIC /node:machinename process call create “<commandline here>” ,-keep the quotes-) on the box:
sc queryex wuauserv
Once you had the PID (Process ID) I could then kill the task with the following:
taskkill /PID [process ID] /F
Then you can proceed with executing this "rollback" command line from the server to stop bootloop if any:
Dism /Image:C:\ /Cleanup-Image /revertpendingactions
There are several of other options to try to resolve the root issue here:
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-update-says-updating-your-system100-for/4f262021-f06b-49ca-9b25-4f901c3f11eb?auth=1
--If the reply is helpful, please Upvote and Accept as answer--