0

I've got a Windows Server 2016 installation that went haywire and doesn't boot properly. It's a VM, so I can access the files fairly easily (as well as change the virtual hardware parameters) but that doesn't make fixing the issue any easier. At the time of writing the machnie starts... sort of. It gets stuck on the "loading" indicator of spinning circles on the blue background. There's no text (before this happens the system shows messages related to GPO updates and briefly shows a message related to the user profile service). In this state I cannot access the desktop nor access the service via RDP but some services appear to be running in the background (like file share or print server).

It all started yesterday when the server was acting unstable and I decided to give it a quick reboot (normal shutdown) at which point it entered the "CHKDSK needs to check file integrity" followed by immediately cancelling the process (without any input) and hanging on that screen. At that point I figured some kind of corruption must have taken place so I took the machine offline, mounted the VHDX and proceeded to do some preliminary fixes.

  1. I ran CHKDSK - this found and fixed NTFS-level issues
  2. I ran DISM on the mounted volume (failed with no sources; I eventually found the required sources in another Windows Server 2016 installation's WinSxS folder; see this question) - this found and corrected issues
  3. I ran SFC against the target volume - no issues detected

After all the above steps I am in the "spinning circles of death" scenario described above. I've tried to enter safe mode as well (reboot a few times to trigger recovery, set safe mode from there) but the result was the same - even in console-only safe mode I got the endless spinning circle (and no console).

The server has a number of services that I need - I CAN reinstall them; it's not impossible... but even if I were to migrate this to another server I'd would be much easier to have a working server to copy from rather than just the existing virtual disks and files. I've even tried contacting MS but they were of little help since Server 2016 support ended this year (extended support is still technically available and I do have a support plan so I'm still unsure why they didn't help).

Does anyone have any clue what I could do to fix the server? Or at least bring it to a complete boot + desktop (I could try an in-place upgrade from there to sort of reinstall the OS whilst keeping the services)?

MBender
  • 381
  • 2
  • 8
  • 25

1 Answers1

1

If the server is semi-booted, but can't load, try accessing the server remote service/task and check the state.

Often with the spinning wheel of death I fix it by running services.msc from another server, and I connect to the faulty server. My first service target is often Windows Installer and Windows Update, they are often the culprit.

If it's them the culprit you will find a enormous cbs.log's file inside the system's folder too, if you navigate on the server c$. It's sign of a install that loop indefinitely.

If it's not them the culprit, try from another server;

tasklist /s serverinproblem /u admin /p password

and then

taskkill /s serverinproblem /u admin /p password /im process

or

taskkill /s serverinproblem /u admin /p password /pid processPID
yagmoth555
  • 16,758
  • 4
  • 29
  • 50
  • 1
    The first idea (run services.msc and connect to the server) yielded SOME results - namely a list of running services, among which Windows Update was running (I couldn't get it to stop, however). `tasklist` failed with the error "The remote system must be rnning Windows 2000 or above"... which doesn't make sense. I'll try setting the Windows Update Service startup to "Disabled" and see if that helps... – MBender Jul 27 '22 at 14:54
  • Alas... With Windows Update service disabled the system still gets stuck on the spinning circle of death. And with `taskkill` not yielding any results I'm not sure what else I can try. – MBender Jul 27 '22 at 16:18
  • @Shaamaan Could psexec work ? – yagmoth555 Jul 27 '22 at 17:40
  • But... what would I be looking to do with psexec, exactly? – MBender Jul 27 '22 at 17:46
  • @Shaamaan Run a remote taskmgr with it, as the goal is to see what is blocking. Did you stopped the Windows Installer service too when you did the Windows update's one ? – yagmoth555 Jul 27 '22 at 17:48
  • The Windows Installer service wasn't running when I disabled the Update Service. As for PSExec... I think the server is on it's last legs because the trust to the DC has been broken and PSexec isn't executing commands. – MBender Jul 27 '22 at 18:08
  • @Shaamaan well, sadly unless you have a snapshot, it would be maybe quicker to restart a server :| Make sure to have a full backup next time. – yagmoth555 Jul 27 '22 at 18:12