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 ; 1229955 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 ; 2743381 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 ; 2766813 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 ; 1542390 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 ; 1178926 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 ; 407766 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 ; 226006 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 65039 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 ; 346719 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 74131 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1970945 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 561133 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 ; 1611433 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 315184 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 ; 304399 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 78204 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 ; 223672 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 45272 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 ; 760275 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 75587 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 ; 53944 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 44094 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 ; 74533 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19870 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 ; 33901 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 ; 41959 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 6068 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 ; 12073 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 ; 110560 downloads)
It’s better format the USB with FAT32 or NTFS file system?
NTFS is better for XP/2003 installs and support for > 4gb files, but not for boot in UEFI mose, unless a driver is used. FAT32 is for UEFI boot .
It all depends what sources you have and where are you booting them – BIOS/legacy or UEFI.
Tested using an over 5GB ISO file of Windows 8.1 64bit. Stuck during Windows 8 Metro logo (v1.6 Beta 1).
So source ISOs that are over 4GB and contain “install.swm” and “install2.swm” are not supported?
I’d try first another source and make sure the hardware supports Win8.
The limitations you’ve listed are not true.
Tried Windows 7 32 bit (normal install.wim file), works good. Notice that I use murphy78’s releases. The newer ones contain already split WIMs, which I think it’s the culprit (from WinSetupfromUSB side, on DVD+R DL it works great).
Tried Rufus, again the same error.
Tried ZOTAC WinUSB Maker, there is error “Critical error when injecting the boot tag”.
Now only Easy2Boot left to try.
I confirm only with Easy2Boot the source did work, both with MBR and UEFI booting (as .imgPT files).
I hope there will be a workaround with WinSetupfromUSB in the future.
I need to have my hands on such source to be able to reproduce the problem and eventually fix it.
Just Google “Windows 8.1 8in1 x64 en-US Jun2015 murphy78” for such source.
Just tried Windows 8.1 8in1 x64 en-US Jun2015 murphy78, iso file name Win81-x64-Jun2015-en-US.iso, CRC-32 8a1bdb77, using 1.6 beta1, everything seems fine, up to the “select operating system you want to install” screen, EULA and partition screens load too, did not continue further.
Where exactly do you get stuck? Are you using the same source with the same CRC32?
Yes, that’s the exact ISO.
http://any-image.com/images/00734134378704531353.png
I don’t know then why it didn’t work. Me too I didn’t go any farther than the partition screen. I just want to have a working Win8.1 USB install media. The computer that was tested was an old Core 2 Duo computer, as I work as amateur in a PC service shop.
The exact error that showed up was like this in this image, stuck in the logo screen before going to the install screen (not even showing the circle below the logo that should show up after a while normally):
http://any-image.com/images/88845833401817884421.jpg
It worked successfully when booted only via DVD disc and Easy2Boot. Perhaps buggy BIOS or compatibility problem?
I shall confirm once again if this will happen again using WinSetupfromUSB next time I update the source ISO and if a client wants a Windows 8.1 OS in his/her system.
For clarification, by “Me too I didn’t go any farther than the partition screen”, I meant when using DVD disk and Easy2Boot.
always missing file when install XP,
will show window like ‘cant find file xxxx, pls advise right address. globalsources/i386/’
i need to replace ‘globalsources’ with ‘e:’ maybe ‘f:’ to make is work
Is this customised source? Please try vanilla one if it is.
Is it the same machine?
Is there any usb hub between?
im using msdn version xpsp3 14-74070.
hv tried on my laptop/office computer, both hving same problem.
no hub between.
Try other USB stick, the one you are using might not have serial number which would lead to changing drive letters during the stages of the setup process.
thomas, change in the bios sata / ide (enhanced/compatible)
Hi, i have a problem with WinSetupFromUSB 1.6 beta1:
I am using the program for several Win7/8 setups. I format the stick, integrate W7 (4,6 GB on FAT32, splitting works fine) as first system, setup works perfectly. As soon as I integrate an other Windows ISO to the same stick, UEFI-Boot fails (“A recent hardware or software change might be the cause.”). When I go to “back to boot selection”, there is only “Windows Setup EMS enabled”, instead of several boot options.
So I switched back to 1.5 with smaller W7 image and W8 image, no problem at all.
Thanks for the report.
Do you happen to keep the log files created by 1.6 ?
What was the second source added with 1.6?
Is the boot menu working fine in BIOS mode?
Added:
Just added vanilla W7 then large W8.1 using 1.6 end everything seems normal.
Will really need your log files created by 1.6 to be able to reproduce the issue. Details where to find them in the last FAQ, on the FAQ page.
Hello,
logfile1: formating and adding several systems –> error
http://www.ericunterberg.eu/logfile.cab
logfile2: formating and adding one Win7 (> 4,2GB) –> worked
http://www.ericunterberg.eu/logfile2.cab
logfile3: adding additional Win8 to the bootsystem created in logfile2: failed
http://www.ericunterberg.eu/logfile3.cab
I didn’t test with legacy boot.
Best regards
Eric
Interesting…
Log files seem perfectly fine, BCD stores contain what they should, no errors either.
Only logfile1 is incomplete, did the program crash you have you forced it to close while copying? What errors did you have in this case?
Can you test legacy/BIOS boot?
Ok, next try 🙂
logfile4: reformatted usb stick (once again…), added standard W8.1 image –> works
http://www.ericunterberg.eu/logfile4.cab
logfile5: added additional W8.1 Pro image –> works
http://www.ericunterberg.eu/logfile5.cab
logfile6: added standard W7 image –> works
http://www.ericunterberg.eu/logfile6.cab
logfile7: added large W7 image –> fails in UEFI, but works with legacy-bios and grub
http://www.ericunterberg.eu/logfile7.cab
“Windows failed to start …. Status 0xc000000f A required device isn’t connetced or can’t be accessed”. After Pressing Enter again a boot list with only one entry “Windows Setup [ems enabled]”
you can download the boot and efi folder here:
http://www.ericunterberg.eu/bootfiles.7z
Thanks for your cooperation, these log files really help me a lot.
Can you replace USB_DISK:\efi\boot\bootx64.efi (2014-09-09 11:02:45 1618240 bytes) with the one in D:\Temp\w7upd\de_windows_7_upd0715.iso\efi\boot\bootx64.efi (2015-07-19 13:38:17 672640 bytes), keeping a backup of the original one and try again in EFI mode.
I think that issue is with the sources and mostly the sequence they are added to the USB disk, rather than the changes in 1.6, where the part dealing with BCD was not changed, except a few cosmetic ones. Boot process fails well before the file splitting with FAT32 introduced in 1.6 plays any role.
Worked… a little
The bootmenu works again.
Windows 7 setup starts.
Windows 8.1 Setup (exactly the same image, unmodified from MS, which works with 1.5) gives me:
“file \windows\system32\boot\winload.efi
status 0xc0000428
Windows cannot verify the digital signature for this file”
My multiboot stick created with 1.5 uses the 1618240 bytes bootx64.efi too with W7 and W8, works perfectly fine.
This source most likely has a modded EFI bootmgr (efi\boot\bootx64.efi) which uses efi\boot\bcd instead of the default and modified by WinSetupFromUSB efi\microsoft\boot\bcd. Or might be efi\boot\bcd is used first if present, although I am not aware of such behaviour. Default location for EFI BCD is efi\microsoft\boot\bcd.
The boot files you sent me, efi\boot\bcd is wrong, contains single default entry, not the modified by the program ones.
efi\microsoft\boot\bcd contains the proper entries.
Please delete or rename efi\boot\bcd and put back the previous \efi\boot\bootx64.efi (2014-09-09 11:02:45 1618240 bytes), this should also resolve the digital signature error. If boot in EFI fails, get this file from some other W8.1 x64 source, but make sure it’s original stock file.
Hi,
this worked well so far. right now I have the problem that Windows 10 64 bit Setup is not entered into
\efi\microsoft\boot\bcd
only in
\boot\bcd
Is my interpretation right that “\boot\bcd” is used for legacy-BIOS and “\efi\microsoft\boot\bcd” for EFI ?
http://www.ericunterberg.eu/logfile8.cab
I just started from Scratch with W10 (official ISO from MS, downloaded with the boot media creation tool and not manipulated…) with a new stick, no EFI folder is created. However, the EFI files are included in the image http://www.ericunterberg.eu/logfile9.cab
Thanks for the logs, they help a lot.
I am on 2 weeks holiday and when get back will publish updated version which should take care of this.
Eric, please try this updated version and let me know how it goes:
http://www.winsetupfromusb.com/files/download-info/winsetupfromusb-1-6-beta2-exe/
Those are the correct locations.
Hi, beta2 works with this Image. thank you so much!
I tried two times to post my reply with download links, but the postings didn’t appear. could you contat mit with chiron (-at-) gmx.com so I can send you the logfiles?
Thanks, I see them, comments with more hyperlinks need approval before they appear.
Going to take a look at them and try to reproduce and fix the problem.
1) Can we PLEASE have more than 10 seconds (preferably until we press CR or click “OK”) to enter the folder and menu names. Thank you.
2) Is there any way to add a UDF format ISO (ISO/IEC 13346) to the USB stick? I have such an ISO (containing Windows 7, all versions), and I have unsuccessfully tried to add it as a Windows 7 and Grub ISO, but WinSetupFromUSB 1.4 and 1.5 reject the image.
Like WinSetupFromUSB correct flash drive in a ready line where Windows list. The menu.lst file is not possible to do.
You can edit Windows bcd menus with the included BootIce or the free VisualBCD- edit \boot\bcd for BIOS boot and \efi\microsoft\boot\bcd for EFI boot.
Thanks. Two bcd file can not be edited, but you can remove them with the files iso. Then reinstall the image and get something like?
Thank You. I did it. Excellent program! 5 +++++++
Don’t work boot in UEFI mode with Windows 10 build 10.0.10240
You’d have to be a lot more specific. “Don’t work” brings no useful information at all to be able to help.
Error creating Windows 10 with both 32 and 64 bit arhitectures single ISO downloaded from Windows Media Creation tool.
What error?
Can you post the log files, details in the last faq on the faq page.
I have the same Windows 10 problem. It will build x86 & x64 for normal boot, but will not boot them in EUFI mode. It will not even create the EFI boot menu.
Log files please, details in the last faq on the faq page.