Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC Insider

cereberus said:

Totally agree - only downside of a vhd is you cannot upgrade build if vhd is attached to host.

That's the reason I always create my native boot VHDs as MBR disks. It's so incredibly easy to upgrade it in Hyper-V.

To upgrade: Create a new temporary VM using your VHD as existing disk, boot VM from Windows install media, open Command Prompt with SHIFT + F10, enter command C:\Windows\System32\bcdboot C:\Windows to add Windows on VHD to VM's boot menu, restart, upgrade, shut down VM, done. You can now boot back to to it natively from host boot menu.

If you create VHD as GPT, it will be more complicated.

LEOPEVA64 said:

I also have the bug in the WD icon in the system tray, and speaking of WD, I don't remember having seen this animation before in any other part of the system or in some UWP app:


It's nice, I like it :).

Yup, UWP is all about eye-candy... doesn't bring much else to the party ...

Kari said:

That's the reason I always create my native boot VHDs as MBR disks. It's so incredibly easy to upgrade it in Hyper-V.

To upgrade: Create a new temporary VM using your VHD as existing disk, boot VM from Windows install media, open Command Prompt with SHIFT + F10, enter command C:\Windows\System32\bcdboot C:\Windows to add Windows on VHD to VM's boot menu, restart, upgrade, shut down VM, done. You can now boot back to to it natively from host boot menu.

If you create VHD as GPT, it will be more complicated.

I create the installation in Hyper-v first as gen 2 and then attach that to host. Then the vhd has all the setup needed to attach to Hyper-V later. Then I just use bcdboot to make vhd bootable on host. Never had a driver issue with Windows 8 or 10. I never use Windows 7 any more.

One thing is for sure, there will be a long list of fixes in next build. Mine is deteriorating fast. Store and some other APPs stopped detecting internet and had to lower OC of the processor to stay stable.

Kari said:

That's the reason I always create my native boot VHDs as MBR disks. It's so incredibly easy to upgrade it in Hyper-V.

To upgrade: Create a new temporary VM using your VHD as existing disk, boot VM from Windows install media, open Command Prompt with SHIFT + F10, enter command C:\Windows\System32\bcdboot C:\Windows to add Windows on VHD to VM's boot menu, restart, upgrade, shut down VM, done. You can now boot back to to it natively from host boot menu.

If you create VHD as GPT, it will be more complicated.

Not all pcs allow you to boot an mbr vhd if pc is set to UEFI. I have tried this and it worked on one laptop that automatically will boot uefi or legacy bios. Another just refused saying no OS found.

One easy way is to install Windows 10 initially as gen 2 in Hyper-V, then attach vhd to host, and add a boot entry with bcboot.

cereberus said:

Not all pcs allow you to boot an mbr vhd if pc is set to UEFI. I have tried this and it worked on one laptop that automatically will boot uefi or legacy bios. Another just refused saying no OS found.

One easy way is to install Windows 10 initially as gen 2 in Hyper-V, then attach vhd to host, and add a boot entry with bcboot.

I have not found / used a UEFI PC or laptop that does not allow Windows to be booted from MBR VHD? There are no logical reasons why it would be a promlem.

Kari said:

I have not found / used a UEFI PC or laptop that does not allow Windows to be booted from MBR VHD? There are no logical reasons why it would be a promlem.

Well I have - I am guessing it is an old bios as an old PC.