Windows 10: Hyper-V Fails to create new Snapshots: Error: The process cannot access the file because it...

Hello,We have been trying to troubleshoot this issue over the past year. We have Veeam that we are using to create automatic backups of our hyper-v vms. We'll get everything working snapshots are working and veeam job triggers a successful backup mutltiple times. After a couple of days, Veeam starts to fail and when we try to manually create the snapshot, we are getting the following error:The host is Server Core 2022 with Hyper-V installedLet me know further information that I can provide to help solve this issueWe need to figure out what is causing this but we are having issues doing s

:)

 

Hyper-V PowerShell module fails to create new vm

I have a problem with Hyper-V PowerShell module, it fails to create a New-VM on my machine.

It worked fine until I had to reinstall Hyper-V feature in Windows 10.

Since then cannot create VM with powershell cmdlets, creating a VM in GUI works

I receive the following error

New-VM : Hyper-V encountered an error trying to access an object on computer ...... because the object was not

found. The object might have been deleted, or you might not have permission to perform the task. Verify that the

Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again

by using Run as Administrator.

I am the Administrator on local PC, and I checked Hyper-V Virtual Machine Management service, and it is in a running state.

Tried to rebuild MOF file

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

also tried to uninstall Hyper-V feature and reinstall it with powershell, and still no success.

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Any other ideas?

I have Windows 10 Pro, version 1709

Regards,

Igor

 

Hyper V Checkpoint Error

Hi Sarjeant, as an Independent Advisor, I'd be happy to help.

This error generally suggests an issue related to permissions or availability of storage where the checkpoint (also known as snapshot) is being stored. Here are some steps to investigate and potentially solve this issue:

1. Check Permissions: Ensure that the account used by Veeam to back up the VMs has appropriate permissions on the Hyper-V host, and specifically to the directory where the VM's disks and configuration files are stored. This account typically needs full control or administrative access to these resources.

2. Check Storage Space: Ensure that there is sufficient storage space on the disk where the VM's files are stored. When a checkpoint is created, Hyper-V needs to create an .avhdx file which can grow as large as the disk it is shadowing. If there isn't enough space, the operation will fail.

3. Check NTFS Rights: Ensure that the system and the account used by Veeam to back up the VMs have full control over the VM's folder and all its files. You can check this by right-clicking on the folder, going to "Properties", selecting the "Security" tab, and then checking the permissions.

4. Check Antivirus or Security Software: Sometimes, antivirus or security software can interfere with Veeam's ability to back up VMs. You might need to adjust the settings of these programs to exclude the directories where your VM's files are stored.

5. Reconfigure VM Storage Path: If permissions seem correct, and there's enough space on the storage device, it could help to try moving the VM storage to a different location, creating a checkpoint manually, and then moving it back.

6. Reset the VM: As a last resort, if none of the above steps solve the issue, you could export the VM, completely remove it from Hyper-V, and then import it again. Be sure to take necessary steps to avoid data loss, and only try this if you're comfortable with managing Hyper-V at this level.

Remember, any time you are troubleshooting, it's wise to proceed carefully, documenting your steps, and ensuring you have recent backups before making any changes. If you're not comfortable with any of these steps, you should contact a local IT service provider or continue working with Veeam support.

 

Hyper-V new 'Quick Create' Ubuntu 18.04.01 LTS errors on boot

After enabling Hyper-V in Windows 10 Pro and following the 'Quick Create' type wizard in Hyper-V to create a Ubuntu 18.04.01 LTS virtual machine, Hyper-V encounters the following two errors when trying to boot this virtual machine.

This is following the completion of the 'Quick Create' wizard to establish the Hyper-V settings for this particular virtual machine.

When starting this virtual machine the window that this is occurring in displays the following two errors:

• Spectre V2: Spectre mitigation LFENCE not serializing, switching to generic retpoline.
• PCI: Fatal: No config space function found.

This results in the Ubuntu boot up failing and falling back to the Linux Grub menu.

I'm using Windows 10 Pro 64bit, version 1809 on a HP EliteBook 745 G5 notebook which uses an AMD Ryzen 5 2500u CPU.

Any help much appreciated.