Yes. That seems to be the case now. I used it successfully when I had issues moving a Hyper-V virtual machine from its old Host machine to a new one. See post #14 here:
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 HDD
- 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.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, Windows 11 Pro.
-
- Operating System
- Windows 11 Pro
- Computer type
- Laptop
- Manufacturer/Model
- Dell Lattitude E4310
- CPU
- i5 M 520
- Motherboard
- 0T6M8G
- Memory
- 4GB
- 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.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, Windows 11 Pro.
