FAQ

1. What can be added to the USB disk with WinSetupFromUSB?
2. Does it support multiple sources of the same type?
3. My internal disk is not shown during first (Text mode) part of Windows XP (2000, 2003) setup
4. There is error 0x0000007B on blue background (BSOD) at start of XP (2000, 2003) Setup
5. Program does not display my USB disk
6. Are customized Windows sources supported?
7. What do the advanced options do?
8. My system won't boot from USB
9. Is (U)EFI supported?
10. How do I add another Windows or Linux source?
11. When adding NT6 (Vista and above setup or PE based utility) ISO occupied space on the USB disk is 150-220 MB more than my source
12. Is the program free and may it be freely redistributed?
13. XP/2003/2000 Setup is very slow when copying files at Text mode phase
14. How to report bugs or problems with the program?
15. How to remove already added sources?
16. How to edit boot menu names?
17. I am unable to add Linux/Other grub4dos ISO because it cannot be de-fragmented
18. Why I cannot boot other sources in UEFI mode, only Windows ones?
19. Is Windows Secure Boot supported?

706 thoughts on “FAQ

  1. Why can I not be able to install customized live linux operating system and windows installer in a single USB?
    When I boot it up in BIOS mode, it has 2 options but I when choose the customized live linux operating system, it failed to load while the other works just fine. I tested the customized live linux operating system alone (without any other operting systems) and it worked perfectly fine. Can anyone explain why it do not work with 2 operating systems?

  2. I put Kali linux on by copying and paste the files inside the .iso file to the usb drive. Yes, I tested it on the same drive.

    • Writing this reply from a freshly prepared and booted in BIOS mode Kali Linux (Live AMD64 option), the same ISO you provided:
      https://cdimage.kali.org/kali-2020.1b/kali-linux-2020.1b-live-amd64.iso

      http://www.winsetupfromusb.com/wp-content/uploads/2020/04/Screenshot_2020-04-05_18-42-04.png

      Also added Windows10_1909.iso to the USB disk, which also boots just fine.

      Would be quite hard to guess what’s wrong in your case, but if I am to guess, that would be a corrupt download or unreliable USB disk.
      Another possibility is using > 128 GB USB disk, which already had lots of stuff, so Kali ISO was placed beyond the readable 128 GB boundary, that’s typical BIOS limitation.

      Besides, the claim the you booted Kali Linux simply by copying files from the ISO cannot be true, there must have been something else done to have it start, wish multiboot was that simple.

      If you do need more help on this, you will have to provide every single step you made in both cases, with all the details, hopefully that will shed light what was wrong.

      • Yes, I sometimes use Rufus for the task but it also works without Rufus (for me). It seems like I will have to go to the store and buy another USB stick for Kali

    • How exactly do you load the F6 driver and which one is it?
      Have you used the advanced option where you can provide floppy image with F6 drivers?

      • I used the the ICH9/ICH9DO Driver, btw I got Windows 2000 to work but it’s the Adv. Server edition, the only bad thing is that I am now stuck in driver comparability hell, think you can help with that?

        • How exactly did you supply the driver to the installer? Integrated in source, how, nLite, BTS driver pack, manually in source….
          There are so many ways, please be very specific

          • I didn’t integrate anything, I downloaded the ISO and burned it to a CD. The only thing that made it work was switching the Drive Operation from ACHI to a legacy ATA to make the installer think its using an IDE drive, after install, it worked off the bat. Drivers are the only problem. Device Manager doesn’t want to play nice, so I did it the quick and dangerous way, dropping the inf’s, dll’s and cat files in thier right folders

            • So you are not installing from USB disk, right?
              Why don’t you just use nLite or BTS mass storage pack to integrate the correct drivers?

              Still haven’t answered how exactly you provided the F6 driver.

              Also not sure what you mean that you copied files to the relevant folders.

  3. me gustaria que incluyeran traducciones de idioma al programa, en especial el español. y que la descripciones de las distintas opciones se mostraran en su respectivo idioma seleccionado. muchas gracias de antemano. Dios les continue bendiciendo en su trabajo.

  4. I read that you said “GRUb4dos” does not support UEFI because “GRUb4dos is a derivative of GRUB1”.And then I found GRUb2win on the web, which is a derivative of GRUB2.I come from China, translation software may not be very accurate, sorry!

    • Grub2Win is a derivative of grub2 and just as grub2 cannot map a file to a partition entry. That’s the unique grub4dos feature allowing to boot just about any Linux distro, feature all other bootloaders are missing, hopefully not for long.

  5. I have a MVMe ssd in a usb enclosure.
    I do have 3 partitions on the drive.
    WinSetupFromUSB can not see any of the partitions on the drive or even the drive itself.
    What is the problem here?

    • Windows doesn’t see it as USB disk, so not in the list.

      From the FAQ #7 above:

      What do the advanced options do?

      Display disk drives on all interfaces, not only USB – this should be self explanatory, show all detected disks, not only the ones on USB interface. Use it with caution, selecting wring disk may lead to data loss.

  6. Hi there,

    I have successfully made multi operating system (XP + Win7 + Win8) bootable setup USB with your great tool. It’s working flawless, but the folder created by the tool is not meaningful which I want to change.

    For example:

    in WINSETUP folder W10_x86_1607 was created for Win7 and I want to change it as W7 and W81x86 was created for Win8.1 and I want to change it as W81.

    For that I used Visual BCD and updated the Elements (ApplicationDevice and OSDevice) in both locations in booth\bcd as well as efi\microsoft\boot\bcd files

    FROM \WINSETUP\W10_x86_1607\sources\boot.wim TO \WINSETUP\W7\sources\boot.wim

    AND

    FROM \WINSETUP\W81x86\sources\boot.wim TO \WINSETUP\W81\sources\boot.wim

    When I tried booting from USB, it booted successfully. I selected the setup for desired operating system. Setup was loaded successfully, the background was clearly seen. But the first window (screen) asking for language/input could not be seen. Whereas a small windows by WinSetupFromUSB appearing telling initializing USB drive, please wait.

    What am I missing?? What else changes I need to perform??

    Please guide.

    Thanks.

    • You also need to edit the paths in \windows\system32\Winpeshl.ini in boot.wim next to the ISO, index 2.

      Folder names can be set at build time, just select the advanced option for custom folder names.

      Are you using customized source for Win7? A bit weird why Win7 source was detected as Win10, apparently the info in boot.wim contains strings for Win10, that’s what program ises to determine Windows version and names the folders.
      Either Microsoft changed something recently, or this source was built using Win10 boot files/boot.wim and Win7 install.wim.

Leave a Reply to beka Cancel reply