Here is an incomplete list of some of the supported sources tested with WinSetupFromUSB.
Since new sources are added frequently, please check again for updates.
Tests are usually performed on a NTFS formatted USB flash disk, including the Linux based ones. If there are additional steps needed to get a source going or another file system is needed, there will be a note.
Please leave a comment if you have tested another source, with a description and link to it, or if you have a request for a new one.
WindowsLinux / *BSD / *nixAntivirus Rescue DisksDOS/Other
Windows 2000/XP/2003 Setup option, multiple sources are supported:
- Windows XP, any architecture (32 and 64 bits), any Service Pack (SP), any version (Home, Professional etc.)
- Windows 2000, any SP, any version
- Windows 2003, any architecture, any SP, any version
Windows Vista / 7 / 8 / Server 2008/2012 based ISO option, multiple sources are supported::
- Windows Vista, 7, 8, 8.1, any architecture, any SP, any version
- Windows 10 Technical Preview– if using it with WinSetupFromUSB version 1.4 and earlier, make sure to use the advanced option “Custom menu names for Vista/7/8/Server Source” and set folder and boot menu names.
- Windows 10 – single and dual ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are supported since version 1.9.
- Windows Server 2008, 2012, 2016, 2019 any architecture, any SP, any version
- Windows Thin PC – Windows Thin PC 90 day evaluation
- Symantec Norton Ghost 15.01
- Windows Defender Offline , 32 and 64 bit versions, select to save as an ISO file when creating the startup media
- EaseUS Todo Backup WinPE emergency disk
- ESET SysRescue
- Avast Rescue Disc
Norton Bootable Recovery Tool
UBCD4Win/WinBuilder/Windows FLPC setup/BartPE option:
IA64/Itanuim versions are not tested.
Linux ISO/Other Grub4dos compatible ISO option, multiple sources are supported:
Ubuntu / Xubuntu / Kubuntu
Note- if there are problems starting or installing Debian/Ubuntu from USB hard disk take a look at this tutorial
Debian
Get Debian
- 7.1 Netinst i386, AMD64
- 7.2 Netinst i386, AMD64
- 7.2 live i386 standard, live i386 kde desktop
- 7.6 Netinst i386, AMD64
Mageia
- Mageia – 3 Dual CD – When the message that can’t find Installation disc appears, select Back, then Cancel, then select Hard disk from the menu. Next select the USB disk, sdb4 or whatever the USB disk was named, make sure 4th partition is selected and OK twice. Or point it to the installation ISO in /ISO/ directory.
Slackware
- SlackWare – 14.0 x86 DVD ISO -Once in terminal issue:
>fdisk -l <–make a note of the USB disk name
>mkdir /hd
>mount /dev/sdb1 /hd <– replace sdb1 with your USB disk name
Continue to setup and for source media select “Install from a hard drive partition”. For partition enter /hd and for directory enter /iso/. Setup will ask you to mount the Slackware ISO and use it as source. If you need to use more ISO files as sources, for different versions and architectures, you might have to place them in different directories. More details here.
Others
Instructions for Ophcrack
once loaded, open Sakura Terminal (top left corner) and issue:
>su root
enter root as password
>automount
note which device is the newly mounted one with ISO9660 file system, typically /dev/sdb4
>mkdir /media/oph
>mount /dev/sdb4 /media/oph
Now return back to Ophcrack Launcher and select Search for tables and start Ophcrack
Other way around is to copy tables directory from the ISO file to the root of the USB disk
Use Linux ISO/Other Grub4dos compatible ISO option unless other specified
Use Linux ISO/Other Grub4dos compatible ISO option
hard disk external adata ex500 no supported in program
Disk is not displayed or what exactly? If not displayed then try the advanced option:
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 wrong disk may lead to data loss.
Problem is in Windows or the USB driver, program simply requests from windows all drives on the USB. If disk is not there, but is USB, then windows or the driver did not enumerate it properly. For these cases that advanced option was added.
thank you is worked
Can the program be made for Linux?
If you mean to run it under Linux- unfortunately not possible.
Hi there, Is any chance that i can install Android Remix os and Lakka os to boot from a usb Drive by using winsetup?
You can try. Use grub4dos/other ISO option.
Please add latest versions of MemTest (v7.5) and Ultimate Boot CD (5.3.7)?
Did you mean that these were tested and were ok?
can you give me links for windows aio supported by winsetupfromusb?
I don’t maintain such list of links, nor intend to.
Generally speaking, if the ISO has single boot.wim and default folder structure and naming it should work. Given the large storage capacities and low prices nowadays, I am not interested at all in working on AIO ISOs support, especially because every “release” has its own thoughts how to do it, barely or not following at all manufacturer or any general recomendations or standards. This makes support of such ISO next to impossible in multiboot scenario.
Programs which dump entire contents as they are, have better luck because no changes or any logic is required when dealing with a single source- just make the disk bootable and copy contents as they are.
every time i boot from usb in uefi mode, show error like winload.efi is missing
how can i fix it?
What have you got on the disk?
win 10 x64 aio
Hi, it doesn’t suport WIN PE like this “https://winclub.pl/topic/287-win-dreamos-pe-czyli-windows-live/”. (bootmgr) Please add this option.
Please read the comment next to yours.
I Can’t use this tool I needs to make a windows bootup loader cd
wow really work awesome great job guys , well done
Mikrotik Server is not supported
Have you tried the netinstall version?
See here this is the problem
Is this the netinstall ISO?
no
Well, then try it as advised earlier.
Apparently the regular version doesn’t like booting from USB and the init scripts keep searching for their files on CD only, and there is no CD. That’s something RouterOS can fix in the init scripts.
ok thank you