updates

Author: v-lianna

support/windows-server/toc.yml

@@ -2836,6 +2836,8 @@ items:
     items:
     - name: Get-VMNetworkAdapter command doesn't report IP addresses
       href: ./virtualization/get-vmnetworkadapter-doesnt-report-ip-addresses.md
+    - name: Troubleshoot Hyper-V virtual machine start, state, and access failures
+      href: ./virtualization/hyper-v-start-state-access-failures-clustered-standalone.md
     - name: Virtual Machines enter the paused state
       href: ./virtualization/virtual-machines-enter-paused-state-low-disk-free.md
     - name: Virtual machine shutdown actions don't run

support/windows-server/virtualization/hyper-v-start-state-access-failures-clustered-standalone.md

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting Hyper-V virtual machine start, state, and access failures in clustered and standalone environments
+title: Troubleshoot Hyper-V Virtual Machine Start, State, and Access Failures
 description: Provides a detailed troubleshooting guide to help you resolve issues related to Hyper-V virtual machines (VMs) that fail to start, become stuck in transitional states, or become inaccessible in both clustered and standalone environments.
 ms.date: 08/22/2025
 manager: dcscontentpm
@@ -10,159 +10,189 @@ ms.custom:
 - sap:virtualization and hyper-v\virtual machine state
 - pcy:WinComm Storage High Avail
 ---
-# Troubleshooting Hyper-V virtual machine start, state, and access failures in clustered and standalone environments
+# Troubleshoot Hyper-V virtual machine start, state, and access failures in clustered and standalone environments
 
 This article provides a detailed troubleshooting guide to help you resolve issues related to Hyper-V virtual machines (VMs) that fail to start, become stuck in transitional states (such as starting, stopping, saved, or paused), or become inaccessible in both clustered and standalone environments. Common causes include VM configuration file corruption, storage or network problems, process lockups, checkpoint or AVHDX (automatic virtual hard disk) issues, and permission or driver errors. Timely identification and resolution of these problems are essential to minimize VM downtime, prevent business disruption, and avoid data loss in production environments.
 
-## Symptoms
+You might encounter various symptoms when dealing with Hyper-V VM issues, including the following items:
 
-You may encounter various symptoms when dealing with Hyper-V VM issues, including the following:
-
-### End-user and technical symptoms
+## End-user and technical symptoms
 
 - VMs fail to start or power on in Hyper-V Manager or Failover Cluster Manager.
 - VMs are stuck in states like "starting," "stopping," "saved-critical," "paused," or "restoring."
-- VMs are missing or not visible in Hyper-V Manager or the output of Get-VM.
+- VMs are missing or not visible in Hyper-V Manager or the output of `Get-VM`.
 - VM states are displayed as "running critical," "stopping," or "online pending."
 - VM consoles are inaccessible, and remote desktop connections are unavailable.
 - VMs fail to migrate successfully between cluster nodes.
-- Hyper-V Manager or Failover Cluster Manager cannot change VM states or report their status.
-- VMMS (virtual machine management service) or VMM services are stuck in a "Stopping" state.
+- Hyper-V Manager or Failover Cluster Manager can't change VM states or report their status.
+- Virtual machine management service (VMMS) or VMM services are stuck in a "Stopping" state.
 - Storage volumes, such as Cluster Shared Volumes (CSVs), appear as RAW or offline, and VHDX files are inaccessible or locked.
 
-### Error messages, event logs, and codes
+## Error messages, event logs, and codes
+
+- Error messages:
+
+  - > A virtual machine or container with the specified identifier already exists in Hyper-V.
+  - > Failed to start worker process: Catastrophic failure 0x8000FFFF.
+  - > Virtual machine failed to generate VHD tree: The system cannot find the file specified (0x80070002).
+  - > The process cannot access the file because it is being used by another process.
+  - > Failed to perform the Cleaning up stale reference point(s) operation. The virtual machine is currently performing: Turning Off.
+  - > The file or directory is corrupted and unreadable. (0x80070570)
 
-- “A virtual machine or container with the specified identifier already exists in Hyper-V.”
-- “Failed to start worker process: Catastrophic failure 0x8000FFFF.”
-- “Virtual machine failed to generate VHD tree: The system cannot find the file specified (0x80070002).”
-- “The process cannot access the file because it is being used by another process.”
-- “Failed to perform the Cleaning up stale reference point(s) operation. The virtual machine is currently performing: Turning Off.”
-- “The file or directory is corrupted and unreadable. (0x80070570)”
 - Event IDs: 21502, 1069, 1205, 5120, 1135, 225, 15500, 1793, 1795, 7034, 7031, 7036, 16300, 14102, 4092, 18012, 18016, 20848, 20864, 12620, 12240, 153, 20848, 18524, 1146, 1230.
 - Cluster resources stuck in "online pending" or "failed" states.
 - VMs are unavailable after patching, host restarts, or storage and network events.
 
-## Cause
+Hyper-V VM failures might originate from several root causes categorized as follows, and corresponding resolutions are provided respectively:
 
-Hyper-V VM failures may originate from several root causes categorized as follows:
+- [Cause 1: Configuration and metadata corruption](#cause-1-configuration-and-metadata-corruption)
+- [Cause 2: Storage and file system issues](#cause-2-storage-and-file-system-issues)
+- [Cause 3: Process and service lockups](#cause-3-process-and-service-lockups)
+- [Cause 4: Permissions, security, and driver problems](#cause-4-permissions-security-and-driver-problems)
+- [Cause 5: Cluster, network, and failover issues](#cause-5-cluster-network-and-failover-issues)
 
-### 1. Configuration and metadata corruption
+> [!NOTE]
+> To resolve these issues, perform the initial checks using the following steps:
+>
+> 1. Identify error messages, event IDs, and affected VMs using Hyper-V Manager, Failover Cluster Manager, or PowerShell.
+> 2. Review system logs, Hyper-V logs, and cluster event logs for relevant entries.
 
-- Corrupt or missing VM configuration files (e.g., .VMCX, .XML) prevent the VM from being recognized or started by Hyper-V, often after failed migrations, storage issues, or abrupt shutdowns.
+## Cause 1: Configuration and metadata corruption
+
+- Corrupt or missing VM configuration files (for example, `.VMCX`, `.XML`) prevent the VM from being recognized or started by Hyper-V, often after failed migrations, storage issues, or abrupt shutdowns.
 - Checkpoint (AVHDX) chain corruption or missing differencing disks prevent the VM from starting.
 - Orphaned checkpoints, incomplete merges, or invalid entries in configuration files block VM operations.
 - Duplicate VM GUIDs or object entries, particularly with System Center Virtual Machine Manager (SCVMM), can cause "already exists" errors and prevent VM imports or starts.
 
-### 2. Storage and file system issues
+## Cause 2: Storage and file system issues
 
 - CSVs or volumes are offline, RAW, or inaccessible due to storage subsystem failures, disk corruption, or drive letter conflicts.
 - VHD or VHDX files are locked or in use by another process, such as a backup or antivirus program.
 - Missing or corrupted VM runtime state files (VMRS) impede VM operations.
 - BitLocker-locked disks prevent VMs from starting after patching or reboots.
 
-### 3. Process and service lockups
-
-- Stale VMWP (VM Worker Process) or VMMS (VM Management Service) processes are stuck due to storage or network issues or deadlocks.
-- Failed attempts to terminate VM processes via Task Manager, taskkill, or Process Explorer persist due to kernel or resource locks.
-
-### 4. Permissions, security, and driver problems
-
-- Permissions issues restrict the Hyper-V service account from accessing VM files or folders.
-- Antivirus or third-party filter drivers interfere with Hyper-V, blocking file access or causing merge failures.
-- Outdated or misconfigured storage or network drivers lead to connectivity loss or failover events.
-
-### 5. Cluster, network, and failover issues
-
-- CSV or network communication failures, such as cluster node isolation, result in mass VM failovers or reboots.
-- Improper cluster configurations or inconsistent patching across nodes cause instability.
-- Live migration or failover failures occur due to insufficient memory, incompatible settings, or node misconfigurations.
-
-## Resolution
-
-To resolve these issues, follow the troubleshooting steps below:
-
-### A. Initial checks
-
-1. Identify error messages, event IDs, and affected VMs using Hyper-V Manager, Failover Cluster Manager, or PowerShell.
-2. Review system logs, Hyper-V logs, and cluster event logs for relevant entries.
-
-### B. File system and storage checks
+### Resolution: File system and storage checks
 
 1. Verify storage volumes:
 
-    - Use Disk Management or diskpart to ensure volumes are online and properly assigned.
-    - If volumes are RAW or missing, reassign drive letters and repair disk corruption using chkdsk:
+    - Use Disk Management or `diskpart` to ensure volumes are online and properly assigned.
+    - If volumes are RAW or missing, reassign drive letters and repair disk corruption using `chkdsk`:
+
+      ```console
+      chkdsk <drive_letter>: /f /r</drive_letter>
+      ```
 
-        chkdsk <drive_letter>: /f /r</drive_letter>
 2. Check VM configuration and disk file presence:
 
-    - Confirm the existence of .VMCX, .VMRS, .VHDX, and .AVHDX files in the VM folder.
+    - Confirm the existence of `.VMCX`, `.VMRS`, `.VHDX`, and `.AVHDX` files in the VM folder.
     - For missing or corrupt configuration files, rebuild the VM using existing VHDX files or restore from a backup.
     - For missing or corrupt AVHDX files:
 
-        Set-VHD -Path <vhdx path> -ParentPath <parent vhdx path> -IgnoreIDMismatch</parent></vhdx>
+      ```powershell
+      Set-VHD -Path <vhdx path> -ParentPath <parent vhdx path> -IgnoreIDMismatch</parent></vhdx>
+      ```
+
     - If BitLocker is enabled, unlock the disk:
 
-        manage-bde -unlock D: -RecoveryPassword <yourrecoverypassword></yourrecoverypassword>
+      ```console
+      manage-bde -unlock D: -RecoveryPassword <yourrecoverypassword></yourrecoverypassword>
+      ```
+
     - For locked or in-use files, use Process Explorer to identify and terminate the locking process, or reboot the host to release the lock.
 
-### C. Process and service recovery
+## Cause 3: Process and service lockups
+
+- Stale VM Worker Process (VMWP) or VMMS processes are stuck due to storage or network issues or deadlocks.
+- Failed attempts to terminate VM processes via Task Manager, taskkill, or Process Explorer persist due to kernel or resource locks.
+
+### Resolution: Process and service recovery
 
 1. If the VM is stuck in transitional states:
 
     - End the VM process:
 
-        taskkill /PID <pid> /F</pid>
+      ```console
+      taskkill /PID <pid> /F</pid>
+      ```
+
     - Restart VMMS or the host if processes remain stuck.
 2. Remove saved states or checkpoints:
 
-    Get-VMSnapshot <vmname> | Remove-VMSavedState<br>Remove-VMSavedState <vmname></vmname></vmname>
+   ```powershell
+   Get-VMSnapshot <vmname> | Remove-VMSavedState<br>Remove-VMSavedState <vmname></vmname></vmname>
+   ```
+
+## Cause 4: Permissions, security, and driver problems
+
+- Permissions issues restrict the Hyper-V service account from accessing VM files or folders.
+- Antivirus or third-party filter drivers interfere with Hyper-V, blocking file access or causing merge failures.
+- Outdated or misconfigured storage or network drivers lead to connectivity loss or failover events.
 
-### D. Permission and security configuration
+### Resolution: Permission and security configuration
 
 1. Ensure the Hyper-V service account has full control over VM files and folders.
-2. Apply antivirus exclusions as per Microsoft’s Hyper-V documentation.
+2. Apply antivirus exclusions as per Microsoft's Hyper-V documentation.
 3. Identify and unload problematic filter drivers:
 
-    fltmc
-fltmc unload <drivername></drivername>
+   ```console
+   fltmc
+   fltmc unload <drivername></drivername>
+   ```
 
-### E. Cluster and network remediation
+## Cause 5: Cluster, network, and failover issues
+
+- CSV or network communication failures, such as cluster node isolation, result in mass VM failovers or reboots.
+- Improper cluster configurations or inconsistent patching across nodes cause instability.
+- Live migration or failover failures occur due to insufficient memory, incompatible settings, or node misconfigurations.
+
+### Resolution: Cluster and network remediation
 
 1. Validate cluster health and configuration using the cluster validation wizard or:
 
-    Test-Cluster
-2. Resolve network issues by reviewing Event IDs (e.g., 5120, 1135) and adjusting parameters:
+   ```powershell
+   Test-Cluster
+   ```
+
+2. Resolve network issues by reviewing Event IDs (for example, 5120, 1135) and adjusting parameters:
+
+   ```powershell
+   (Get-Cluster).SameSubnetThreshold = <value></value>
+   ```
 
-    (Get-Cluster).SameSubnetThreshold = <value></value>
 3. Ensure consistent patching and proper network/storage configurations across nodes.
 
-### F. VM configuration repairs and rebuilds
+### Resolution: VM configuration repairs and rebuilds
 
-1. For corrupt configuration files, edit the .VMCX file or create a new VM with existing disks.
+1. For corrupt configuration files, edit the `.VMCX` file or create a new VM with existing disks.
 2. Address saved state or checkpoint issues by removing invalid checkpoints or reattaching disks.
 
-### G. Escalation and bug reference
+## Escalation and bug reference
 
-1. If known bugs or product defects are involved (e.g., UEFI firmware bugs or cluster communication issues), review vendor advisories and apply recommended updates or fixes.
+If known bugs or product defects are involved (for example, UEFI firmware bugs or cluster communication issues), review vendor advisories and apply recommended updates or fixes.
 
 ## Data collection
 
 Gather the following logs and diagnostics to assist with troubleshooting:
 
 - Hyper-V event logs:
 
-    Get-WinEvent -LogName Microsoft-Windows-Hyper-V-VMMS-Admin | Export-Csv -Path <unc path></unc>
+  ```powershell
+  Get-WinEvent -LogName Microsoft-Windows-Hyper-V-VMMS-Admin | Export-Csv -Path <unc path></unc>
+  ```
+
 - Cluster logs:
 
-    Get-ClusterLog -UseLocalTime -Destination <folder></folder>
+  ```powershell
+  Get-ClusterLog -UseLocalTime -Destination <folder></folder>
+  ```
+
 - Process dumps for stuck services:
 
-    procdump -ma <pid> <output_path></output_path></pid>
+  ```console
+  procdump -ma <pid> <output_path></output_path></pid>
+  ```
 
 ## References
 
-For additional details, consult the following resources:
-
-- [Hyper-V performance tuning guide](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v)
-- [Failover cluster troubleshooting](https://learn.microsoft.com/en-us/windows-server/failover-clustering)
+- [Hyper-V performance tuning guide](/windows-server/virtualization/hyper-v)
+- [Failover cluster troubleshooting](/windows-server/failover-clustering)