Update to Latest Version of Windows 10 using Update Assistant  

D4ni3l said:

thanks kari for the detailed information and about Windows update potential issue

apparently w10 replace all physical drivers by hyper-V drivers automatically and put them back in case of native boot
that's nice !

You are welcome.

There are a few things to consider when using Windows on native boot VHD. For instance, if you think that it is even remotely possible that you might occasionally need to add the VHD to Hyper-V VM for upgrade or any other purpose, you need to partition VHD correctly. For instance, if VHD will only ever be used as native boot VHD, it does not need System reserved partition (MBR partitioning) or EFI system partitions (GPT partitioning). Simply create VHD with just one single Windows partition and attach it to host, apply Windows image to it with DISM, use BCBOOT to add it to boot menu, done.

But: that VHD would not work in Hyper-V. To be able to use VHD both in native boot and in Hyper-V, it must be properly partitioned, which is why I recommend that you use Hyper-V to create your native boot VHDs. Create first a VM, install Windows normally which automatically creates correct partition structure, update Windows fully when done, shut down the VM, mount the VHD on host and only then add it to boot menu as native boot VHD. See tutorial: Hyper-V - Native Boot VHD Windows 10 Virtualization Tutorials

In doing this you will guarantee that it works without issues both in native boot and in Hyper-V.

A bit more about that WU issue, if VM using a native boot VHD is allowed to connect to network and possible WU issues caused by it. In screenshots below an example, I installed Windows 10 Pro today to a native boot VHD, then later on used the VHD in a new VM. I use PowerShell Windows Update which makes managing updates somewhat easier than WU in Settings app. Read more: Update and Upgrade Windows 10 using PowerShell Windows 10 Installation Upgrade Tutorials

OK, first boot to desktop after native boot VHD was attached to a Hyper-V VM. Listing available updates, I can see that all of them are for host hardware devices, all of them for devices completely missing from VM:


I needed a few Hide-WUUpdate cmdlets to hide all of them, for instance Hide-WUUpdate -Title "Intel*" -Confirm:$False hides all updates starting with string Intel:


After hiding the last unnecessary hardware device update and checking available updates again which returns nothing, I can stop worrying and upgrade using Update Assistant, Media Creation Tool, Windows Update or an ISO. No unnecessary update will now cause issues with upgrade.


After I have fully upgraded Windows on this VM, I shut down and can now boot the host to this upgraded VHD. When booted, I will then unhide all hidden updates.

Kari

hello kari,

I have done exactly what you described

1. Install a new Windows 10 in a new "W10-NATIVE-BOOT.VHDX" with Hyper-V
2. Force the update of the vitual machine with powershell utilities PSWindowsUpdate
   Get-WUInstall
   
3. Update the boot
   
   
   VHDX temporary mounted in the host to check the partitions structure

Everything works as expected
The new VHDX Windows native boot is working and I have done the update of the physical machine with Get-WUInstall

Below the only error I see in the event log of the virtual machine when I switch from native boot to Hyper-V:



It is so easy to do when you know how to do it

Thanks again kari for sharing your expertise

D4ni3l said:

Thanks again kari for sharing your expertise

You are welcome, always nice to get positive feedback :)

I wouldn't be worried about that crash dump error. It's because of differences in RAM (different amount on VM and in native boot) and page file. As the VM is only a temporary solution to get VHDX upgraded, there's no need to change page file settings on VM. The event / error should not occur when again booted natively.

I did manage to convert a native host vhd which I had created natively to be suitable for use in hyper-v as follows:

1) create some unallocated space in vhd (I used minitool partition wizard free)

2) Create Macrium Reflect Rescue ISO

3) Create VM in hyper-v with vhd as hard drive, and Rescue ISO as DVD drive, with VM set to not from Rescue ISO

4) Boot into Macrium and use "fix windows boot problems" and it rebuilds BCD.

Then you can boot vhd in hyper-v

Windows 10 Fall Creators Update now available via Windows 10 Update Assistant.

Hello ThisOn3Guy, and welcome to Ten Forums. :)

Are you able to create a bootable installation USB with the latest version of Windows 10, and clean install Windows 10?

Clean Install Windows 10 Windows 10 Tutorials

Create Bootable USB Flash Drive to Install Windows 10 Windows 10 Tutorials

It will use the latest version of Windows 10.

If you like, you can get another USB flash drive to use. They're pretty cheap to purchase these days.