Windows 10 1903 USB won't boot

Discussion in 'Troubleshooting Help' started by sonicthemouse, Jun 13, 2019.

  1. sonicthemouse

    sonicthemouse Member

    Joined:
    Jan 9, 2006
    Messages:
    804
    Location:
    3207 (BH) / 3033 (AH)
    Hey guys and gals,

    I'm literally tearing my hair out here.

    I have a USB stick that I like to use to boot from, to install Windows 10 on PCs as needed.

    I created it using Win10 1809 Media Creation Tool.

    Worked fine for a year, no worries.

    Since the release of 1903, I decided to update it, so when I do fresh installs, I don't need to then update to 1903 separately.

    So I formatted the USB, ran the 1903 media creation tool, failed.
    Tried a different USB stick, failed.
    Tried running it from a different PC, failed.
    Finally tried running it from a Win 7 PC, and it worked :D

    But the stick is not bootable. Tried it in old non-UEFI PCs, UEFI-only PCs, CSM mode in BIOS, and PCs which allow you to boot to either UEFI or Legacy from the same USB stick (works for Acronis USB).

    But none can boot the stick.

    I even tried downloading the 1903 ISO, and using Rufus to create a bootable USB instead of the media creation tool. Still won't boot.

    Now I know it's not a problem with Rufus cos I then used it to create a bootable FreeDOS USB and it worked fine.

    I'm wondering if MS have f**cked the boot stuff in the 1903 ISO?

    Anyone actually done this and got it working?

    Am I missing something obvious?

    Any help appreciated. I didn't keep the 1809 bootable stick so right now I have no way to install Windows 10 :lol:
     
  2. Myne_h

    Myne_h Member

    Joined:
    Feb 27, 2002
    Messages:
    9,210
    Best suggestion: Wipe the drive and try again.

    cmd
    diskpart
    lis dis
    sel dis #
    clean

    MAKE SURE YOU SELECT THE CORRECT DISK!!!!! (#) It's why I have lis dis as the 3rd command.

    Wipes all the partitions and any possible structures, flags, whatever.

    Then you just need to create a new fat32 partition.
    Then try the MCT again. I *assume* that does the same job as rufus.

    If it doesn't... just copy all the files over from the iso and a UEFI machine should boot.
     
    Last edited: Jun 13, 2019
  3. Matthew kane

    Matthew kane Member

    Joined:
    Jan 27, 2014
    Messages:
    2,363
    Location:
    Melbourne
    I usually download the iso and rufus the fucker. Never failed on me.
     
  4. terrastrife

    terrastrife Member

    Joined:
    Jun 2, 2006
    Messages:
    18,595
    Location:
    ADL/SA The Monopoly State
    checksum match for ISO?
     
  5. Bold Eagle

    Bold Eagle Member

    Joined:
    Jun 28, 2008
    Messages:
    9,378
    Location:
    Brisbane
    Agree with this it reads like a corrupt ISO.

    If you can get into the OS on any of the target systems you could do a Win10 inplace upgrade;
    https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
    That is;
    - Mount the ISO,
    - run the Setup.exe

    Here are my checksums via 7-zip's CRC-SHA tool;
     
    Last edited: Jun 13, 2019
  6. pwlm1975

    pwlm1975 Member

    Joined:
    Apr 18, 2016
    Messages:
    395
    Location:
    Logan, Qld
    +1 to this.
     
  7. im late

    im late Member

    Joined:
    Jan 5, 2012
    Messages:
    1,546
    Location:
    Canning Vale WA 6155
    I used the ms media creation tool to create 1903 usb bootbles in the last two weeks with Zero issues. Have used on a dozen different PCs at work with zero issues.

    So from my experience MS continues to NOT let me down at work or home
     
  8. ibace

    ibace Member

    Joined:
    Aug 10, 2015
    Messages:
    172
    Location:
    Bathurst NSW...
    I have used the MS and Rufus at different times; mostly Rufus tho not at 100%... burnt the 1903 using Rufus - no issues at all and have loaded about 7 systems so far...
    I downloaded the GB version not the US....my checksums were;

    Name: Windows.10.1903.iso
    Size: 3,975,020,544 bytes (3.70 GB)
    CRC32: d8ef265d
    MD5: 55caa8fb2ce8934a7bd0dbf5d91e8cb5
    SHA1: 11fdcccfcfedf09c0ffca6add9d8a08a10bff0df
     
  9. elvis

    elvis Old school old fool

    Joined:
    Jun 27, 2001
    Messages:
    38,010
    Location:
    Brisbane
  10. Bold Eagle

    Bold Eagle Member

    Joined:
    Jun 28, 2008
    Messages:
    9,378
    Location:
    Brisbane
    Agree and you don't have to be concerned about network issues/disruptions.
     
  11. OP
    OP
    sonicthemouse

    sonicthemouse Member

    Joined:
    Jan 9, 2006
    Messages:
    804
    Location:
    3207 (BH) / 3033 (AH)
    Thanks for the replies everyone :D

    Currently I've been using the 1809 media creation tool (which creates a perfectly working bootable USB) then doing the in-place update to 1903 (great minds think alike Bold Eagle :lol:) but it's a pain and I want to know why the "clean" method (no leftover bits and pieces from 1809) is working okay for the rest of you and not for me :confused:

    And yes, it's definitely better than trying to use the native "Windows Update" to do it, but this is more for fresh installs.

    Here are my checksums (EN-US), not sure why they're different when I downloaded it using the media creation tool...

    Again Bold Eagle, was yours EN-US, x64?

    Windows1903.iso
    3.69 GB (3,967,483,904 bytes)
    CRC32: 2B365C57
    CRC64: 74011192B9A79F55
    SHA256: BCD6430839EE45B87EBAEAA2CD2B8C54985FB01D49717DC33CA2DAF515AA7053
    SHA1: 2C1D488BA9B64DC5B161AFE4E42EDAF22F267833

    im late - yeah, I never had a problem with 1803 or 1809 media creation tool. Only this one.

    Can I just ask, are you using a USB3.0 or 2.0 stick? I've now tried a Patriot 3.0, Kingtson 3.0 and Sandisk Cruzer Blade 2.0, tried the 3.0 sticks in 3.0 ports, and 3.0 in 2.0, and 2.0 in whatever, with Media Creation Tool on about 4 different PCs, all give the same error with every stick. Tried it at work and at home in case the firewall / ISP is messing up the download. Tried RUFUS-ing the ISO to each of the 3 sticks, still nothing bootable.

    Yet if I use 1809 Media Creation Tool, it works perfectly on all 3 sticks, bootable in 2 different systems in Legacy and UEFI mode :rolleyes:

    The only time I've managed to successfully run the 1903 tool to build a bootable USB and actually not have an error, was using a Windows 7 machine. But that drive still didn't boot :lol: :upset:
     
  12. im late

    im late Member

    Joined:
    Jan 5, 2012
    Messages:
    1,546
    Location:
    Canning Vale WA 6155
    Think it is a Verbatim usb 2.0 stick.
     
  13. Myne_h

    Myne_h Member

    Joined:
    Feb 27, 2002
    Messages:
    9,210
    Did you do what I said to do?
    Wipe the drive properly using diskpart?

    I've had issues with booting from sticks that have only been solved by wiping that way and trying again.

    As I said, if it's UEFI, all you need to do is clean the disk, create a new fat32 partition and literally copy paste the files from the ISO to the drive.

    If it's UEFI, it'll boot.
     
  14. ausduckz

    ausduckz Member

    Joined:
    Oct 27, 2009
    Messages:
    193
    Location:
    3690
    Could try using the Windows 10 Download Tool to save the ISO rather then create a USB drive.

    Then use Windows 7 USB/DVD Download Tool to create the USB drive using the Windows 10 ISO;
    https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool

    I've used that Windows 7 tool for years since it's release and has never caused me any issues.

    If all that fails, we could discuss downloading the .ESD (Microsoft's Electronic Software Download) file direct from Microsoft, and converting it to .ISO
     
    Last edited: Jun 18, 2019
  15. OP
    OP
    sonicthemouse

    sonicthemouse Member

    Joined:
    Jan 9, 2006
    Messages:
    804
    Location:
    3207 (BH) / 3033 (AH)
    Yep, sorry, just didn't reply to everyone individually.

    Deleted all partitions from each USB stick using DISKPART.

    Not sure if I mentioned in the OP but I need both legacy and UEFI boot, so can't just copy files - I need this stick to be as universal as possible :thumbup:

    Yep, tried the Windows 7 tool with the downloaded ISO. Tool succeeds, but drive is not bootable in legacy or UEFI :(
     
  16. Myne_h

    Myne_h Member

    Joined:
    Feb 27, 2002
    Messages:
    9,210
    Did you do the clean command?
    Let's at least get one of your 3 drives working with UEFI.
    Do that, then copy to fresh partition.

    It'll take 15 mins.

    Works? Y/N?


    .

    If Y:
    Do a 2nd drive with clean command and the ms MCT tool.

    Works? Y/N?
     
    Last edited: Jun 18, 2019
  17. Bold Eagle

    Bold Eagle Member

    Joined:
    Jun 28, 2008
    Messages:
    9,378
    Location:
    Brisbane
    Capture.PNG

    If the target devices have any OS on them you can then just 'copy' the ISO onto a USB and hit that setup.exe from the USB.
     
    Last edited: Jun 18, 2019
  18. garnet

    garnet Member

    Joined:
    Nov 10, 2009
    Messages:
    361
    Location:
    3020
    try different ISO, and windows USB/DVD creator.
     
  19. OP
    OP
    sonicthemouse

    sonicthemouse Member

    Joined:
    Jan 9, 2006
    Messages:
    804
    Location:
    3207 (BH) / 3033 (AH)
    Good plan.

    1. USB 2.0 drive, in a USB 2.0 port, so no chance of any USB compatibility issues.

    2. Cleaned:

    [​IMG]

    3. Created partition, formatted FAT32, default allocation size:

    [​IMG]

    4. Downloaded a fresh copy of the ISO using MCT, home internet so no firewall, checksums:
    Size: 3967483904 bytes (3783 MB)
    CRC32: AA21948D
    CRC64: CFA66DE0FE8BF236
    So different again to the previous ones I got, and different to other members' results too :rolleyes:

    5. Mounted the ISO (double-clicked in Win 10, no additional software used) and copied contents to 'cleaned' USB.

    6. Doesn't show up under "UEFI Boot Sources", screenshot below. 'Windows Boot Manager' and 'SAMSUNG MZ...' both boot to the Windows 10 installation on my SSD.
    I know the USB is working and detected by the PC because it is listed under "Legacy Boot Sources" - 'TOSHIBA USB DRV PMAP', although it doesn't work (of course).

    [​IMG]



    :confused:


    :upset:
     
    Last edited: Jun 19, 2019
  20. Myne_h

    Myne_h Member

    Joined:
    Feb 27, 2002
    Messages:
    9,210
    So weird.

    Is there a boot or efi folder in the drive?
    With the bootx64.efi file in it?

    Gotta say, it doesn't make sense. That should be foolproof.

    Oh... wait...There is ONE case where that won't work. When the UEFI is 32bit and you've got a 64bit OS.

    Such as those fucking irritating Intel Atom *trail things
     

Share This Page

Advertisement: