Free tools Windows power users keep installed
One-click scans. No signup required.
The Hyper-V message “The server encountered an error while creating New Virtual Machine” is a generic wrapper, not a diagnosis. Open the full dialog and identify its expanded error code. 0x80070003 usually means Hyper-V cannot find a configured path; 0x80070569 points to a denied logon type; 0x80070522 indicates a missing privilege; and remote creation can fail with 0x80070005 when an SMB or SOFS configuration store rejects access. The reliable fix is to follow the branch that matches the complete code and whether the VM is being created locally or remotely.
What the Hyper-V error actually means
Hyper-V Manager often displays only the headline when the New Virtual Machine wizard fails. The same headline can be produced by a missing ISO, a changed drive letter, an inaccessible virtual-machine folder, a remote-share permission problem, a Windows user-rights policy, or a host that has too little free memory or storage. Treat the headline as a starting point rather than as evidence of one specific fault.
As an Amazon Associate I earn from qualifying purchases.
A Microsoft Q&A case posted on September 10, 2020 shows the pattern: the visible message was “The server encountered an error while creating New Virtual Machine,” while the expanded detail was “Failed to access configuration store 0x80070003.” That code changes the investigation to file and folder paths. Other cases with the same headline show entirely different causes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems| Expanded code | Meaning or signal | Primary investigation |
|---|---|---|
| 0x80070003 | “The system cannot find the path specified.” | Verify the VM configuration path, virtual-disk path, ISO path, drive letters, and Hyper-V folders. |
| 0x80070569 | “The user has not been granted the requested logon type at this computer.” | Inspect local policy and rights assigned to the relevant service or virtual-machine account. |
| 0x80070522 | “A required privilege is not held by the client.” | Investigate privilege assignment, policy changes, and security controls instead of changing paths repeatedly. |
| 0x80070005 | General access denied, reported during remote external configuration-store creation. | Check the SMB/SOFS share permissions and test from the Hyper-V host. |
Record the complete failure before changing anything
Do not retry blindly or delete VM folders while the error is still ambiguous. Capture the VM name, the exact wording, the hexadecimal code, and whether the wizard was run on the Hyper-V host or from another computer. If the dialog has a details, expand, or copy option, save that text. The expanded sentence determines which subsystem is failing.
#1 Best Overall
- WIRED NETWORK USB PRINT SERVER: Connect a single USB 2.0 printer to a wired Ethernet LAN (RJ45); 10Base-T, 100Base-TX auto-sensing to ensure a reliable connection, letting you print from any network computer, across the office or over the Internet
- MANUAL NETWORK SETUP REQUIRED: Configuration via web interface (static IP or DHCP) using LPR queue “LP1"; Not plug-and-play, requires intermediate network knowledge for installation; Access our online FAQs for additional helpful tips and instructions
- USB PRINTER COMPATIBILITY: Works with most USB 2.0 printers using standard drivers; Not compatible with USB hubs, multi-function printers with proprietary drivers, or printers requiring full bi-directional communication
- COMPATIBILITY: The USB to Ethernet print server is USB 2.0 compliant and works with macOS and Windows; It also supports LPR network printing and Bonjour Print Services for broad compatibility; Included software is compatible with Windows only
- PRINT FROM ANYWHERE: Print from any computer connected to the Ethernet; This print server doesn’t require a wired connection to a computer, however it must be connected to your networking device (eg. router or switch) with the included RJ45 network cable
- Run the New Virtual Machine wizard until it fails.
- Copy the full dialog, including the code and any reference to a configuration store, ISO, disk, or access denial.
- Note the storage locations selected in the wizard and whether they are local volumes, mapped drives, SMB shares, or SOFS paths.
- Open the Hyper-V-VMMS-Admin event log and record events at the same time as the failure. Remote failures may include a more useful event identifier, such as Event ID 13000.
The VM name itself is rarely the root cause. A name collision can matter, but the documented branches for this message are identified more reliably by the expanded code, the creation location, and the storage target.
Fix 0x80070003: verify every path Hyper-V must open
0x80070003 expands to “The system cannot find the path specified.” Hyper-V may be looking for more than one item: the VM configuration folder, the virtual hard-disk destination, an installation ISO, or a parent folder that no longer exists. A single changed drive letter is enough to make the wizard fail.
Re-select the ISO instead of trusting the saved wizard value
An ISO can become stale after it has been moved, renamed, deleted, or made unavailable. In the wizard’s installation options, browse to the ISO again. For a VM that was already created, open its settings, select the DVD drive, choose the image-file option, and browse to the current ISO location. Confirm that the file is present on the machine that will actually perform the operation; a path visible on your workstation may not exist on the Hyper-V host.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Check the VM configuration and virtual-disk locations
Review the destination selected for the VM configuration and the destination selected for its virtual hard disk. Open those folders in File Explorer on the host and verify that the parent directories exist. Check for a drive letter that changed after a reboot, disk replacement, or storage reconfiguration. A path stored as D:VMs, for example, is invalid if the volume is now mounted under another letter.
Hyper-V’s default configuration area is C:ProgramDataMicrosoftWindowsHyper-VVirtual Machines. Confirm that this folder exists on the host and that the intended storage location is still configured. If the VM is being placed on another volume, verify that the volume is online and that the selected parent folder has not been renamed.
Rank #2
- [Win OS Install or reinstall] — Boot from the USB to install or reinstall Win 11, 10, or 7 Home & Pro editions. Includes OS installations and reinstallations media plus WinPE Utility Suite.
- [WinPE Repair & Recovery Tools] — Boot into the included WinPE utility suite to backup system and important files, troubleshoot startup problems, repair boot issues, recover data, recover Win User accounts password, and diagnose common PC problems.
- [All-in-One PC Rescue USB] — Combines Win 11, 10, and 7 installation media with PC repair, recovery, and diagnostic tools on one bootable 64GB USB drive, helping you troubleshoot and restore a computer without needing multiple discs or downloads.
- [Support] — Full instructions are included in packaging plus a printable copy of the instructions with troubleshooting information on the device. Also, a video “How to boot from a bootable USB drive.mp4” to help guide you through starting a PC from a USB drive. If you need help using the USB please contact us for assistance, we are here to help.
- [Video] - If you are new to booting from a USB drive or need a refresher see our video "How to boot from USB drive" both in description and on USB device.
Do not delete a folder merely because it looks empty
Removing and recreating a missing directory can solve a genuinely absent path, but deleting an existing Hyper-V folder can destroy configuration files or disconnect a virtual disk from a VM. Preserve any needed VM data first. If a previous VM with the same name exists, identify its configuration and disk files before deciding whether to reuse, move, or recreate anything.
Retry with a simple local destination
When several paths are uncertain, create a test VM using an existing local volume and a verified ISO. This isolates a path problem from a remote-storage or permissions problem. If the local test succeeds, the original destination—not the basic Hyper-V wizard—is the likely failing component.
When creation works locally but fails remotely
Remote administration adds another authorization boundary. A Microsoft-related case reported Event ID 13000 and an error stating that user “XXXXAdministrator” failed to create an external configuration store with a general access-denied error (0x80070005) on an SMB or SOFS path. In that situation, repeatedly changing the ISO or VM name will not repair the share access.
- Log on to, or otherwise administer from, the Hyper-V host and run the same creation using a local path.
- If local creation succeeds, test the remote destination separately. Confirm that the share is online, the path resolves from the host, and the account used by the operation has the required share and file-system permissions.
- Review the Hyper-V-VMMS-Admin log on the host for the failed timestamp and Event ID 13000 or related access errors.
- Check whether the configuration store is on SMB or SOFS and whether a security or group-policy change coincided with the failure.
Mapped drive letters are a common source of confusion in remote administration: a drive mapped in an interactive session may not be visible to the Hyper-V service or to a session running on the host. Use the host’s actual share path when validating the destination.
Permission and policy branches: 0x80070569 and 0x80070522
0x80070569: requested logon type was not granted
The text “Logon failure: the user has not been granted the requested logon type at this computer” indicates a user-rights assignment problem. A cited permissions case reports this code behind the same generic VM-creation headline. Inspect local security policy and domain group policy for changes affecting the account, service, or virtual-machine operation. Also check whether a security product or hardening baseline recently removed a required right.
Rank #3
- Comprehensive Solution: This Windows 10 reinstall DVD provides a complete solution for resolving various system issues, including crashes, malware infections, boot failures, and performance slowdowns. Repair, Recover, Restore, and Reinstall any version of Windows.
- USB will work on any type of computer (make or model). Creates a new copy of Windows! DOES NOT INCLUDE product key.
- Windows not starting up? NT Loader missing? Repair Windows Boot Manager (BOOTMGR), NTLDR, and so much more with this DVD. Clean Installation: Allows you to perform a fresh installation of Windows 11 64-bit, effectively wiping the system and starting from a clean slate.
- Step by Step instructions on how to fix Windows 10 issues. Whether it be broken, viruses, running slow, or corrupted our disc will serve you well
- Please remember that this DVD does not come with a KEY CODE. You will need to obtain a Windows Key Code in order to use the reinstall option
Record which identity is named in the detailed error. The interactive administrator who launches Hyper-V Manager is not necessarily the identity that must be allowed to access a service or remote configuration store. Correct the applicable policy through your organization’s normal change process, then retry and confirm that the same code is gone.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →0x80070522: a required privilege is missing
0x80070522 means “A required privilege is not held by the client.” This is not normally fixed by browsing to another ISO or creating another folder. Review privilege assignments, service rights, group-policy changes, and security software that may be blocking the operation. Compare a failing account with an account that is authorized to create VMs, but do not grant broad privileges permanently just to make a test pass.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check memory, disk space, and competing VMs
Resource pressure is another possible branch, although it is not a universal explanation. One community case attributed the generic failure to only 10 GB of RAM being available; the reporter succeeded after shutting down other VMs and creating a smaller test VM. That is a case-specific lead, not a published minimum requirement or a success rate.
- Check the host’s available memory while the wizard is running.
- Stop nonessential VMs temporarily and retry with a smaller startup-memory value.
- Check free space on the volume that will hold the configuration and virtual disk, not only on the system drive.
- Ensure that a growing virtual disk has room for its current and future allocation.
- Retry after resource pressure is removed, then restore the intended VM size once the storage and memory plan is confirmed.
If the same code remains after freeing resources, return to the expanded error. Memory pressure does not explain a clear “path not found” or “logon type not granted” message.
A decision path that avoids wasted retries
| What you observe | Next action | Why it matters |
|---|---|---|
| 0x80070003 or “path specified” | Re-browse to the ISO, verify VM and disk folders, check drive letters, and confirm the default Hyper-V folder. | The host cannot open one of the configured locations. |
| Local creation succeeds; remote or SMB/SOFS creation fails | Validate share reachability, share and NTFS permissions, and Hyper-V-VMMS-Admin events on the host. | The additional remote storage or authorization boundary is implicated. |
| 0x80070569 | Inspect logon-type rights and policy for the identity named in the details. | The account is being denied a required logon category. |
| 0x80070522 | Inspect required privileges, policy, and security software. | The client lacks a privilege; changing a path will not add it. |
| No clear code, low memory, or low disk space | Stop nonessential VMs, use a smaller test VM, and verify free space on the target volume. | Resource exhaustion can prevent configuration-store or disk creation. |
Prevent the error on the next VM
- Keep VM configuration, virtual disks, and installation media on documented paths whose drive letters do not change unexpectedly.
- Before starting a wizard, confirm that the ISO exists on the host or on a share the host can access.
- Use a consistent local test destination to distinguish Hyper-V problems from share permissions.
- Record the expanded code and event-log entries whenever a creation fails; this prevents different causes from being treated as one recurring defect.
- Monitor host memory and target-volume free space before assigning a large startup-memory value or creating a dynamically expanding disk.
- Apply user-rights and group-policy changes deliberately, because a security hardening change can surface as 0x80070569 or 0x80070522 without altering the VM wizard.
Final troubleshooting checklist
- Capture the complete dialog and expanded code.
- For 0x80070003, verify the ISO, VM configuration path, virtual-disk path, drive letter, and
C:ProgramDataMicrosoftWindowsHyper-VVirtual Machines. - Preserve existing VM data before deleting or recreating folders.
- Test locally on the Hyper-V host if the wizard was launched remotely.
- For SMB or SOFS storage, check reachability and both share and file-system permissions, then review Hyper-V-VMMS-Admin events.
- For 0x80070569 or 0x80070522, investigate rights, privileges, policy, services, and security software rather than repeatedly changing paths.
- Check available RAM and disk space; stop nonessential VMs and retry with a smaller test VM when resources are tight.
The generic headline becomes actionable only after you connect it to the expanded code, the creation location, and the storage target. That combination identifies whether you should repair a path, authorize a remote store, correct a user-rights policy, or relieve host resource pressure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
