Windows10 Hyper-v The server encountered an error while creating New Virtual Machine. Failed to access configuration store 0x80070003

Gokhan Varol 21 Reputation points
2020-09-10T23:12:09.3+00:00

This started happening few days ago probably after a windows update. I tried uninstalling HyperV component restart, readd restart etc no luck. My existing hyperv virtual machines fail with the same error, to create a new one also fails.

Please advise, Thank you.

The server encountered an error while creating New Virtual Machine.

Failed to create a new virtual machine

New Virtual Machine failed to realize

Failed to access configuration store 0x80070003

23912-hyperverror.jpg23962-windows10version.jpg

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
1,831 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaowei He 9,746 Reputation points
    2020-09-11T06:12:22.673+00:00

    Hi,

    1. What is the update do you install before the issue occurs, will it work if we uninstall the update and reinstall the Hyper V role?
    2. If you have another working Hyper V host, please check if the files located in C:\ProgramData\Microsoft\Windows\Hyper-V is entire. If not, please try to restore the files from a working Hyper V host. Thanks for your time!
      Best Regards,
      Anne

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Gokhan Varol 21 Reputation points
    2020-09-11T13:34:39.787+00:00

    I don't like messing with auto updates, if they are breaking portions of Windows I'd prefer Microsoft knowing about it and fixing it.

  3. Paul 1 Reputation point
    2020-12-26T16:11:14.33+00:00

    I've had the same issue, and somehow solved it by deleting the directory "C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines"
    There were no files in there; after deleting it, I didn't get the error anymore...

  4. Dallas Burbridge 1 Reputation point
    2022-07-15T20:48:23.65+00:00

    You probably changed the drive letter like I did.

    On the Specify Name and Location Page
    It appears to cache the first drive letter used and you will have to change it every single time for the new vm's you make.

    221295-image.png

    Connect Virtual Hard Disk Page

    This one also has a persistent drive letter

    221252-image.png