Win10+ Setup Disk (Works with UEFI Secure Boot / BIOS / Install.wim over 4 GB)

Discussion in 'MDL Projects and Applications' started by rpo, Mar 18, 2019.

  1. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60

    It's happening only with 20H1
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. alcit

    alcit MDL Novice

    Mar 1, 2017
    5
    2
    0
    working great.. good bye install.esd
     
  3. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,502
    1,504
    60
  4. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    Figured it out... it's "bootx64.efi" in the \efi\boot folder
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Carbon12

    Carbon12 MDL Novice

    Aug 29, 2014
    1
    0
    0
    #285 Carbon12, Jul 24, 2020
    Last edited: Jul 24, 2020
    I don't understand why any of this is necessary. So the install.wim is bigger than 4gb...split it to 4gb or less .swm files. Put the whole thing on the fat32 and you can boot legacy or uefi from fat32. One partition, no sweat. I must be missing something...what?
     
  6. qwesta

    qwesta MDL Senior Member

    Jul 22, 2011
    351
    136
    10
    indeed, you are missing something, read about this in the previous posts, why this is necessary
    Answer is in the BIOS, as a tip
     
  7. Flipp3r

    Flipp3r MDL Guru

    Feb 11, 2009
    2,021
    970
    90
    It must be something to do with 20H1. I've just upgraded my ADK to this build & have noticed my WinPE no longer shows the UEFI logo but the Windows logo & my WinPE is at a lower resolution.
    Copying back the 19H1 WinPE wim's & all is back to normal...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Flipp3r

    Flipp3r MDL Guru

    Feb 11, 2009
    2,021
    970
    90
    I use a 128GB USB3 key for all my installations. All the Windows and Server Editions I need are included. ESD is much easier to maintain & install from...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    #289 freddie-o, Jul 24, 2020
    Last edited: Oct 3, 2020
    It's giving people more options. Others prefer not to split their install.wim and disable Secure Boot

    More options here...

    [SOLUTIONS] Installing Windows on UEFI System with install.wim over 4 GB
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    It seems to be "bootx64.efi" of 20H1 ("efi\boot" folder).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. qwesta

    qwesta MDL Senior Member

    Jul 22, 2011
    351
    136
    10
    i don't know what was wrong with my USB or the script.
    I'm getting this error all the time
     

    Attached Files:

  12. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    I'm wondering why your Destination Directory is C:\Windows\system32...?



    mydig.PNG
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. qwesta

    qwesta MDL Senior Member

    Jul 22, 2011
    351
    136
    10
    got the error,
    the device manager wasn't recognising my USB drive, so I went to properties and made driver update, thereafter all went fine as it should be.
    Thank so for the response
     
  14. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    #294 freddie-o, Oct 3, 2020
    Last edited: Oct 3, 2020
    Updated the script

    v2.0 (Oct 3, 2020)
    Renamed the script to Win10 Setup Disk
    Few cosmetic changes
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,502
    1,504
    60
    Some people get worried because the file explorer shows the two partitions on the usb disk : just remove the driver letter from the fat32 partition by additing the following statement after line 177 (remove-item ($env:temp + "\bcd.*") -force) :
    Code:
    Get-Volume -DriveLetter $usbfat32.substring(0,$usbfat32.Length-1) | Get-Partition | Remove-PartitionAccessPath -accesspath $usbfat32
     
  16. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    @rpo I was just thinking about this yesterday.
    What if we did this before creating the NTFS partition.
    Will the script work on older versions of Windows that do not support reading and creating multiple partitions on removable storage devices??
    Because it will hide the Fat32 partition first and then create the NTFS partition
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,502
    1,504
    60
    No, it will not work because you can't hide tha fat32 partition as you have robocopy and copy-item statements. Hiding the partition removes the drive letter.
     
  18. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    Sorry I wasn't clear. What I meant was...
    First create the fat32 partition
    Copy all the boot files/folders to the fat32 partition
    Hide the fat32 partition
    Then, create the ntfs partition
    Copy the ISO to the ntfs partition

    Will this work?

    Also noticed this small detail after creating the Setup disk

    Untitled.png
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,502
    1,504
    60
    Yes, this will work. I will adapt the script and i found the correction for the detail you observed.
     
  20. freddie-o

    freddie-o MDL Expert

    Jul 29, 2009
    1,603
    2,673
    60
    Also, when I tested the script on Windows 1607 (14393) Non-administrator account, it wouldn't run
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...