How to add multiple Windows NT6/10 (Vista, 7, 8, 10, Server 2008/2012) sources + Ubuntu to USB disk

Here is how to quickly add multiple Windows NT6/10 (Vista, 7, 8, 10, Server 2008/2012 etc.) sources and Ubuntu with persistence space to a USB disk.

1) If using the program for first time on this USB disk, select the auto-format option. Use FAT32 if you’d need to boot in UEFI mode.

2) Select the first NT6 source, it is expected as in ISO image file, here is an example with Windows 7 x64:

3) (Optional) In advanced options you could change folder and boot menu name, make Q-Dir File Explorer launch before start of Setup and add a folder with custom boot critical drivers to be loaded. The latter could be useful to load custom USB 3.0 drivers or SATA/AHCI/RAID ones.

For non-boot critical drivers, such as Wireless/WLan, LAN, Video or Sound drivers, a good idea is to use SAD (Stand Alone Driverpack utility), a proven and reliable solution from the DriverPacks team. More details about these options can be found in the FAQs.

4) (Optional) Add Ubuntu 14.04 Desktop with its own persistence space:


5) Press GO to start the process:

6) If the auto format option was selected, please do read carefully which disk is going to be reformatted, all data is going to be wiped out, the click OK on both dialogue boxes:


7) You can watch detailed progress of what is happening by selecting the Show Log option:

In a few minutes you will see Job Done message, the first two source have been transferred:

8) Now lets add another NT6 source, it would be Windows 8 Enterprise Eval x64, in the very same way as the first one. To preserve contents of the USB disk, make sure the auto-format option is not checked. Press GO and wait until process completes.:


9) Lets add yet another NT6 source, this time Server 2008 R2 x64, sequence is exactly as before:


10) Here is the boot menu once the system was booted from this USB disk:

11) To get persistence in Ubuntu, when the Live CD menu gets displayed hit the key to enter “Other Options”. This will display the arguments that the Live CD passes to the kernel. At the end of this argument list just add a space and add the word “persistent”. This will instruct the Live CD to maintain and use persistence.

102 thoughts on “How to add multiple Windows NT6/10 (Vista, 7, 8, 10, Server 2008/2012) sources + Ubuntu to USB disk

  1. I’ve the same Error Lin 34284 – I’m able to put one Windows 10 Source in the USB-Stick, but after that all other sources (Win10 or Win7) will give the same Error.
    How to provide my log to you?

  2. Hi, trying to build multi-boot USB with Windows install sources and a persistent Linux Mint 18 64-bit (Ubuntu variant). I created a persistence file as instructed (2 GB). Once I select the Linux Mint entry in the boot menu, I hit escape at the boot options to enter my own options, and type “persistent” (no quotes) before the — (I put a space afterwards as is standard). It does not actually seem to be keeping persistence, however. It boots normally, whether I also add “toram” or not (though “toram” succeeds in loading entirely into ram). But the casper-rw partition that’s “tacked” or “ghosted” onto the end of the usb device (/dev/sdb3) never mounts, and any changes I make (text files scattered about in various locations) don’t keep between reboots.

    /dev/sdb4 does mount as /cdrom when booted normally, when booted “toram” does not mount at all, which is expected.

    What am I missing? WSFUSB 1.8

      • It seems the last post mentions that persistent partitions stopped working. Other thread:
        Post #3 mentions that Ubuntu mangled casper such that it won’t recognize a casper-rw on the SAME DEVICE AS ONE IS BOOTING TO (emphasis mine).

        Since partition #4 is used to create the booting file system, partition #3 being casper-rw is being ignored.

        However, the idea of lower-casing the partition name sounded promising – in post #7 on that thread they say that using Multisystem they can get persistence to work with a casper-rw partition… I’ve rebuilt my linux mint with a 300 mb persistence file with lowercase partition name, but still no luck.

        Apparently the newest Ubuntu, however, has the same problem – I tested it the other night with a friend’s stick and he had the same problem – no persistence with ubuntu 16.x using WSFUSB.

        I suspect this thread:
        May have the answer – in that it requires editing the files in an installed live USB – however, we’re not really doing LIVE USBs now are we? We’re doing emulated Live CDs off of USB. And we can’t assume editing the files pretty much.

        There’s a Linux tool called Multisystem which seems to be, according to most forum threads, able to get around this, and I don’t know how they’re doing it but it might be worth a shot looking at that? Maybe it will help improve the process for WSFUSB.

        • So, I think I’ve been made a liar of. Tricksy computers. 🙂

          Turns out that when I had casper-rw (all-lower-case) in my label, I WAS getting persistence! Linux just never mounted the disk directly – but when I checked the /cow directory it persisted. Tested with some changed files in /etc and /home — they work. I’m not sure if it’s because of the capital letters in the label or not, but it seems to have worked when I set the label SPECIFICALLY to “casper-rw” all lower-case.

          It didn’t show it as a persistent drive, but /cow (the cow-file system that is used by ubuntu to make persistent live files) showed the right size, and changes were being written to the partition when I re-mounted it.

          Right now I’m testing a theory from “” and I might be interested in writing you up a tutorial on how to have UEFI:NTFS (from Rufus) combined with WSFUSB.

          Right now testing with an 8 GB persistence file (wowzers) with UEFI:NTFS built usb using winsetupfromusb to put linux on there. If successful, I’d like to give you the steps I took for it, as well as to suggest that the default persistence label be changed to “casper-rw”.


          • Another annoying comment of mine (sorry, I swear I keep thinking of these things)

            What method do you use to create the persistence file, do you have a particular link or place online that details the steps you do that might be duplicated? I ask because my 8 GB file screwed up but I think the label was bad, but it would be nice to create a few persistence files for testing (and making a few manual menu entries) off the same ISO, without having to copy the ISO over and over and over again.

            You know, for testing purposes. 🙂

  3. I have made multiboot using this fantastic tool ( WIndows 10 pro x64 – build 1709 + Windows 7pro x64 + Windows 7 pro x86 + Ubuntu 17.4 + some tools ). Now I have to replace build 1703 with 1709. How to do that to avoid formatting usb flash and starting all over for the begining, please ?
    Thank you

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

    RETRY to select another source or CANCEL to return to the main menu

    • Most likely the ISO is not in UDF format and 7-zip can’t read it. Confirm by opening it with 7-zip manually.
      Or it was heavily modified and those default folders were removed/renamed.

  5. and I have no idea how to upload log files, but winsetup’s ends with
    2018/07/23 21:33:10- Updating default description to: Win10 x86 Eng in D:\boot\bcd
    2018/07/23 21:33:11- The operation completed successfully.

    2018/07/23 21:33:11- Func UpdateBCD returned an error: 4
    2018/07/23 21:33:11- Func MakeVistaBoot returned an error: 5
    2018/07/23 21:33:21- Removing TEMP folder
    2018/07/23 21:33:21- ———————————Program quited———-

    and procmon shows the only programs accessing D:\boot are bcdedit and winsetupfromusb
    (originally, bitdefender was preventing access, but I turned it off and retried a few times)

  6. Please ignore above 2 comments and refer to comments on FAQ page where link to log files may be found. Thanks so much!

Leave a Reply