installing with UEFI/GPT - 1803 build

Page 2 of 2 FirstFirst 12
  1. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
       #11

    Fully agree. I was just pointing out that the newer versions of Rufus make it pretty hard to screw up. If you pick UEFI you get Fat32. If you pick MBR you get NTFS.

    I like the universal flash drive as Bree mentioned (and you've mentioned many times). That's really what Rufus should be doing.
      My Computers

  2. cereberus's Avatar
    Posts : 12,014
    Windows10
       #12

    Ztruker said:
    Fully agree. I was just pointing out that the newer versions of Rufus make it pretty hard to screw up. If you pick UEFI you get Fat32. If you pick MBR you get NTFS.

    I like the universal flash drive as Bree mentioned (and you've mentioned many times). That's really what Rufus should be doing.
    That's the whole point. Do not use Rufus as creating ntfs drives can cause issues.

    Rufus was invented back in days of Windows 7 or earlier when isos could not be mounted natively. Now you can since Windows 8, it is largely redundant.

    As others say.

    1) mount iso as drive

    2) format flash drive as MBR and fat32.

    3) Copy files from mounted drive to flash drive.

    4) If flash drive is to be used on legacy bios pc, mark partition on flash drive as active.

    That's it.
      My Computer


  3. Posts : 12
    windows 10 64 bit Pro
    Thread Starter
       #13

    Formatting with FAT32 instead of NTFS did the trick, many thanks.
      My Computer

  4. NavyLCDR's Avatar
    Posts : 15,515
    Windows 10 Pro
       #14

    Glad it worked for you!
      My Computer


  5. Posts : 1
    Windows 10 Pro x64, version 1803
       #15

    If install.wim is too large for fat32...


    In my case install.wim was too large for fat32, so I had to split it into two files. Found this by Armin Oberneder:

    If the install.wim file of the Windows image is larger than 4GB, an error will occur during the copying process. At the end of the copy process, the message that the file is too large appears. This message appears, because the FAT32 file system reaches its limits and cannot process >4GB files.

    In order to finish the UEFI-USB-Stick you have to use a little trick:

    Using DISM, the file must be split into two or more <4GB files. Please note that this process is only possible up to Windows 7 or Windows Server 2008.[3][4]

    Simply enter the following command:
    Code:
    Dism /Split-Image /ImageFile:E:\sources\install.wim /SWMFile:C:\Users\Administrator\Desktop\install.swm /FileSize:3000
    • /ImageFile: Path of the source file install.wim in the sources folder of the Windows ISO
    • /SWMFile: Path of the split target files
    • /FileSize: Maximum size of split target files in MB

    Now you can copy the split install.wim, install2.wim, install3.wim etc. to the USB stick in the "sources" directory.
    Cheers
      My Computer

  6. cereberus's Avatar
    Posts : 12,014
    Windows10
       #16

    BigOlTuna said:
    In my case install.wim was too large for fat32, so I had to split it into two files. Found this by Armin Oberneder:



    Cheers
    Much easier way now Windows supports multiple partitions on usb flash drives.

    Create bootable USB installer if install.wim is greater than 4GB | Windows 10 Tutorials
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:24.
Find Us




Windows 10 Forums