

If the virtual machine has any checkpoints, they are left as-is. Warning 3: Only the active virtual machine is impacted. It will not change anything on saved or paused VMs. This script will turn off a running virtual machine (you are prompted first). It must be in an Off state (not Saved or Paused).

Warning 2: These settings cannot be modified while the virtual machine is on. Any of these fields may be tracked and used by third-party software that manipulates the virtual machine. Any of these fields may be tracked and used by software inside the virtual machine.

Other side effects, potentially damaging, may occur. Modification of the BIOS GUID field is likely to trigger software activation events. Warning 1: Changes to these fields are irreversible without restoring from backup. There are other modifiable fields on this particular WMI class, but these are the only fields that I’m certain have no effect on the way that Hyper-V handles the virtual machine. You can provide your own GUID or specify a new one. On virtual machines, it is possible and even necessary at times. On physical machines, I don’t believe that it’s possible to change the UUID. You can see it on any Windows computer with gwmi Win32_ComputerSystem | select UUID. Microsoft’s implementation of the standard UUID is called a Globally Unique Identifier (GUID).
