Here you can get help, access FAQ and tutorials, get support, report a bug of make feature request about WinSetupFromUSB by leaving a comment.

Useful Links

540 thoughts on “Help

  1. Hi itaushanov.

    I have encountered a couple of problems using the Samsung HDD utility HUtil 2.10 with v1.40 of WinSetUpFromUSB:

    (1) I had downloaded the HUtil210.iso (from to a Win XP folder which had compression enabled. After adding HUtil210.iso to my USB drive it would not boot into it claiming that it could not find the ISO. When I checked in XP I discovered that the ISO had been copied across verbatim so the file was still in compressed format on my USB stick. When I removed the compression (using Windows Explorer) and defragmented the USB drive it then booted. Surely this is a (minor) bug and WinSetUpFromUSB should copy the ISO to the USB stick uncompressed?

    (2) Now that I can boot into HUtil 2.10, it won’t actually work! I think there is a problem with the CONFIG.SYS line that loads the qcdrom.sys device driver – it reports no CD ROM drive found (I think). Anyway, the end result seems to be that none of the HDUtil files get copied into the RAM disk. Any chance you could take a look at some point?

    Thanks very much,


          • Yes, a bit overkill but if it works that’s the most important thing. I’ll give that a go, thanks.

            BTW, I have started using WinSetUpUSB 1.8 with a 64GB memory stick, and each time I want to add an ISO it asks me if I’m sure it’s the right drive because it’s so large – could the next release of the program be a bit more intelligent and identify if the target USB drive is already being used for WInSetUpFromUSB and if so not ask for confirmation each time? Thanks very much 😎

            • I would just raise the limit to >64 MB in the next version and keep the warnings as data removal is inreversible and would rather stay on the safe side causing a bit of inconvenience for the end user, which in my opinion is better compared to the question “I formatted the wrong disk by accident, how do I get my data back” :).

              • Sure, but at this stage I’m not formatting the USB stick – I’m just adding further ISOs to it so there’s no potential data loss?

                • One of the first checks is for grub4dos or fbinst MBR, if not present program will change MBR to grub4dos one. Won’t result in data loss most likely, but may got your main system unbootable if wrong disk is selected.

                  • OK, but I have already used WinSetUpFromUSB to format the USB stick with FBInst, so at this stage there should be no need to chang the MBR either?

                    • But there is need to check. Warning messages are when process starts, so one can answer all prompts and go for a smoke for example.
                      Won’t be changing this further apart from raising the limit.

  2. Hi again,

    Afraid I have found another problem! I have added the ISO for FreeBSD 11.1 (FreeBSD-11.1-RELEASE-amd64-dvd1.iso from to my USB stick but it runs into trouble during the boot process:

    Mounting from cd9660:/dev/iso9660/11_1_RELEASE_AMD64_DVD failed

    If you could take a look at that too I would be very grateful.

    Sorry to be bringing you problems… I’m a big fan of WinSetUpFromUSB 😎


  3. This Programm is valuable, it can no doubt make multiplebot usb sticks. Only deficiency is that the winpe10se-iso`s added to the multiboot usb sticks do not Function properly. Some funktions of the winpe10se-iso files do not work, as they should do. Winpe-xp and winpe7se functions properly. Does anyone experince also this problem and know the resaon or solution of this Problem? .

    • How did you add those, using which option?
      Winpe10se build can vary a lot, how did build yours? Did you download premade ISO? Where from? What exactly does not work? What errors do you get? A lot of questions to answer before anyone could help.
      As you can probably guess, all these are not stock ISOs and you need to be as detailed as possible.

  4. Hi,

    I’m sorry if I comment my issue again. I cant seem to find my previous post. How can I edit the virtual drive letter where the ISO is mounted? The recovery DVD I use specify drive O for loading the image. The usb always allocate drive G for this one, thus error occur on recovering the drive. By the way, the 1.8 also with windows server 2016

    • Program picks the first available drive letter and thisbchanges depending on the number of disks attached. Hardcoding this drive letter is not currently possible.

      You may however try to use the advanced option to launch Q-dir file explorer first and mount again your ISO as drive O, by using imdisk options for example or native mount if supported.

      • Hi

        Thanks for the reply. I am just curious about usbdrive.tag file? What is the purpose of this and can you give an example code?

        Another thing, is it possible if I format the usb as winpe bootable media then create the multiboot usb? I will not tick fbinst so that it wont format the drive. If so, what file will I manually launch in winpe? I just thought of this because it is easier to assign the drive letter in winpe. This would have not been an issue but some of our recovery dvd have an encrypted config.ini in the bin folder. I have tried editing the config.ini to manually to edit drive o to drive g and this works. I cannot simply copy the config file from the unencrypted one mainly because every pc has its own disk size and OS.

        This is just a great app. I have managed to make it work from installing windows 2003 OS standard all the way to server 2016.

        • Additional info, i say it is encrypted because config file is composed of hexadecimal codes. It can be opened thru notepad. For the unencrypted one, it could be easily opened and edited thru notepad as well.

        • Usbdrive.tag is used by grub4dos to determine which one is the USB drive.

          Boot process in BIOS mode is a as follows:
          Bios->grub4dos MBR on the boot drive(USB)->grub4dos (grldr) and then whichever grub4dos menu option is selected.
          Not sure what you mean by winpe bootable. That could mean number of things.
          If you don’t use fbinst format option, then MBR will be checked and replaced by grub4dos MBR code which searches for grldr and chainloads it. In case of auto format with fbinst that MBR code is fbinst one, which is also set to chainload grldr.

          Grub4dos can boot just about any other bootloader, be it bootmgr or whichever.

          What file winpe will launch depends entirely in what’s in it. Grub4dos only chainloads bootmgr, which reads bcd store and starts whatever it saya, in stock PE/windows setup that would be boot.wim. Now what you have in boot.wim is entirely another story.

          I would still advise you to try Q-dir route first. Besides, there are number of ways to make your PE start a script before anything else is executed.

          • Hi there,

            I have used q dir, and this tool helped me in tweaking the imagex source drive. I let the boot image run since it has a preconfigured volume letter and size allocation, thus saving me on assigning the multiboot in a different letter drive, then after the automated recovery of the machine, it prompts the syntax that causes the error. I can alt tab thru the windows and run command prompt from q-dir. Since imagex is ran thru command prompt, I copied the syntax and modified the source drive. Thanks for the pointers 🙂

            • Once Q-dir is launched, one could do just about anything. That’s the reason I have added that option a while ago.
              Glad to help

Leave a Reply