Build 19043.928 out to Beta & Release Channel + ISO for 19043.928

I was wondering why you folks seem to be converting the .wim file.  I know it is larger than 4 GBs since I did a clean install yesterday after having downloaded the .iso.  But, just in case you don't know, there is an easier way, ..  The drive booted and the install started automatically, which I did not expect.

I did learn yesterday you can no longer make a partition active on a USB drive with either Diskpart or Disk Management.

@Saltgrass, 

Looks like the active command works fine with DISKPART.

I'm just making an Installation USB media the same way that MCT does.

One Fat32 partition, that can boot on either UEFI or Legacy BIOS.

If the install.wim is bigger than 4,294,967,296 bytes it cannot be copied to a FAT32 disk so I just convert the install.wim to install.esd to stay below the limit.

I tried marking mine active multiple times, and as you can see, it is not currently active.  All I got was the message below.  I also just noticed the USB drive is showing as GPT .. I did not do anything I know of for that to happen.

Maybe I am missing something but all I do is mount the .iso and copy the files to the NTFS partition.  No DISM operations necessary..

I tried marking mine active multiple times, and as you can see, it is not currently active.  All I got was the message below.  I also just noticed the USB drive is showing as GPT .. I did not do anything I know of for that to happen.

Maybe I am missing something but all I do is mount the .iso and copy the files to the NTFS partition.  No DISM operations necessary..

I know, NTFS does not have the 4GiB file size limit.

What is in the FAT32 partition ? Are you booting from it ? How was it prepared ? How did the disk convert to GPT ?

Here are my 2 ISO Files, the first is the one downloaded from MS Insider with the install.wim

The second is with the install.esd, 

If I mount the one with the .esd I can copy all the files to a FAT32 USB Flash drive with the Partition set Active.

That can boot from Both Legacy BIOS or UEFI machines.

There is nothing in the FAT32 partition.  I just created another one.  When I set it in the Boot Device menu, I was given both partitions as a choice.  If I chose the FAT32 partition, nothing happened but if I selected the NTFS partition it booted to the install.

I am wondering now if the FAT32 partition is still necessary but it does work with it on the drive.  I suppose removing the FAT32 partition will be my next test.. ;)

There is nothing in the FAT32 partition.  I just created another one.  When I set it in the Boot Device menu, I was given both partitions as a choice.  If I chose the FAT32 partition, nothing happened but if I selected the NTFS partition it booted to the install.

I am wondering now if the FAT32 partition is still necessary but it does work with it on the drive.  I suppose removing the FAT32 partition will be my next test.. ;)

There are some older UEFI machines that can still boot from NTFS, but the newer machines that are UEFI only require FAT32 or will not boot. 

An example is my Dell XPS 8700 that is set for UEFI, but it can still boot from an NTFS USB device.

The newer Lenovo Yoga 920 or the Dell XPS 8930, which are UEFI only machines,  will only boot from FAT32.

What machine are you using ?