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 ; 1228364 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 ; 2743119 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 ; 2766782 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 ; 1542356 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 ; 1178910 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 ; 407760 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 ; 226001 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 65036 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 ; 346696 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 74129 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1970931 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 561132 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 ; 1611429 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 315182 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 ; 304392 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 78202 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 ; 223659 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 45270 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 ; 760261 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 75582 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 ; 53938 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 44090 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 ; 74532 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19869 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 ; 33897 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 ; 41955 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 6064 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 ; 12071 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 ; 110548 downloads)
Thanks! Love the app, but you should look into Let’s Encrypt for some SSL on this site. 😉 Especially since you have a form asking for emails, names or logins. SSL also makes it harder for someone to spoof the download link.
It’s a lot more involved than setting up Let’s Encrypt, hence this is still on the overdue to-do list.
Thank you very much, you make multiboot easy for me, I ama really gratefull.
Такая вот проблема, помогите, пожалуйста…
USB аккумулирует 32 ГБ в WinSetupFromUSB Ставлю пункт Автоматическое форматирование с помощью FBinst, в формате FAT32 и добавляю образы по очереди, все как обычно. Но установка с версией Win10 2004 19041.264 и все возможные сборки новые значения до 21H2 X64 не планируются на доступ к UEFI и MBR выдают ошибку Не удалось смонтировать виртуальный диск. Невозможно продолжить, нажмите OK для перезагрузки.
Образы X86 загружаются без проблем на любые устройства с UEFI и MBR
Have you tried starting fresh with new download of the program, in a new folder ( that’s to avoid conficts with any previous versions) and using stock Microsoft sources only?
Пробовал, тогда ошибки нету, но меня такой вариант не устраивает, мне нужно что бы в одном ISO образе были все редакции WIN10. HOME PRO LTSC и так далее.
Пробовал записывать ISO образы Win10_x64bit по очереди по одному, но в каждом из мною перечисленных ниже (4) ISO образов упакованы все редакции WIN10.
1) 20H2 (19042.685) выдает ошибку
2) 21H1 (19043.1110) выдает ошибку
3) 21H2 (19044.1466) выдает ошибку
4) 2004 (19041.508) ВСЕ OK ошибок нет, но этот ISO образ и более старый и занимает менее 4ГБ, а мною выше перечисленные (3) разных ISO образа занимают более 4ГБ и выдают одну и ту же ошибку после записи и только ISO Win10_x64bit в FAT32. В NTFS работают все (4) разных образа ISO как по очереди так и вместе. Но мне вариант в NTFS не подходит.
Заметил одну особенность что ISO образы размером более 4ГБ именно в формате записи FAT32 выдают эту же ошибку, а ISO образы которые я перечислил выше (1) (2) (3) имеют размер меньше 4ГБ
В следствии чего WinSetupFromUSB 1.10. видит что в FAT32 уместить ISO образ боле 4ГБ невозможно. По этому программа автоматически пережимает ISO образ в Архив winRAR, а так же разбивает этот ISO образ на 2 части + WIM. И того получается:
В папки WINSETUP есть папка W10_x64 и в этой папке есть еще папка sources>boot.wim, выходим назад в корень папки W10_x64 и в ней видим w_10_21Н2_x64_13.01.2022.iso.001(3,99 ГБ) and w_10_21Н2_x64_13.01.2022.iso.002(366 МБ) при чем что (( w_10_21Н2_x64_13.01.2022.iso.001(3,99 ГБ) это и есть тот самый winRAR)) а ((w_10_21Н2_x64_13.01.2022.iso.002 этот файл вообще неизвестного формата))
Мне очень сложно объяснять из-за неточности перевода. Я могу записать видео и дать вам ссылку, что бы вы посмотрели можно так сделать?
A bit confused because of translation.
Are you saying program is putting all these sources in win10_x64, instead of their own folder, which leads to messed up ISO files? If that’s bthe case, you can try using the advanced option for custom Windows folder and boot manu names and force them in separate folders, could be a bug introduced recently.
Splitting is not using winrar or anything, file is just cut in parts before the 4 GB boundary, that’s all, there is no a single byte added to the original file and this should not be a problem.
You can upload somewhere the program log files for me to review, FAQ #14:
http://www.winsetupfromusb.com/faq/
Я подготовил информацию, посмотрите пожалуйста.
https://youtu.be/4FvLPXUvp-A
https://drive.google.com/file/d/1DEcHKqGadIcjVRia-ark8ZNNMdZgK75O/view?usp=sharing
Is the H in ISO file name in Cyrillic?
w_10_21Н2_x64_str_13.01.2022.iso
Replace all Cyrillic charachers with latin ones in these ISO files, and all the sources in a path with latin characters only, then try again.
From the log:
…
[LaunchApps]
%systemdrive%\windows\WinPreSetup.exe, “/mountiso=WINSETUP\W10_x64_2004\w_10_21═2_x64_str_13.01.2022.iso.001”
Note the odd character after _10_21, that’s why this particular source is failing to start, likely the other ISOs have same issue, got no time to check all logs and away from computer.
Leave ISO splitting alone, it has nothing to do with the issue.
Спасибо вам огромное за помощь, проблема была в названии ISO образа ,буква “H” была виновна в ошибке.
Я очень долго ломал бы себе голову если бы вы мне не ответили, но вы все же ответили мне, и проблема решена!
Программирование это не мое, я очень плохо разбираюсь в чтении лог файлов, спасибо вам за помощь
No worries, that was a good exercise with well hidden offender 🙂
Las ISO en el boot menú , aparecen dobles
http://www.winsetupfromusb.com/faq/#faq16
Is this software support both uefi and Legacy?
http://www.winsetupfromusb.com/faq/#faq9
سپاس گزارم از برنامه بسیار مفید با کارآیی عالی در سطحی به این بالایی . وفعا عالی بود و کمال تشکر را درام از زحمات شما…. امیدوارم همواره سلامت و پایدار باشید.
did any one can create multiboot support efi because when i format usb drive it’s only work legacy boot, So how create multiboot work with efi boot
EFI boot is supported for Windows sources
Actually if you want to boot in uefi mode, you can boot only x64 Bit windows or you have to download dual boot os
Is it will work dell vostro 3681 desktop
Unfortunately, this program has limited functionality and a lot of bugs. To date, the most urgent question of functionality is to make the USB flash drive bootable and simply sketch ISO images into it. For stability, this function is performed by two programs – Easy2Boot and Vento. Easy2Boot is in the first place, as it has been developed for a long time and with high quality.
Thanks for the feedback.
Would you mind sharing what these lots of bugs are?
this is a very easy use, faster than other usb boot.
multi windows boot able tool.
When will we see support for ChromeOS Flex, and perhaps Windows 11 support, without the need for TPM and Microsoft account, like Rufus…
With Rufus, you can only fit 1 OS, but imagine the capability of your multiboot USB if you can have Rufus functionality as well..
Cheers…