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 ; 975062 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 ; 2681330 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 ; 2756684 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 ; 1536701 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 ; 1175647 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 ; 406914 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 ; 224978 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 64466 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 ; 344359 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 73450 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1966824 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 559950 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 ; 1609943 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 314219 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 ; 303280 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 77569 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 ; 220567 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 44529 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 ; 756989 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 74628 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 ; 53234 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 43683 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 ; 74039 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19451 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 ; 33212 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 ; 40756 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 5734 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 ; 11658 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 ; 108756 downloads)
Trying to get Linux Distros onto an older PC, sadly has no native USB boot support, was wanting to get a CD that could mount the USB and switch over to it, so a regular boot from the USB would be possible. The machine is a laptop with a CD drive (not DVD), so the distros I want to try on it, are too large to even get onto it (but are spec okay to run on it). I’m trying to Live run the Distros to see if I am going to run into any issues with them, but because the bios says nothing about USB booting, I can’t even do that, the previous Distro I tried to install, the Live worked, but the install failed (but that required burning a CD, which is now a coaster).
Try Plop on a CD to boot from USB:
https://www.plop.at/en/bootmanager/plpbt.bin.html#runcd
Can also try latest grun4dos with USB driver on a CD:
https://www.rmprepusb.com/tutorials/grub4dos#TOC-Slow-or-no-USB-booting-on-some-systems-
Hello and good evening itaushanov My name is Mauricio. I would like to congratulate you for your software, with the help of it was that I got as close to reaching my goal!
I am a computer technician and I am urgently in need of putting all my bottable software on a pen drive or external HDD. With the help of a youtuber from my country that is Brazil, I got close to what I wanted, which is the following in my 32 GB pen drive put all my Windows 7 Ultimate 32bits, another 64bits, Windows 8.1 32 and 64 Separated and Windows 10 32 and 64 all separated I do not have nor work more with Windows AiO. The second pen drive I made with antivirus and tools like: Hirens Boot, Ultimate Boot, Kaspersky Rescue Disk etc. Worked perfectly.
But the first pen drive in which I put Windows gave the following error:
*Could not mount the virtual disk.
*Cannot continue, press OK’ to reboot.
Here is the tutorial I followed below:
Parte 1 (https://www.youtube.com/watch?v=Ax5fw1042tA)
Parte 2 (https://www.youtube.com/watch?v=QZenh4JO6SA)
I use the latest version 1.8!
Which source is giving that? Is it one or all? Can you share the logs? Details are in the FAQ page.
https://youtu.be/lwVEXBULjfA
thank’s alot
after installing windows xp computer wont boot without the same USB that i used to install and i don’t like it
What exactly happens when it does not start? Any messages on the screen? Do you have a file boot.ini, ntldr and ntdetect.com in c:\ ? Need to enable show hidden and system files in explorer. If there is boot.ini, what are its contents?
这个最新的工具，不能够自定义写入系统的名称么？
?
这个最新的工具，不能够自定义写入系统的名称么？is Chinese. It means “This latest tool, can not customize the name of the write system?” I have no idea what THAT means, though.
I got that far too, although Google translate is also available to the person asking the question…
可以啊,下面不是有adv……..opt..的选项么..然后分系统类型,可以自定义菜单名称.和文件夹的名称.
I think it’s a good tool.Thanks!
https://youtu.be/lwVEXBULjfA
latest laptop are not boot with win 7
Stock Windows 7 does not support USB 3.0 which is used in modern laprops.
You either need to integrate the required drivers in the source, or try the advanced program option to load these, or fall back to USB 2.0 by using such disk, or by changing BIOS settings if there are any, or by using USB 2.0 port if any.
Got lots of options here…
Жалько нема української мови
http://www.winsetupfromusb.com/files/download-info/winsetupfromusb-1-7-exe/
Problem with creating bootable USB with STANDARD M$’s iso – Win10_ME_16299.15 (v.1709)_x64 by WinSetupFromUSB 1.8, but the 6-year old version 1.0b8 do this job perfectly !!!
Pls. fix a.m. problem with new version.
Thanks in advance.
What problem?
The old beta8 dumps source on the USB as is and doesn’t support multiple sources of this type. Supporting multiple sources is where the tricky part is, besides the changes MS are doing with every other build…
The problem is the following – when I create bootable USB with a.m. the latest M$ ISO (which has several OS editions in one ISO):
I have a window with mistake : “Could not mount img file” (something like that) and it is not possible to go thru. So pls. check this issue and fi[ it asap.
2B honest – I prepared 2nd Bootable USB using WSFU-1.8 with Win10_ME_16299.15 (v.1709)_x64 on another flesh drive. Installing OS was OK (Tested on Virtual Box). Sorry for false alarm…
—
I have the request: – is it possible to renew v.1.0b8 for Dual ISOs (x32 and x64 in a single ISO) to the latest versions of programs unit ?
Was just downloading that Win 10 to play with it 🙂
Not sure what you mean by programs unit, probably lost in translation.
1.0b8 should support any source, unless crazy modified, but only one of this type. More sources can only be added with the later versions.
“Not sure what you mean by programs unit”
I mean programs\tools which are placed in “files” folder of WSFU-1.0b8. All of them are about 6 years old…
See the picture: https://yadi.sk/i/cVQUj-o03PCSFV
—
There are only few utils for creating Bootable USB, which could work with Dual ISOs properly. I know the 3 ones:
1) WSFU-1.0b8
2) Easy2Boot
3) AIO_Boot_Extractor
The last 2 utils are currently improving and upgrading, and I will be very obliged you if you upgrade your utility (WSFU-1.0b8) also.
kind regards,
Dmitry
I have no plans to update further the old versions- they were already updated.
As for dual ISOs- USB memory/disks are nowadays cheap and large enough so that one could afford the space to put 2 single ISOs instead of 1 dual.
You are right and wrong in the same time !
The main idea is to use real AIO (all-in-one) iso on bootable flash: 2languages+(for platforms x86+x64)+all-editions of OS.
For example Windows 10 (v1703) RUS-ENG x86-x64 -20in1 (AIO ISO – 4,23 Gb only !!!) contain
10 russian and 10 english versions 32bit(x86) and 64bit(x64):
– Windows 10 Enterprise x64 Russian
– Windows 10 Enterprise x64 English
– Windows 10 Enterprise x86 Russian
– Windows 10 Enterprise x86 English
– Windows 10 Education x64 Russian
– Windows 10 Education x64 English
– Windows 10 Education x86 Russian
– Windows 10 Education x86 English
– Windows 10 Professional x64 Russian
– Windows 10 Professional x64 English
– Windows 10 Professional x86 Russian
– Windows 10 Professional x86 English
– Windows 10 Home x64 Russian
– Windows 10 Home x64 English
– Windows 10 Home x86 Russian
– Windows 10 Home x86 English
– Windows 10 Home Single Language x64 Russian
– Windows 10 Home Single Language x64 English
– Windows 10 Home Single Language x86 Russian
– Windows 10 Home Single Language x86 English
In case you try to substitute this AIO iso with assortment of single ISOs you have to use several usb drives with total capacity ~70 Gb !!!
One can fit all these Eng x64 for example in single iso with single boot.wim, no need to have single ISO for each type…
Another such ISO could be for all RU x64 if they can’t be added to the EN one. In total you will end up with just a few ISOs like 12-15 GB.
If you do need so many sources, that implies you can afford to dedicate one 64 GB stick and get all your stuff on it.
Probably you don’t understand the HUGE complexity in supporting multiple sources, expecially heavily customised ones, where rarely anyone follows any standards or naming conventions.
It may look to you like just add support for this, but in reality this is like rewriting everything from a scratch, just to find out 1 month later, that yet another heavily customised ISO doesn’t work, and fixing it breaks other stuff…and that’s after several months work.
Sorry, I don’t have the spare time to spend on all this. It’s in my plans from long time, but I doubt I will find any soon the needed time to work on it.