It appears that the days of simply being able to export a VM and import it into any Host you like are over. With Windows 11 requiring that the VM has TPM turned on in its Settings, and that if the Host that created it also has TPM turned on, then when such a VM is exported and imported to another Host the imported VM fails to run with the error: "the key protector could not be unwrapped"
At first I thought this meant the VM was a Shielded VM but I'm increasingly comming to the conclusion that it may just be down to the need for the VM to have its own TPM if it is to run W11. More on this, first posted over on Ten Forums as my first Windows 11 VM that could not be exported and imported successfully was created on a Windows 10 Pro Host machine.
www.tenforums.com
At first I thought this meant the VM was a Shielded VM but I'm increasingly comming to the conclusion that it may just be down to the need for the VM to have its own TPM if it is to run W11. More on this, first posted over on Ten Forums as my first Windows 11 VM that could not be exported and imported successfully was created on a Windows 10 Pro Host machine.
Inadvertently created a Hyper-V Shielded VM - Windows 10 Help Forums
Well here's an interesting twist. I appear to have inadvertantly created a Hyper-V Shielded VM, one that cannot be imported and run on any Host except the one it was created on. Microsoft said: To help protect against compromised virtualization fabric, Wi
www.tenforums.com
My Computers
System One System Two
-
- OS
- Windows 11 Home
- Computer type
- Laptop
- Manufacturer/Model
- Acer Aspire 3 A315-23
- CPU
- AMD Athlon Silver 3050U
- Memory
- 8GB
- Graphics Card(s)
- Radeon Graphics
- Monitor(s) Displays
- laptop screen
- Screen Resolution
- 1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
- Hard Drives
- 1TB Samsung EVO 870 SSD
- Browser
- Edge, Firefox
- Antivirus
- Defender
- Other Info
-
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 128GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro 22H2 Insider Beta as a native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 128GB NVMe ssd, supported device running Windows 11 Pro.
-
- Operating System
- Windows 11 Pro
- Computer type
- Laptop
- Manufacturer/Model
- Dell Lattitude E4310
- CPU
- i5 M 520
- Motherboard
- 0T6M8G
- Memory
- 8GB
- Screen Resolution
- 1366x768
- Hard Drives
- 500GB HDD
- Browser
- Firefox, Edge
- Antivirus
- Defender
- Other Info
-
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 128GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro 22H2 Insider Beta as a native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 128GB NVMe ssd, supported device running Windows 11 Pro.
