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:

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.9- 13.May.2019
WinSetupFromUSB 1.8- 16.May.2017
WinSetupFromUSB 1.7- 09.Aug.2016
WinSetupFromUSB 1.6- 28.Nov.2015
WinSetupFromUSB 1.6 beta2- 03.Aug.2015
WinSetupFromUSB 1.6 beta1- 24.May.2015
WinSetupFromUSB 1.5 - 10.May.2015
WinSetupFromUSB 1.4 - 27.March.2014
WinSetupFromUSB 1.3 - 10.Jan.2014
WinSetupFromUSB 1.2 - 20.Dec.2013
WinSetupFromUSB 1.1 - 08.Dec.2013
WinSetupFromUSB 1.0 - 17.Oct.2013 (libwim-9.dll updated- 14.Nov.2013)
Previous versions

1,180 thoughts on “Downloads

  1. Здравствуйте, в новой версии программы не нахожу кнопку 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?

  2. 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?

      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.

          • 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

  3. When i use this software in 64bit windows for make bootable 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.

  4. Hi , Thanks for your program, my question is can i set up a combine of windows 7 , 8 , 10 on the same flash-USB ?

  5. 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.

  6. 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).

  7. 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.

  8. 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.

      • 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?

              • 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.

Leave a Reply