Windows 10: An error occurred while attempting to checkpoint the selected virtual machines

​

If you see the message An error occurred while attempting to checkpoint the selected virtual machines, with Event ID 3280, this post will help you resolve the issue. A Hyper-V checkpoint captures the state, data, and configuration of a virtual machine at a specific point in time. This is crucial for applying updates or creating […]

This article An error occurred while attempting to checkpoint the selected virtual machines first appeared on TheWindowsClub.com.

read more...

 

Installing a Virtual Machine in Windows 10

Step #1 is to decide which virtual machine software you wish to install.

The three most popular choices are:

• VirtualBox (from Oracle)
• VMWare Workstation Player (from VMWare); and
• Hyper-V (from Microsoft)

Once you've made your choice you can find detailed, illustrated instructions for installing each one on the internet.

As a personal suggestion: You might find it easier to use either VirtualBox or VMWare Workstation Player. Hyper-V is more complicated to setup.

Between VirtualBox and VMWare, I think you'll find VirtualBox more user-friendly, and it has the advantage of allowing you to create checkpoints - backups of your virtual machine - whereas to do that in VMWare you'll need to upgrade to their (expensive!)
paid version.

 

Hyper-V 2019 Checkpoint Operations fails after a day

We backup our Hyper-V 2019/16 servers containing couple of virtual machines, with Unitrend backup system, which requires checkpoints to be able to back the VM's. When we tested to create checkpoint, it would give the error "An error occured while attempting
to checkpoint the selected virtual machines. The operation cannot be performend while the object is in use". When we check the logs we get the following Event ID: 19100, 18012, 18014.
Normally when we reboot the Hyper-V servers , we are able to create checkpoints for a day or so after which the same issue recurs.

We have used ICACLS to grant the "NT Virtual Machine" user of each VM full access, and ensured that the VHD files and checkpoints are in the same folder. We also ovserved that the .avhdx files which are created would remain and are not able to automatically
get merged to the parend .vhdx file.

This is happening al all our Hyper-V 2019 servers which are part of a domain.

 

BSOD when launching Virtual Machine

Hi,



Thank you for writing to Microsoft Community Forums.



I appreciate your effort on this. I understand how difficult it could be when the computer doesn’t work as it is supposed to, we will look into this for you. Please reply with the following details to assist you with the appropriate troubleshooting
steps:

• Which application are you using to create Virtual Machine?
  
• Does the issue occur only when launching a Virtual Machine?
  
• Have you reinstalled Windows on the computer?
  
• What is the make and model of the computer?
  

I have analyzed the dump files shared by you. Since the issue occurs when you launch Virtual Machine, I suggest you to try disabling the VMWare USB Arbitration Service and check if that helps. Please follow the steps mentioned below:

1. Press Windows key + R, to open
   Run dialog box.
   
2. Type services.msc and click on
   OK.
   
3. Look for the VMWare USB Arbitration Service and double click on it to open
   Properties.
   
4. Select Disabled from the drop down for
   Startup and Stop the service.
   
5. Click on Apply and OK.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator