DavidY said:

Hi Kari,
Does this tutorial include setting up the Recovery partition?
I wondered if another step was required to copy winre.wim onto there, and then a reagentc step to link to it?

Sorry for delayed reply.

If you follow the instructions in this tutorial to the letter, EFI, WinRE and MSR partitions will be created exactly as when doing a traditional install. No additional actions are required.

I am not sure at which point EFI and WinRE will be populated, can't find any documentation about it.

this nice method works on Hyper-V Virtual Machine also

I attached a Windows ISO 1703 (April 2017) as the first DVD for boot
I put a copy of [ 16299.15.170928-1534.rs3_release_clientconsumer_ret_x64fre_en-us...........esd ] (Sept 2017) on an second ISO DVD with ImgBurn

I followed your instructions above

I now have a clean W10-1709 virtual machine

So simple in fact when you know

thanks Kari

some pictures

Hi @Kari,

After todays online forums, I gave this a go (installing as dual boot). I ran into a couple of problems:-

1) I just cannot boot from a 17128 iso no matter what I try. I got round this by booting from a Macrium Reflect Winpe image and running Dism from there, and it worked fine. Hell it is a lot faster!

I then booted into my normal windows, and added a boot entry. Then I ran into next problem.


2) I selected the 17128 installation from the dual boot menu, and it just would not boot into the new installation, just getting into a reboot loop and eventually ending back at dual bot menu after quite some time. I then used the Macrium Deploy option and selected the 17128 installation and BAM - it booted straight to OOBE in seconds.

Running deploy, it complained about the standard SATA controller and let me install the AMD version, which I always had to manually install after a clean install, and worked. So I am guessing there is some incompatibility with the standard windows SATA controller and 17128 (1803 versions) on AMD pc.

Now I know what to do, I can clean install fine on host pc now.

Many thanks for advice and this great guide, even if I do it a little differently.


Thinking about it, I probably do not even need to boot to a winpe drive to run dism if installing a dual boot?

Edit: Indeed, dism can be run from normal windows to clean install a dual boot version. Very nice.


So key steps:-

Create an install.wim using @Kari's uuptoiso tool.

Shrink C drive by say 50GB

Create new partition in newly unallocated space

Deploy image with dism from an admin command prompt

Add boot entry from admin command prompt

Boot pc - select new installation

Beauty of this method is you an carry on using existing windows for most of it.

Obviously, if not dual booting i.e. only single booting, you will have to boot first into a win pe environment to run dism etc.

cereberus said:

Hi @Kari,

After todays online forums, I gave this a go (installing as dual boot). I ran into a couple of problems:-

1) I just cannot boot from a 17128 iso no matter what I try. I got round this by booting from a Macrium Reflect Winpe image and running Dism from there, and it worked fine. Hell it is a lot faster!

I then booted into my normal windows, and added a boot entry. Then I ran into next problem.


2) I selected the 17128 installation from the dual boot menu, and it just would not boot into the new installation, just getting into a reboot loop and eventually ending back at dual bot menu after quite some time. I then used the Macrium Deploy option and selected the 17128 installation and BAM - it booted straight to OOBE in seconds.

Running deploy, it complained about the standard SATA controller and let me install the AMD version, which I always had to manually install after a clean install, and worked. So I am guessing there is some incompatibility with the standard windows SATA controller and 17128 (1803 versions) on AMD pc.

Now I know what to do, I can clean install fine on host pc now.

Many thanks for advice and this great guide, even if I do it a little differently.


Thinking about it, I probably do not even need to boot to a winpe drive to run dism if installing a dual boot?

Edit: Indeed, dism can be run from normal windows to clean install a dual boot version. Very nice.


So key steps:-

Create an install.wim using @Kari's uuptoiso tool.

Shrink C drive by say 50GB

Create new partition in newly unallocated space

Deploy image with dism from an admin command prompt

Add boot entry from admin command prompt

Boot pc - select new installation

Beauty of this method is you an carry on using existing windows for most of it.

Obviously, if not dual booting i.e. only single booting, you will have to boot first into a win pe environment to run dism etc.

This should work , Thanks

cereberus said:

Hi @Kari,

After todays online forums, I gave this a go (installing as dual boot). I ran into a couple of problems:-

1) I just cannot boot from a 17128 iso no matter what I try. I got round this by booting from a Macrium Reflect Winpe image and running Dism from there, and it worked fine. Hell it is a lot faster!

I then booted into my normal windows, and added a boot entry. Then I ran into next problem.


2) I selected the 17128 installation from the dual boot menu, and it just would not boot into the new installation, just getting into a reboot loop and eventually ending back at dual bot menu after quite some time. I then used the Macrium Deploy option and selected the 17128 installation and BAM - it booted straight to OOBE in seconds.

Running deploy, it complained about the standard SATA controller and let me install the AMD version, which I always had to manually install after a clean install, and worked. So I am guessing there is some incompatibility with the standard windows SATA controller and 17128 (1803 versions) on AMD pc.

Now I know what to do, I can clean install fine on host pc now.

Many thanks for advice and this great guide, even if I do it a little differently.


Thinking about it, I probably do not even need to boot to a winpe drive to run dism if installing a dual boot?

Edit: Indeed, dism can be run from normal windows to clean install a dual boot version. Very nice.


So key steps:-

Create an install.wim using @Kari's uuptoiso tool.

Shrink C drive by say 50GB

Create new partition in newly unallocated space

Deploy image with dism from an admin command prompt

Add boot entry from admin command prompt

Boot pc - select new installation

Beauty of this method is you an carry on using existing windows for most of it.

Obviously, if not dual booting i.e. only single booting, you will have to boot first into a win pe environment to run dism etc.

You can also use this to install to a virtual hard drive instead of creating a new partition. Using Macrium Reflect Redeploy as I did is a little trickier as you have to attach the virtual disk from the Macrium Reflect Command prompt first using diskpart commands, but only take a minute to do.

Today, I tried an experiment - I wanted to clean install Skip Ahead in a hyper-v vm, and normally it takes ages on my laptop. I followed the guide booting from skippy iso up to point of having created all the required partitions, and then shutdown VM.

I then went to host, and attached vhd as a drive using disk management, and used dism from host to deploy OS instead.

I then detached vhd from host, and booted to skippy iso, and created boot entry, booted vm and it went as I hoped straight to oobe.

Doing dism on host rather than in vm is much quicker on my laptop.

I then made a copy of vhd, mounted as drive in host, made a boot entry. I tried rebooting to host but it failed as cases in previous post. I rebooted into Macrium Reflect, added vhd using diskpart and ran Macrium Redeploy, and as before BAM on rebooting, straight to oobe.

Doing it this way, means I can install on vm and dual boot on host with essentially only one main installation phase. You have to do it via vm first to ensure drive has all the partitions needed to boot in vm.