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:
https://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 ; 1249931 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 ; 2746689 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 ; 2767238 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 ; 1542735 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 ; 1179147 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 ; 407818 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 ; 226081 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 65091 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 ; 346872 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 74164 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1971161 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 561184 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 ; 1611511 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 315246 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 ; 304462 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 78224 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 ; 223874 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 45328 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 ; 760478 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 75680 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 ; 54002 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 44127 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 ; 74582 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19911 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 ; 33951 downloads)
- fixed issues on some new systems when XP/2000/2003 Setup hangs during text mode:
https://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 ; 42032 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 6090 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 ; 12117 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 ; 110691 downloads)
Esta ferramente sinceramente é a melhor não tem pra minguem quem falar que tem um tal de AB Multiboot que é melhor não intende de nada ferramenta gratuita onda todos podem baixar sem nenhum custo, e sem pegadinha de esconder senha para fazer o pessoal de trocha esse é o melhor e pronto
Thank you
For two linux distros WinSetupFromUSB get stuck on defragmenting and i had for force close it. The first was Kubuntu 20 and the second was Fedora KDE 32. I don’t know why.
Likely WinContig was still defragmenting in the background. Either let it run, or if that’s taking too long use faster USB stick with faster write access for small files, that’s where the main difference is between good and bad quality sticks.
Alternatively, can avoid fragmentation altogether by putting largest ISO files first, before any other sources and use large enough USB disk which will more likely have enough contiguous free space.
I let let it run long enough. I am using WinSetupFromUSB often so i know what time it usually take to defragment. This was not normal.
Nothing much I can say, WinContig is used internally to defragment. Either avoid fragmentation altogether, or run WinContig manually and see if it gets stuck.
If you were using same stick many times, it might have developed faulty sectors and WinContig might be getting stuck when accessing some of them, hard to know untill you rule out faulty stick by using another, confirmed good and quick one.
What will be the negative effects if i don’t defragment?
Linux ISOs won’t be able to boot
1.9 не скачивается
Gostaria de saber porque as partições do windows 10 v2004 fica fora de ordem
Hi, thanks for your tool, it’s been really useful for years. I’m trying to create an USB with Windows 10 20H2 ISOs but it’s not working. Do we have to wait for an update?
What’s exactly the issue?
LoLo, I downloaded Windows 10-20H2 from https://www.microsoft.com/en-us/software-download/windows10ISO (using Windows XP or Linux so we get the iso, not the “media creation tool”.) Then I used WinSetUpFromUSB to add it to the USB drive. It works fine. Just boot from the USB, select “Windows 7/8/10…” from the menu, and then select the menu name specified when you ran WinSetUpFromUSB.
(If you downloaded the iso from another source, it may be defective. And, if you downloaded the “media creation tool”, you can’t use that file with WinSetUpFromUSB, but you can use it to create a bootable USB with W10 on it, as an alternative to WinSetUp.)
Hello, is it possible if i can flash older versions of Windows below Windows XP like Win2K, Win98, Win95?
i only asked this question to ensure if this program will do so because other flash tools like rufus when its successful, and when i boot the flash setup on my older pc, it bluescreens.
Windows 2000 should be supported, but I haven’t tested it for ages, you can give it a try.
Windows 95/98- no, unless added as Linux/Other ISO and grub4dos entries manually changed to load Windows 95/98. What exactly needs to be changed I don’t remember, google probably can help if you search for grub4dos windows 98
ok, thanks! i will give Windows 2000 a try. since i couldn’t find any tutorials of how i can flash Windows 95, 98 on USB.
Bear in mind you need to be testing on hardware or VM supported by Windows 2000, which could be challenge to find nowadays.
Thanks again for including the “Test in QEMU” feature, i managed to discover the cause of the BSoD.
i tested Windows 2000 using the feature and it worked, but when i tested it on REAL hardware this time, it suddenly showed a blue screen of death with the stop code:
INACCESSIBLE_BOOT_DEVICE.
do i need to format the drive to FAT?
because i formatted it to NTFS when it partitioned for the setup to be imported.
i’m trying to install Windows 2000 on my old PC that supports windows up to 8.1. i use it for experimenting and studying OSes.
Inaccessible boot device is usually SATA/AHCI drivers, Windows doesn’t have the needed driver to continue the boot process and loses connectivity to the disk.
Try switching disk mode to IDE/compatible.
Alternatively, if you can find SATA/AHCI driver for Windows 2000, either rebuild the source using the advanced option to provide F6 drivers, or just integrate it in the source and rebuild the disk.
FAT32 should be slightly faster on Windows 2000 setup, NTFS is faster on XP.
Both should work just fine.
Test I’ve done some time ago:
https://msfn.org/board/topic/125116-fat16-vs-fat32-vs-ntfs-speed-on-usb-stick/
okay! thank you for the help and guide, maybe the problem might be solved if i try and download a new copy of the Windows 2000 setup. otherwise, i do have a pre-existing Windows on my old PC, maybe i can boot it up and find drivers for SATA AHCI HDDs. i’m using a Biostar N68S Motherboard which has an AMD Sempron 145 Processor.
my pc dump after select os imege end go button press
ihave change ram,hdd,windows reinstall but same probme press go and after dump my pc help me plezz
use window 10
Awsome!
I can’t boot & add WinPE 10&8_Sergei_Strelec x86_x64_2021.01.05 latest version 2021. Please help me..?
Or please code in menu.lis add WinPE 10&8_Sergei_Strelec x86_x64_2021.01.05 latest version 2021 show programs in winPE ?
This program is worthless. I tried it and it would NOT make a bootable usb and gave NO excuse as to why it refused to do anything!
other than possibly formatting the usb to ntfs though i don’t know if it even did that correctly. It made 6 files and put on there for some reason none of which had anything to do with the .iso file i set it to use to make a bootable usb.
I had no antivirus programs running so NO excuse.
What source have you added and what exactly happened after you pressed GO button?
Log files would greatly help, as per FAQ #14.
And please, take it easy.