Windows 10: Announcing Windows 10 Insider Preview Build 16193 PC and 15213 Mobile

@waltc, you cannot clean install from mounted ISO. Only in-place upgrade is possible.

To clean install you have to boot PC from install media (USB / DVD), alternatively boot from WinPE media and apply install.wim (or install.esd) with DISM, or boot from WinPE media and launch Windows setup from a hard disk partition (or USB / DVD).

 

This is an FYI for anyone using Avast Free. After I upgraded my 16188 Home and Pro installations to 16193, both installations showed signs of having major problems. Specifically, I could not start programs (ie, Rufus), I could not uninstall programs (ie Avast) so I took an uneducated guess that Avast might be causing the problems. With that said, I used Macrium to go back to 16188, then I used aswclear to uninstall Avast, and I was finally able to upgrade Home and Pro to 16193 without any major issues.

My lesson learned: Do not continue to use a 3rd party AV solution when running on a pre-release build.

 

I always prefer clean install when there is an ISO available. So much less hassle. I stopped using Avast because I felt the latest versions were too intrusive.

 

I totally agree a clean install is always the safest way to go; however, I will wait for the final public release because doing a clean install on two machines (every week?) during the pre-release periods is just too much work IMHO.

 

plus adds wear and tear to drives..

all the erases and writes...

 

Two machines would be a bit much. I don't use insider builds on my main machine because its used for work. So it does remain fun when builds

 

And what happens if the third option is chosen? is not a clean install?:

 

All Macrium Reflect users:

Check to make sure your USB recovery drive still boots from UEFI. I have a Macrium Home rescue USB drive and a Pro rescue USB drive and they both failed to boot from UEFI (but they worked on 16188). So, I tried recreating them and they still failed to boot from UEFI.

The temporary fix is/was to turn off secure boot in both my Home and Pro machine and now they both boot properly from UEFI.

I'm not sure if this is a Macrium issue or the Win PE version that Macrium uses to create the rescue drives.

In any event, you can also just leave secure boot enabled and then use the legacy boot option (if available) to get to the recovery menu until this gets fixed.

 

I was under the impression that a usb stick needed FAT32 to boot, as most Motherboards do not support UEFI.

 

Edit: After further consideration I have changed my position. This procedure does not result in a clean install in the truest sense of the term. For lack of any thing better I am going to call it a fresh install.

I use a procedure I found two years ago. I don't remember where I found it, so I can not give credit to the person who created it. Some of the steps may seem counter-intuitive but they work, so do not skip them.

First go to Disk Management and create a new simple volume in an unallocated area. Note the partition number of the new volume. In my example mine is partition number 5. Do not assign a drive letter. Do not format volume. Don't worry about RAW File System. Windows Setup will handle this.













Mount ISO but do not run Setup.exe. Go to the Sources folder and run Setup.exe from there.









Proceed as usual in Windows Setup. Choose Custom Install.





From Windows Setup choose the partition number created earlier. In my example partition number 5.





Click Next to clean install fresh install Windows into your newly created partition.





I don't know if this can be considered a "clean" Windows install, but it sure acts and looks like a clean install. @Kari, give it a try sometimes if you are at all interested. I think you might be surprised. It certainly surprised me that a clean install fresh install could be achieved from a mounted ISO inside Windows

I realize some hard-liners are going to say that a clean install is a single boot system where there are four partitions created for an UEFI/GPT environment (of course a Leagcy/MBR would be different) and I can understand that interpretation. However the procedure above produces a dual (multi) boot system with Windows for all intents and purposes in a seemingly clean install fresh install.

Notice: The procedure described above is not for a novice. It has the real potential to go sideways if not performed properly (as in an unbootable system). It took me a couple of tries to get it right. Please make sure you have a backup plan that may include Macrium Reflect. It is presented as is and I offer no guarantee of a successful outcome.

Mods/Admins I know you do not need my permission but please feel free to move or delete this post or @Brink may want to turn it into a tutorial. That's where it probably belongs.

 

The stick was created as fat32 with the Macrium Reflect utility.

The options selected were mbr/gpt so it could boot from either (provides 2 options on the boot menu).

 

I think most modern motherboards do now support UEFI as its becoming the de rigueur replacement for BIOS.

 

Referring only to booting up.....using USB.

 

I had no idea of ​​this method, excellent, many times I wanted to install from scratch in another partition and the only way I found was to burn the ISO, thank you very much.
*Thumbs*Thumbs

 

One drawback for this procedure is, it won't give you the C: Windows, but another drive letter. I wasn't aware of the whole procedure, maybe this could be the reason for that, but tracit99 will report, if I'm wrong... *Smile