- Local time
- 2:00 PM
- Posts
- 5,593
- OS
- Windows 10 Pro + others in VHDs
Not really a request for help - more an observation.
Years ago.
At one time, you could not upgrade an OS e.g. from one Insider version to the next when using a native booting vhdx file.
I had to attach the vhdx file to a Hyper-V VM and upgrade using a virtual machine, then I could reconnect VHDX file as a native booting vhdx file (deleting old boot entry and recreating a new one).
Later (couple of years back)
A year or two back, MS made it possible to upgrade a vhdx file in native boot mode. I could update without Hyper-V or do it in VM (e.g. if I wanted to keep using pc whilst vhdx was upgraded). This was the perfect solution - I could upgrade natively or in a vm.
Now (not sure when this started)
Something has happened and now if I upgrade by VM now, and try to reattach the vhdx file as native booting (recreating boot entry), it falls over and refuses to boot.
I can now only upgrade when natively booting - the vhdx does work in a vm.
However, I no longer have the option to do the upgrade in a vm (if I want to natively boot vhdx) which was useful sometimes.
Ok, this is slightly irritating and not a big deal, but if I forget and do the upgrade in a vm, I shoot myself in the foot, and have to revert to a backup!
Years ago.
At one time, you could not upgrade an OS e.g. from one Insider version to the next when using a native booting vhdx file.
I had to attach the vhdx file to a Hyper-V VM and upgrade using a virtual machine, then I could reconnect VHDX file as a native booting vhdx file (deleting old boot entry and recreating a new one).
Later (couple of years back)
A year or two back, MS made it possible to upgrade a vhdx file in native boot mode. I could update without Hyper-V or do it in VM (e.g. if I wanted to keep using pc whilst vhdx was upgraded). This was the perfect solution - I could upgrade natively or in a vm.
Now (not sure when this started)
Something has happened and now if I upgrade by VM now, and try to reattach the vhdx file as native booting (recreating boot entry), it falls over and refuses to boot.
I can now only upgrade when natively booting - the vhdx does work in a vm.
However, I no longer have the option to do the upgrade in a vm (if I want to natively boot vhdx) which was useful sometimes.
Ok, this is slightly irritating and not a big deal, but if I forget and do the upgrade in a vm, I shoot myself in the foot, and have to revert to a backup!
My Computer
System One
-
- OS
- Windows 10 Pro + others in VHDs
- Computer type
- Laptop
- Manufacturer/Model
- ASUS Vivobook 14
- CPU
- I7
- Motherboard
- Yep, Laptop has one.
- Memory
- 16 GB
- Graphics Card(s)
- Integrated Intel Iris XE
- Sound Card
- Realtek built in
- Monitor(s) Displays
- N/A
- Screen Resolution
- 1920x1080
- Hard Drives
- 1 TB Optane NVME SSD, 1 TB NVME SSD
- PSU
- Yep, got one
- Case
- Yep, got one
- Cooling
- Stella Artois
- Keyboard
- Built in
- Mouse
- Bluetooth , wired
- Internet Speed
- 72 Mb/s :-(
- Browser
- Edge mostly
- Antivirus
- Defender
- Other Info
- TPM 2.0