6 ms·

Windows images that are over 4.3GB(I don't remember the exact max size) most image burning tools will fallback to NTFS on the USB formatting and some motherboar

by sdlion 5y ago

Windows images that are over 4.3GB(I don't remember the exact max size) most image burning tools will fallback to NTFS on the USB formatting and some motherboards/laptops don't like this. (Even on my rather modern Dell laptop) The best solution so far I've found is to manually partition the USB into a 1GB FAT32 partition and the rest NTFS. Then you extract the files where needed [0] I learned this method just last year but it seems it's pretty universal. At least for Win10 ISOs. And I don't have to boot Windows and wait for its updates! [0] https://techbit.ca/2019/02/creating-a-bootable-windows-10-uefi-usb-drive-using-linux/ https://techbit.ca/2019/02/creating-a-bootable-windows-10-ue...

pxeboot 5y ago
That seems far more complicated than just using DISM, PowerShell or wimlib (on Linux or Windows) to split the install.wim file into two parts, which I believe older versions of Rufus (or a similar utility) offered to do. https://wimlib.net/man1/wimsplit.html https://wimlib.net/man1/wimsplit.html
- jevinskie 5y ago
  Yep, wimlib is the portable magic that makes FAT32/4GB a non-issue. It is still annoying to have to use Windows to run NTLite. ;) https://evanshortiss.com/create-a-windows-install-usb-via-macos https://evanshortiss.com/create-a-windows-install-usb-via-ma...
- vxNsr 5y ago
  Or use ventoy and never worry about large files again.
Stratoscope 5y ago
I'm as big a Rufus fan as anyone, but for Windows 10 why wouldn't I just use Microsoft's boot image creator? That's what I've done lately, and it works every time with no fuss. https://www.microsoft.com/en-us/software-download/windows10 https://www.microsoft.com/en-us/software-download/windows10 Edit: I just remembered that you might not be on a Windows device, in which case you may well want to download the ISO and use Rufus to make a bootable stick from it.
- deleted 5y ago
  [deleted]
- verst 5y ago
  I have used Rufus from Macs (my primary work devices) to create bootable Windows installers on USB to reinstall my gaming PCs plenty of times :)
- chrisandchris 5y ago
  If you‘re under Windows and want any stick, use Rufus. If you‘re under Linux (or Mac) and have an Iso, use dd. At least that‘s how I do it.
  - antibuddy 5y ago
    My memory is a bit hazy, but I remember dd not working for Windows images. Did you test that recently?
    - chrisandchris 5y ago
      Some SO user mention it seems to work with dd, however I did not test that recently. Most comments seem to mention that it‘s more difficult than dd. [0] https://unix.stackexchange.com/a/598632 https://unix.stackexchange.com/a/598632
      - vetinari 5y ago
        Normally, for UEFI boot, you could be able just to create a FAT32 partition and copy the ISO content there. In the past, it was perfectly workable way to do so. Except for the unfortunate install.wim file. The first releases of Windows 10 were fine, they had it under 4GB, but some of the half-year releases have it grown over 4GB, and FAT32 cannot handle that. Thus all the mitigations you see here. The Microsoft's USB tool does not use install.wim; it contains install.esd instead. It is basically the same thing, but with different compression, so it is still a bit under 4GB. You can recompress install.wim into install.esd, if you have the inclination ...and a windows machine nearby (dism /export-image).
sascha_sl 5y ago
Rufus does in fact have a long explanation of this on their FAQ: https://github.com/pbatard/rufus/wiki/FAQ#blah-uefi-blah-fat32-therefore-rufus-should-blah https://github.com/pbatard/rufus/wiki/FAQ#blah-uefi-blah-fat... You probably left Secure Boot on. That prevents loading the NTFS UEFI driver.
- sdlion 5y ago
  I think I did that, then have problems with the windows installer. A driver prompt. I regularly have to give services to laptops, so I prefer options that "just works". This is also the reason I don't usually use the Windows installation media creator, because is slow and won't burn my several ISOs. There was a time the new Win10 iso installation process would fail on any configuration I would try... I lost somewhat around THREE DAYS trying to solve each f*"** cryptic error message and an old iso did the trick. Just a few hours updating and it was done. Sadly most of my clients won't just accept the option of installing Linux ;)
VMtest 5y ago
I used the same method as you, but from different source. I tried to dig into my documentation for the link that I saved, it doesn't seem like I saved the google search terms for it, but they can be deduced from the link anyway. 1. https://win10.guru/usb-install-media-with-larger-than-4gb-wim-file/ https://win10.guru/usb-install-media-with-larger-than-4gb-wi...

by sdlion 5y ago

pxeboot 5y ago

That seems far more complicated than just using DISM, PowerShell or wimlib (on Linux or Windows) to split the install.wim file into two parts, which I believe older versions of Rufus (or a similar utility) offered to do. https://wimlib.net/man1/wimsplit.html https://wimlib.net/man1/wimsplit.html

jevinskie 5y ago
Yep, wimlib is the portable magic that makes FAT32/4GB a non-issue. It is still annoying to have to use Windows to run NTLite. ;) https://evanshortiss.com/create-a-windows-install-usb-via-macos https://evanshortiss.com/create-a-windows-install-usb-via-ma...
vxNsr 5y ago
Or use ventoy and never worry about large files again.

Stratoscope 5y ago

I'm as big a Rufus fan as anyone, but for Windows 10 why wouldn't I just use Microsoft's boot image creator? That's what I've done lately, and it works every time with no fuss. https://www.microsoft.com/en-us/software-download/windows10 https://www.microsoft.com/en-us/software-download/windows10 Edit: I just remembered that you might not be on a Windows device, in which case you may well want to download the ISO and use Rufus to make a bootable stick from it.

deleted 5y ago
[deleted]
verst 5y ago
I have used Rufus from Macs (my primary work devices) to create bootable Windows installers on USB to reinstall my gaming PCs plenty of times :)
chrisandchris 5y ago
If you‘re under Windows and want any stick, use Rufus. If you‘re under Linux (or Mac) and have an Iso, use dd. At least that‘s how I do it.
- antibuddy 5y ago
  My memory is a bit hazy, but I remember dd not working for Windows images. Did you test that recently?
  - chrisandchris 5y ago
    Some SO user mention it seems to work with dd, however I did not test that recently. Most comments seem to mention that it‘s more difficult than dd. [0] https://unix.stackexchange.com/a/598632 https://unix.stackexchange.com/a/598632
    - vetinari 5y ago
      Normally, for UEFI boot, you could be able just to create a FAT32 partition and copy the ISO content there. In the past, it was perfectly workable way to do so. Except for the unfortunate install.wim file. The first releases of Windows 10 were fine, they had it under 4GB, but some of the half-year releases have it grown over 4GB, and FAT32 cannot handle that. Thus all the mitigations you see here. The Microsoft's USB tool does not use install.wim; it contains install.esd instead. It is basically the same thing, but with different compression, so it is still a bit under 4GB. You can recompress install.wim into install.esd, if you have the inclination ...and a windows machine nearby (dism /export-image).

sascha_sl 5y ago

Rufus does in fact have a long explanation of this on their FAQ: https://github.com/pbatard/rufus/wiki/FAQ#blah-uefi-blah-fat32-therefore-rufus-should-blah https://github.com/pbatard/rufus/wiki/FAQ#blah-uefi-blah-fat... You probably left Secure Boot on. That prevents loading the NTFS UEFI driver.

sdlion 5y ago
I think I did that, then have problems with the windows installer. A driver prompt. I regularly have to give services to laptops, so I prefer options that "just works". This is also the reason I don't usually use the Windows installation media creator, because is slow and won't burn my several ISOs. There was a time the new Win10 iso installation process would fail on any configuration I would try... I lost somewhat around THREE DAYS trying to solve each f*"** cryptic error message and an old iso did the trick. Just a few hours updating and it was done. Sadly most of my clients won't just accept the option of installing Linux ;)

VMtest 5y ago

I used the same method as you, but from different source. I tried to dig into my documentation for the link that I saved, it doesn't seem like I saved the google search terms for it, but they can be deduced from the link anyway. 1. https://win10.guru/usb-install-media-with-larger-than-4gb-wim-file/ https://win10.guru/usb-install-media-with-larger-than-4gb-wi...