Here you can download WinSetupFromUSB and updates of the tools included.
Please do not hotlink files, use this page if you want to post a link to the program. If you need to link to a specific version, you could use version number like this:
http://www.winsetupfromusb.com/downloads/#1-10
Note: A few antivirus programs keep detecting a couple of the included files as viruses. This is false positive. These vendors were informed numerous times and the serious companies such as DrWeb and Kaspersky, update their signatures to remove the false detection within a few hours after being informed. Others, such as McAfee, despite all the efforts and contacts, don’t do anything to update their signatures. For a few unknown ones, which use third party signatures, there is no way to contact them or they simply don’t respond. This program will never knowingly distribute any kind of malware.
WinSetupFromUSB 1.10.exe (28 MB ; 1102773 downloads)
- Windows 11 support
- added detection of higher Windows 10 build numbers for the boot menu names
- Removed file spit infobox if ISO file needs to be split
- Increased warning for large disks selection to > 64 GB
- minor bug fixes
WinSetupFromUSB 1.9.exe (28 MB ; 2708621 downloads)
- added support for multi-version/dual Windows ISOs (32 and 64 bits in one ISO for example). Stock Microsoft dual ISOs are supported and tested, other such sources too, as long as they use unmodified bootmgr and default location for BCD store is in /boot/bcd. Tested in BIOS/UEFI with both Secure Boot on and off, stock Windows 10 dual and single ISO builds 1803, 1809, Server 2016 and 2019.
- added detection of Windows 10 build number which is added to the boot menu names
- updated ImDisk and WimLib
- minor bug fixes
WinSetupFromUSB 1.8.exe (24 MB ; 2761057 downloads)
- fixed issue with Windows 10 and recovery option not shown
- fixed issue with persistence file size not set correctly and tooltip for using persistence
- updated some the tools to their latest version- BootIce, ImDisk, WimLib
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.7.exe (24 MB ; 1538448 downloads)
- disabled superfloppy check due to issues with latest Windows 10 builds
- increased input timeouts to 45 seconds
- fixed issue with Swedish locale and bcdedit
- added check if imdisk is an old version
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.6.exe (24 MB ; 1177005 downloads)
- updated imdisk package for compatibility with latest Windows 10 versions
- Added Windows 10 in all GUI elements
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
2) If program is run on latest Windows 10 builds, seconds source can no longer be added due to incorrectly detected superfloppy format of the USB disk. This is due to changed by Microsoft WMI call results or structure. Fix is being worked on and will be released as soon as it’s ready.
WinSetupFromUSB 1.6-beta2.exe (24 MB ; 407275 downloads)
- Fixed missing EFI boot menu for Windows 10 sources
Note: Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.6-beta1.exe (24 MB ; 225421 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 64711 downloads)
- Added support for Windows Vista/7/8 and above sources larger than 4 GB and FAT32 for EFI compatibility- credits. In other words, now is possible to use FAT32 formatted USB drive and add larger than 4 GB source, say Windows 10, to be able to boot in EFI mode. As this is new feature not yet fully tested, the first version is released as a beta. Any feedback is appreciated.
WinSetupFromUSB 1.5.exe (23 MB ; 345113 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 73754 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1969032 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 560508 downloads)
- added better handling of illegal characters for Linux/Other ISO source file name
- added advanced option for adding persistence partition for Linux sources. Each source has its own persistence space associated with it
- added better handling for Kon-Boot, source is to be added as ISO file using the Linux/Other ISO option
- added advanced option to add custom folder with boot critical drivers for NT6 sources (Vista and later). These drivers are added in boot.wim and loaded with DrvLoad before start of Setup, scratch space is increased accordingly. Only drivers for present devices will be loaded. Use it to add USB, SATA/SCSI or Chipset/USB drivers for example. Loaded drivers will be staged and available to the OS being installed. For non boot-critical drivers (Lan, WLan, Video etc.), have a look here
- added internal check for NT6 sources with multiple boot.wim, only default osloader entry in BCD store and the corresponding boot.wim will be added
- fixed errors when USB disk was initially prepared with the auto-format option, and on next run of the program it may complain about missing MBR and partition table
WinSetupFromUSB 1.3.exe (22 MB ; 1610613 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 314609 downloads)
- Fixed bug when adding NT6 source with missing new line feeds in WinPEshl.ini
- Fixed handling of NT6 sources with install.esd
- Fixed bug with NT6 sources with EFI directory but no BCD file in it
- Added Ei.cfg and CVersion.ini Removal Utilities in \tools\winisoutils directory should one needs those files removed from the NT6 source ISO file
- WimLib updated to version 1.6.0 for compatibility with new WIM formats
WinSetupFromUSB 1.2.exe (22 MB ; 303691 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 77898 downloads)
- Fixed bug where program running on Windows localized in other than English language would not add NT6 source
- Improved handling when program is placed and run from directories which contain special characters- `~@#$%^&()-+=,; Single quote – ‘ is not supported in program directory path and there is a check for that
- Added an advanced option for NT6 (Vista and later) sources to add Q-Dir File Explorer, which starts before Setup. This is useful to quickly browse disk contents and backup and restore files before launching Setup, rather than booting first in another OS to perform the same task. When Q-Dir is closed, Setup starts.
- BootIce updated to version 1.3.2.1
WinSetupFromUSB 1.1.exe (22 MB ; 221743 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 44827 downloads)
- (U)EFI support for Windows Vista x64 SP1 and later 64 bits Windows. USB disk must be formatted in FAT32 as per EFI specifications to boot under EFI. To prepare USB disk running the program under Windows XP or 2003, which do not include bcdedit.exe, an active internet connection must be present in order to download it
- default auto-format file system has been changed to FAT32 for EFI compatibility
- Firadisk driver is now added to each XP 32 bits source, but disabled by default. A new option in DPMS and custom F6 floppy menus activates it. This should help loading SATA/AHCI/RAID drivers from virtual floppy on problematic machines
- NT6 sources boot menus are now handled by BOOTMGR
- fixed recognition of Windows 8.1 sources which contain INSTALL.ESD instead of INSTALL.WIM
- added check in boot menu for Linux sources to warn if PLoP is loaded. Linux sources would not work with PLoP loaded as it supports only read mode
- removed the ZIP archive as it seems some users tend to launch the program directly from the Windows zip folder view, rather than extracting all files and folders. A self extracting SFX archive is added instead
- updated wimlib to 1.5.3 which would also fix the issues with the first 1.0 versions (downloaded before 14.Nov.2013) and NT6 sources
- various small bug fixes
WinSetupFromUSB 1.0.zip (37 MB ; 758472 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 75000 downloads)
Windows Vista and above Setup/PE may not start, command prompt may appear saying :
“A winpesh.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name.”
or simply restarts. Please refer to this post for details and fix, or re-download the program if you downloaded it before 14.Nov.2013.
- custom boot menu name when Linux/Other ISO is added
- when XP/2003/2000 source is added and incorrectly the i386 folder is pointed as source directory, program uses its parent directory
- other small fixes and improvements
WinSetupFromUSB 1.0RC4.zip (37 MB ; 53535 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 43831 downloads)
- Ability to add multiple Windows Vista, 7, 8, Server 2008/2012 sources from ISO file. Use the same option to add PE2 (Vista/Server 2008) and above based utility. Thanks to synchronicity for his amazing wimlib project
- Ability to add almost any Linux based ISO which uses hybrid cd-rom/hard disk mode, credits to cdob . Refer to this page for a non exhaustive list of tested ISOs
- Auto-format option when used with NTFS would do its best when formatting the disk, to avoid fragmented large files on this volume later on by moving $MFT at the beginning of the partition. This way $MFT zone remains at the beginning of the volume and there should be way more contiguous space available large files to occupy
- DPMS updated to DPMS2, thanks to Steve
- the command prompt window during GUI mode of XP/2000/2003 setup is now hidden, thanks to cdob. It’s needed to keep the USB drive mounted throughout the GUI mode of setup
- added ability to copy all log files to the relevant WINSETUP sub-folder during PE phase of NT6 (Vista and later) boot. Create an empty file debugme with no extension in the relevant sub-directory, e.g \WINSETUP\Win7x64\debugme, and all log files from the start of PE phase will be copied next to it
- Updates of the tools included and various bug fixes
WinSetupFromUSB 1.0 beta8.zip (31 MB ; 74239 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19596 downloads)
- added an option for Auto-format, using FBinst internally. This will delete all partitions and create a single one on the target USB disk, use with care
- added an option for Auto-detect and use SATA/RAID/SCSI F6 drivers during XP/2003/2000 Setup thanks to DPMS by Chenall. The boot entry is optional and has to be selected once before booting First part of Setup
- added an option to include a floppy image with F6 SATA/RAID/SCSI drivers during XP/2003/2000 Setup. The boot entry is optional and has to be selected once before booting First part of Setup
- working USB to USB install thanks to WaitBT driver by Shao Miller
- added an option for creating a “kicker” ISO for Vista/7/8/Server 2008 Setup, thus avoiding possible setup failures
- added another debug option for Vista/7/8/Server 2008 Setup, shifting hard disk possitions, thus avoiding possible other setup failures
- added an option for custom folder name and boot menu entry for XP/2003/2000 Setup
- added an option for adding and using custom NTDETECT.COM in order to avoid possible BSOD 0x0000007B on some machines
- fixed partial GUI freezes during large file copy, e.g. install.wim
- fixed bug where changes occur in the small ISO for XP/2003/2000 Setup leading to errors at start of Text mode
- added USB monitor function to refresh list if USB disks when disk is connected or disconnected
- updated versions of the included programs and tools, QEMU should now support booting Vista/7/Server 2008 x64 versions too
- various bug fixes and improvements
WinSetupFromUSB 1.0 beta7.7z (7 MB ; 33508 downloads)
- fixed issues on some new systems when XP/2000/2003 Setup hangs during text mode:
http://www.msfn.org/…all-iso-method/ - fixed grub4dos menu.lst entries when detecting the number of hard drives connected
- fixed custom boot menu titles input box when adding multiple similar XP/2000/2003 sources
- grub4dos, included tools and programs updated
- fixed issue with incorrectly detecting if source is Windows 2000
- flushing USB disk write cache is now performed internally, rather than using external programs
WinSetupFromUSB 1.0 beta6.7z (4 MB ; 41372 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 5866 downloads)
- added option to display all connected disks in case one needs to prepare eSATA etc. drives.
- improved detection of USB disks at start of GUI mode in case of 2000/XP/2003 setup
- added support for adding Ubuntu/Kubuntu/Xubuntu ISOs
- added option for shared BTS OEM folder if several sources need to share same OEM folder. Use tooltip for info.
- experimental option to prepare source to be installed on USB, to be tested further.
- better handling in case 2000/XP/2003 install is on machine with 2 or more internal disks
- at start of GUI mode, after own setup.exe and setup.cmd are finished, setup.exe from th e source is executed, no matter another fake or the original one. Thus BTS presetup.cmd for example is executed by its fake setup.exe.
- added option not to check for and install grub4dos MBR. One would have to take care of chainloading grldr by other means.
- updated many of the included programs
WinSetupFromUSB 1.0 beta4.7z (4 MB ; 11809 downloads)
- fixed issue with non-English versions of Windows XP/2003
- fixed bug when program directory is on the same USB disk and partition which is being prepared
- removed dependencies on Windows Scripting Host, in case it’s broken.
- BootIce, Grub4Dos, SysLinux, RMPrepUSB updated to the latest versions
WinSetupFromUSB 0.2.3.exe (4 MB ; 109547 downloads)
Здравствуйте, в новой версии программы не нахожу кнопку Perform Format. Подскажите пожалуйста, где она есть?
There are no such changes compared to the previous versions and there has never been such button as far as I recall.
Can you send a screenshot?
Wersion 1.0 beta 6 – bootice/perform format
Well, that’s BootIce, completely separate program, likely interface has changed when some of the new versions was added.
Will a new version be issued?
Hi,
I am trying to boot in uefi with Windows 10 32 bit. But it’s not happening. 64bit working in both uefi and non-uefi. But 32bit working only in non-uefi, not in uefi. Please suggest.
Are you 100% sure your PC supports 32 bit UEFI and why would you even need to boot 32 bit Windows nowadays?
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh824898(v=win.10)?redirectedfrom=MSDN
Quote:
Note
While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC.
“…why would you even need to boot 32 bit Windows nowadays?”
1) In order to run 16-bit programs that won’t run under 64-bit Windoze, without having to run them in a virtual machine.
2) To cut disk storage and backup media requirements in half.
3) many other valid reasons.
Do you buy supported hardware for this, or do you just use BIOS mode?
I don’t understand your question. You asked “why would you even need to boot 32-bit Windows nowadays”. I gave several reasons. Obviously, the hardware must support 32-bit Windoze, and the manufacturer must providing drivers for 32-bit windoze. Why wouldn’t we use BIOS mode? What advantage does UEFI provide other than to complicate everything?
Easy, I am not arguing, just asking out of curiosity. You listed number of reasons and I was curious how far you go when considering 32 bit support, that’s all
When i use this software in 64bit windows for make bootable xp.my usb is goes to in write protect.and now usb is not format
The USB stick is faulty and it’s just coincidence, could have happened when copying files or any other write operation on it by any software.
Hi , Thanks for your program, my question is can i set up a combine of windows 7 , 8 , 10 on the same flash-USB ?
Sure, as many as you want. Any of the supported sources can be added multiple times.
A few weeks ago, I erroneously said that WinSetup wasn’t giving me enough time to enter the boot menu title that I wanted to enter (and that I had to use Bootice afterward to accomplish this). I was confusing the problem with previous versions (before you increased the timeout to 45 seconds), and the current problem, which is: although there is plenty of space remaining in the input field, it won’t let me enter more than 35 characters. For example, if I want to enter “Install Windows 10-1909 Build 18363 (64-bit)”, it only lets me enter “Install Windows 10-1909 Build 18363”. So I want to change my request from increasing the timeout, to increasing the title field size. 🙂
No worries, how many characters do you think will do it? Please bear in mind bootmgr and grub4dos need to be happy with the length, although I don’t recall seeing a limitation, but surely there must be some.
Trying to remember why I put 35 in first place, but can’t, hope I find some notes in the code.
I need 44 characters for my title structure, so I would be happy with 44. 🙂 But others may need/want more. I can’t find limitations for bootmgr and/or grub4dos, but I suspect it is 255 (the same as for a Windoze file name).
In the old days, we used 35 for CITY fields (name and address fields were 40).
good
Generate with WinSetupFromUsb 1.9 on a 16 GB flash drive a Windows 7 and Windows 10 installer.
But when wanting to install those OS, it starts without problems, then it starts informing me to connect the USB without being able to continue with the installation. The USB is still in the same port.
Could you inform me that I am not doing well or that I am lacking in the generation of the pendrive?
Thank you
At that point try to unplug the USB disk and plug it back in.
Also try booting from another USB port, preferably USB2 one if you have.
If that doesn’t work, try adding the appropriate USB3/chipset drivers in the source and rebuild the USB disk.
Does that happen with both Windows 7 and 10?
The issue is that windows installer doesn’t see the USB drive after anymore, usually lack of USB drivers.
I created bootable usb using WinSetupFromUSB and added two linux iso. The usb was left with 4GB free space and decide to add another iso with size 2.5GB. I started WinSetupFromUSB and when it finished copying the iso file i get message that it can’t defragment the iso file and i have to free space on the usb drive. How much free space it needs? It has already 1.5GB free space.
It’s about how much contiguous space is available, not total free space remaining.
Please take a look at this comment and below:
http://www.winsetupfromusb.com/faq/comment-page-27/#comment-3652
Another good read:
http://m.easy2boot.com/not-contiguous-error/
Before adding the third iso file i run WinContig on the usb drive and it didn’t show any fragmentation. Why this contiguous space error in the end then? Is the iso file fragmented itself?
What makes you think the remaining free space was contiguous?
A file can’t be fragmented by itself, it only gets fragmented when the operating system file system drivers put it somewhere, and we have no control over the process. Best we can do is to first defragment the free space before copying the file, thus decreasing the chances to become fragmented and second, to try to defragment after copying.
I run WinContig on the usb drive and it defragmented it. Now it shows 0 fragmented files, but shows one error for the iso file: “The volume does not have a group of contiguous, free clusters that is large enough to contain the entire file.” How it can show zero fragmented files and shows error in the same time?
Maybe that file is in another category? No idea.
Try defraggler too.
I tried defraggler and it found fragmentation on the usb drive. Running defragmantaion already one hour. That is nonsense. If i try easy2boot will a get the same contiguous space error? Is WinSetupFromUSB work in the same way as easy2boot? I have used other multiboot usb creators like YUMI and i didn’t get any contiguous space errors, even if the usb drive gets full with iso’s, but YUMI is not very reliable, some iso files didn’t boot.
Easy2boot uses same method unless something changed recently, so yes, files must be defragmented.
This method allows booting nearly if not all recent Linux distros without any modifications on the source.
Best way of overcoming such issues is simply to use large USB stick, 32 and 64 GB are nowadays cheap enough and give plenty of space for reasonable amount of all kind of sources.