Hyper-V generation 2 failed to realised with error 0xC03A0014

Ho Yeung, Lee 1 Reputation point
2025-04-20T03:24:32.8766667+00:00

after install data centre and then hardening group policy,

Hyper-V generation 2 failed to realised with error 0xC03A0014

failed to access configuration store

virtual disk support provider for specified file was not found

another things is network adapter folder empty

then I change device guard policy back to not configured and gpupdate /force

same error.

and network adapter folder empty no adapter

Latitude 7650 - windows server 2025 data center OEI

UTF-81000005479

UTF-81000005477

Windows Server 2022
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Henry Mai 0 Reputation points
    2025-04-29T01:37:06.3233333+00:00

    Hello Ho Yeung, Lee, I am Henry and I'd like to help.

    The error 0xC03A0014 in Hyper-V Generation 2 VMs, indicating a failure to access the configuration store and a missing virtual disk support provider. Here are some steps to troubleshoot and resolve the issue:

    1. Verify Virtual Disk Path

    The error suggests that the VHD support was not found in the image, indicating a possible issue with the virtual disk's configuration or compatibility.

    • Ensure the virtual disk file (VHD or VHDX) is in the correct location and accessible.
    • If the file was moved or renamed, update the VM configuration to point to the correct path.

    2. Check Virtual Disk Format

    Confirm that the virtual disk is in the correct format (VHDX for Generation 2 VMs).

    If the disk is corrupted, consider recreating it or restoring from a backup.

    3. Reset Group Policy Changes

    • Since the issue occurred after hardening group policy, revert any recent changes that might restrict Hyper-V functionality.
    • Use the command gpupdate /force after reverting policies to ensure they are applied.

    4. Device Guard and Credential Guard

    • If Device Guard or Credential Guard is enabled, it might interfere with Hyper-V. Disable these features temporarily to test:
    • Open Group Policy Editor.
      • Navigate to Computer Configuration > Administrative Templates > System > Device Guard.
      • Set policies to "Not Configured" and run gpupdate /force.

    5. Network Adapter Issue

    • The empty network adapter folder suggests a possible misconfiguration or driver issue:
    • Check if the network adapter is correctly added to the VM in Hyper-V Manager.
    • Ensure the host machine's network drivers are up to date.
    • If necessary, remove and re-add the network adapter in the VM settings.

    6. Reinstall Hyper-V Components

    • If the issue persists, consider reinstalling Hyper-V on the host machine:
    • Open Windows Features and uncheck Hyper-V.
    • Restart the system, then re-enable Hyper-V.

    7. Check Configuration Store Permissions

    • Verify that the Hyper-V configuration store folder has the correct permissions:
    • Navigate to C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines.
    • Ensure the Hyper-V service account has full access to this folder.

    If you receive any error message during the procedure above, please attach a screenshot of the error message to help to identify what is causing the problem

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.