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

564 thoughts on “FAQ

  1. I made one USB, start with windows 10 then Lubuntu 18 but multi boot desn’t work, didn’t show any multi boot menu, just get straight into Windows installation. How to make it to function multi booting with user interactive menu?

    the menu.lst file content is
    color black/cyan yellow/cyan
    timeout 10

    #graphicsmode 0x6A
    graphicsmode -1 640 480:800 24:32 || graphicsmode -1
    ## Menu AutoNumber
    write 0x8274 0x2001

    #graphicsmode -1 800:640 -1 24:32 || graphicsmode -1
    #font /unifont.hex.gz

    #clear mappings and set root in case we return from bootmgr
    map –unmap=0:0xff
    map –unhook
    map –rehook
    ls /usbdrive.tag > nul || find –set-root –devices=hf /usbdrive.tag > nul
    ls /default > nul && default /default

    title Windows NT6 (Vista/7 and above) Setup
    map –unhook
    map –unmap=0:0xff && map –rehook
    savedefault +1
    ls /shifthd.bat > nul || find –set-root –devices=hf /shifthd.bat
    /shifthd.bat
    if “%RDSK%”==”” pause Fatal error while swapping hard disk order, cannot continue! && configfile /menu.lst
    root (hd%RDSK%,0)
    chainloader /BOOTMGR

    title Second part/continue NT6 Setup (Boot first internal disk)
    map –unhook
    map –unmap=0:0xff && map –rehook
    savedefault
    ls /shifthd.bat > nul || find –set-root –devices=hf /shifthd.bat
    /shifthd.bat
    if “%RDSK%”==”” pause Fatal error while swapping hard disk order, cannot continue! && configfile /menu.lst
    pause –wait=1 Booting MBR on hd0 …
    chainloader (hd0)+1

    title Lubuntu18-alter from partition 0
    map –unmap=0:0xff
    map –unhook && map –rehook
    cat –hex –[email protected] (md)0x3D0+0x130 > nul && echo Cannot continue if PLoP is active, please start this entry without loading PLoP first && echo && pause Press any key to return to the main menu && configfile /menu.lst
    set /a dev=*0x8280&0xff
    root (%dev%,0)
    set ISO=/ISO/lubuntu-18_04-alternate-amd64.iso
    ls %ISO% > nul || find –set-root –devices=hf /usbdrive.tag|| echo Error! Could not find usbdrive.tag && echo && pause Press any key to return to the main menu && configfile /menu.lst
    ls %ISO% > nul || find –set-root –devices=hf %ISO% || echo Error! Could not find %ISO% && echo && pause Press any key to return to the main menu && configfile /menu.lst
    map %ISO% (0xff) || map –heads=0 –sectors-per-track=0 %ISO% (0xff) || echo FATAL ERROR mapping %ISO%, please check if file is present and defragmented && pause Press any key to return to main menu && configfile /menu.lst
    #http://reboot.pro/topic/9916-grub4dos-isohybrided/page-2#entry88531
    #http://www.rmprepusb.com/tutorials/tails
    set /a dev=*0x82a0&0xff
    debug 1
    parttype (%dev%,3) | set check=
    debug off
    set check=%check:~-5,4%
    if “%check%”==”0x00” partnew (%dev%,3) 0 0 0 && partnew (%dev%,3) 0x00 %ISO%
    if not “%check%”==”0x00” echo WARNING: PARTITION TABLE 4 IN BIOS DEVICE %dev% IS ALREADY IN USE! && echo && echo To prevent possible data loss will not continue further && pause && configfile /menu.lst
    map –rehook
    root (0xff)
    chainloader (0xff)

    title Lubuntu-18.04-alt from partition 0
    map –unmap=0:0xff
    map –unhook && map –rehook
    cat –hex –[email protected] (md)0x3D0+0x130 > nul && echo Cannot continue if PLoP is active, please start this entry without loading PLoP first && echo && pause Press any key to return to the main menu && configfile /menu.lst
    set /a dev=*0x8280&0xff
    root (%dev%,0)
    set ISO=/ISO/lubuntu-18_04-alternate-amd64.iso
    ls %ISO% > nul || find –set-root –devices=hf /usbdrive.tag|| echo Error! Could not find usbdrive.tag && echo && pause Press any key to return to the main menu && configfile /menu.lst
    ls %ISO% > nul || find –set-root –devices=hf %ISO% || echo Error! Could not find %ISO% && echo && pause Press any key to return to the main menu && configfile /menu.lst
    map %ISO% (0xff) || map –heads=0 –sectors-per-track=0 %ISO% (0xff) || echo FATAL ERROR mapping %ISO%, please check if file is present and defragmented && pause Press any key to return to main menu && configfile /menu.lst
    #http://reboot.pro/topic/9916-grub4dos-isohybrided/page-2#entry88531
    #http://www.rmprepusb.com/tutorials/tails
    set /a dev=*0x82a0&0xff
    debug 1
    parttype (%dev%,3) | set check=
    debug off
    set check=%check:~-5,4%
    if “%check%”==”0x00” partnew (%dev%,3) 0 0 0 && partnew (%dev%,3) 0x00 %ISO%
    if not “%check%”==”0x00” echo WARNING: PARTITION TABLE 4 IN BIOS DEVICE %dev% IS ALREADY IN USE! && echo && echo To prevent possible data loss will not continue further && pause && configfile /menu.lst
    map –rehook
    root (0xff)
    chainloader (0xff)

  2. Hello from Ecuador my question is. how to remove isos from the usb and add new or updated or new versions of Os and PEbuilder.

    Thank you.

    • AFAIK, you can´t remove ISOs, except by re-building the whole USB. But you can add an ISO to a previously created USB anytime.

  3. Nonsense. You CAN remove ISO’s very easily. See “15. How to remove already added sources?” in the FAQ. You can also replace an ISO (as long as it has the identical name) by simply copying it over the existing file on the USB (assuming there is sufficient space). If it has a different name, delete the old source (See #15 in the FAQ) and add the new.

    PUEDE eliminar ISO’s muy fácilmente. Consulte ’15. ¿Cómo eliminar fuentes ya agregadas?’ en las preguntas frecuentes También puede reemplazar un ISO (siempre que tenga el mismo nombre) simplemente copiándolo sobre el archivo existente en el USB (suponiendo que hay espacio suficiente). Si tiene un nombre diferente, elimine la fuente anterior (consulte 15 en las preguntas frecuentes) y agregue la nueva.

      • Well, adding a source and booting it is more that just copying a file.
        Logically, removing a source, needs to reverse what was done to add it.
        If you don’t like removing the BCD entry, nothing stops you from removing the ISO and leaving the BCD entries which will be pointing nowhere. What happens if you do that with a few or more sources?
        Given the various types of sources supported and the complexity adding them, I don’t have any plans for automating source removal in the program.
        Besides, there is not only Windows 7/8/10 sources supported with BCD entries, but also XP likes, Linux and so on.

        • Oscar F. says: “I don´t like the idea of messing up with the BCD just to delete an ISO. There should be an easier way.”

          It’s not that difficult, and you would have to really try to mess up the BCD. If you prefer, you can use BCDEDIT from the command line, but most people prefer the GUI format of BootIce or VisualBCD for simplicity and avoiding errors. I prefer EasyBCD, because I’m nore familiar with it.

          itaushanov says: “Logically, removing a source, needs to reverse what was done to add it. If you don’t like removing the BCD entry, nothing stops you from removing the ISO and leaving the BCD entries which will be pointing nowhere. What happens if you do that with a few or more sources? Given the various types of sources supported and the complexity adding them, I don’t have any plans for automating source removal in the program.Besides, there is not only Windows 7/8/10 sources supported with BCD entries, but also XP likes, Linux and so on.”

          If the sources are removed (deleted) without removing the corresponding BCD, winsetup.lst or menu.lst entries, people will forget they removed them, and complain when they select them from the menu, and they don’t load. I’m not sure what your loader program would do in that situation. Would it display an error message or would it crash?

          An “automated” source removal program wouldn’t be that difficult:

          1) Scan the USB and display the sources contained therein

          2) Allow the user to select the source to delete via mouse click (instead of having to type in the full name, which might lead to errors).

          3) If the source is “Windows Vista/7/8/10/Server 2008-2012”
          a) delete the corresponding ISO file and directory on the USB disk\WINSETUP\.
          b) delete the corresponding entries in \boot\bcd and \efi\microsoft\boot\bcd using BCDEDIT calls.

          4) If the source is “Windows XP/2000/2003”
          a) delete the corresponding folder in USB disk\WINSETUP\.
          b) edit winsetup.lst in USB disk root, removing the relevant lines.

          5) If the source is “Linux/Other Grub4dos compatible ISO”
          a) delete the ISO file from USB disk\ISOs.
          b) edit menu.lst in USB disk root, deleting the relevant lines

          I may write such a program myself, as I regularly remove old W10 sources, and add the latest build. It shouldn’t take more than a few hours.

          • Yes, it´s easy to edit the USB BCD with bootIce. When I posted above I was mistaken, thinking about the system BCD.

  4. Hello:
    Can WinSetupFromUSB recognize disk over 128GB? I have a 256GB removable disk, but this tool cannot display my disk in the list. I tried format disk with bootice and RMPrepUSB, but not work. How should I do? Thank you for your help.

  5. Hey , first of all great product east to use and as far as i can see working properly . I just have one silly question . I put inside of my 32 gb flash windows 10 64 , windows 10 32 , win 7 64 and win 7 32 . On top of that i put Linux , Hiren , bootcd , acronis and couple more . But when i boot it from the boot menu it only shows the 4 windowses and not the rest . M’i missing something ? (apparently i have missed something but if someone can help me what exactly 🙂 )

    • This usually happens when the ISO is not in UDF as it should be and the internally used 7-zip can’t read its contents, or if the ISO is heavily modified with system file/folder names changed, i.e. boot.wim changed to whatever.wim, or install.wim/esd. As usual, looking at log files quickly reveal what the issue is.

  6. hi when I was making bootable of windows 7 and windows 10 I got this message what to do? please help?

    this doesn’t seem to be valid source!
    Either or all of \sources\boot.wim,\bootmgr\boot, \boot\BCD are missing,or sources is not supported

    retry to select anaother sources or Cancel to return to the main menu

    retry cancel

    Logfiles:

    2018/08/29 21:57:52- Checking sizes…
    2018/08/29 21:57:52- Total source size- 0 bytes
    2018/08/29 21:57:52- Target space available- 28.6 GB
    2018/08/29 21:57:57- Obtaining size of NT6 boot files
    2018/08/29 21:57:58-
    7-Zip 9.30 alpha Copyright (c) 1999-2012 Igor Pavlov 2012-10-26

    Listing archive: D:\software\Windows 7 all Edition X86 & X64 Bit Activated\Windows 7 Sp1 AIO (x86x64) 11in1 es-es (USB3.0) Aug2018-=TEAM OS=-\Window 7 AIO SP1(Aug 2018).iso


    Path = D:\software\Windows 7 all Edition X86 & X64 Bit Activated\Windows 7 Sp1 AIO (x86x64) 11in1 es-es (USB3.0) Aug2018-=TEAM OS=-\Window 7 AIO SP1(Aug 2018).iso
    Type = Udf
    Comment = WIn7
    Cluster Size = 2048
    Created = 2009-10-22 00:00:00

    Date Time Attr Size Compressed Name
    ——————- —– ———— ———— ————————
    2009-10-22 00:00:00 D…. boot
    2009-10-22 00:00:00 ….. 262144 262144 boot\bcd
    2009-10-22 00:00:00 ….. 3170304 3170304 boot\boot.sdi
    2009-10-22 00:00:00 ….. 1024 2048 boot\bootfix.bin
    2009-10-22 00:00:00 ….. 97280 98304 boot\bootsect.exe
    2009-10-22 00:00:00 D…. boot\es-es
    2009-10-22 00:00:00 ….. 15872 16384 boot\es-es\bootsect.exe.mui
    2009-10-22 00:00:00 ….. 4096 4096 boot\etfsboot.com
    2009-10-22 00:00:00 D…. boot\fonts
    2009-10-22 00:00:00 ….. 47452 49152 boot\fonts\wgl4_boot.ttf
    2009-10-22 00:00:00 ….. 485760 487424 boot\memtest.exe
    2009-10-22 00:00:00 ….. 383786 385024 bootmgr
    2009-10-22 00:00:00 D…. efi
    2009-10-22 00:00:00 D…. efi\microsoft
    2009-10-22 00:00:00 D…. efi\microsoft\boot
    2009-10-22 00:00:00 ….. 262144 262144 efi\microsoft\boot\bcd
    2009-10-22 00:00:00 ….. 440832 442368 efi\microsoft\boot\cdboot.efi
    2009-10-22 00:00:00 ….. 1474560 1474560 efi\microsoft\boot\efisys.bin
    2009-10-22 00:00:00 D…. efi\microsoft\boot\fonts
    2009-10-22 00:00:00 ….. 47452 49152 efi\microsoft\boot\fonts\wgl4_boot.ttf
    ——————- —– ———— ———— ————————
    6692706 6703104 13 files, 7 folders

    2018/08/29 21:57:58-
    2018/08/29 21:57:58- Func _GetVistaKickerIsoSize returned an error: 3

    • That ISO file name has lots of special characters in it. Try renaming it first. Second- most likely it won’t work anyway, please read supported sources, faqs and notes next to the download.

      • this doesn’t seem to be valid source!
        Either or all of \sources\boot.wim,\bootmgr\boot, \boot\BCD are missing,or sources is not supported

        retry to select anaother sources or Cancel to return to the main menu

        retry cancel

        answer:

        i got the problem winsetupfromusb search for install.wim file when i extracted the iso I saw that there was no install.wim file And I found That in some windows iso,install.esd is keep instead of install.wim

        is there and option of .esd file detection in winsetupfromusb?

              • sorry I recognized that there two boot.wim file one is bootx64.wim and bootx86.wim

                Is there a issue with it? if so how can i solve it?

                • As mentioned earlier, such sources are not supported, there is no easy solution or workaround. Better off stick with stock, unmodified, single source ISOs and add as many as you want. Flash drives are large and cheap enough nowadays.

    • This usually happens when the ISO is not in UDF as it should be and the internally used 7-zip can’t read its contents, or if the ISO is heavily modified with system file/folder names changed, i.e. boot.wim changed to whatever.wim, or install.wim/esd. Usually, looking at log files quickly reveals what the issue is.

Leave a Reply