Issue Description

1. User feedback that the Windows failed to boot and stuck on "PNP Detected Fatal Error" and "Choose your keyboad layout".

2. The Windows system also failed to boot into Safe Mode OR Last Known good configurations.

Error/Warning Information

Handling Process

1. Verify whether it is urgent, if it is urgent, just deploy a new from the same resource on VDC and mount the private disk.

2. Realize the user does not have private disk configured for the VMs.

3. One of the affected VM is newly created and does not have any private data, so deployed a new virtual machine and assigned the user to the new VM and locked the abnormal VM.

4. For the other VM, user concerned on the appdata informations that stored in the abnormal VM and not willing to create a new VM for this user.

5. Explain to user and understand whether it is urgent and whether can accept the time required for troubleshoot and recovery.

6. Mount WinPE into the affected VM.

7. Run "NTBOOTautofix.exe" to regenerate boot configs, problem remain.

8. Launch "DISM++" to check for recent updates, no recently intalled programs or windows updates were found.

9. Run "chkdsk D: /F /X" from WinPE and able to boot the Windows normally.

10. Tried reboot again, able to boot without issues.

Root Cause

There are numerous reasons why Windows files or system files can become corrupted, some of the most common are:

1. Sudden power outage
2. Complete system crash
3. Updating errors

Solution

1. Boot into WinPE and perform chkdsk to check and fix corrupted system files.
   Example: chkdsk d: /f /x

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk?tabs=event-viewer

Suggestions

1. In care of urgency, suggest to deploy new VM for the user to work while you can troubleshoot on the affected VM later.

2. In cases where the VM does not have private disk and user wants to retrieve some files from the abnormal VM, you can mount the system disk of the abnormal VM as a Disk 2 for the new VM for retrieving files.