Here you can download WinSetupFromUSB and updates of the tools included.
Please do not hotlink files, use this page if you want to post a link to the program. If you need to link to a specific version, you could use version number like this:
http://www.winsetupfromusb.com/downloads/#1-10
Note: A few antivirus programs keep detecting a couple of the included files as viruses. This is false positive. These vendors were informed numerous times and the serious companies such as DrWeb and Kaspersky, update their signatures to remove the false detection within a few hours after being informed. Others, such as McAfee, despite all the efforts and contacts, don’t do anything to update their signatures. For a few unknown ones, which use third party signatures, there is no way to contact them or they simply don’t respond. This program will never knowingly distribute any kind of malware.
WinSetupFromUSB 1.10.exe (28 MB ; 1127819 downloads)
- Windows 11 support
- added detection of higher Windows 10 build numbers for the boot menu names
- Removed file spit infobox if ISO file needs to be split
- Increased warning for large disks selection to > 64 GB
- minor bug fixes
WinSetupFromUSB 1.9.exe (28 MB ; 2714098 downloads)
- added support for multi-version/dual Windows ISOs (32 and 64 bits in one ISO for example). Stock Microsoft dual ISOs are supported and tested, other such sources too, as long as they use unmodified bootmgr and default location for BCD store is in /boot/bcd. Tested in BIOS/UEFI with both Secure Boot on and off, stock Windows 10 dual and single ISO builds 1803, 1809, Server 2016 and 2019.
- added detection of Windows 10 build number which is added to the boot menu names
- updated ImDisk and WimLib
- minor bug fixes
WinSetupFromUSB 1.8.exe (24 MB ; 2761763 downloads)
- fixed issue with Windows 10 and recovery option not shown
- fixed issue with persistence file size not set correctly and tooltip for using persistence
- updated some the tools to their latest version- BootIce, ImDisk, WimLib
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.7.exe (24 MB ; 1538770 downloads)
- disabled superfloppy check due to issues with latest Windows 10 builds
- increased input timeouts to 45 seconds
- fixed issue with Swedish locale and bcdedit
- added check if imdisk is an old version
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.6.exe (24 MB ; 1177268 downloads)
- updated imdisk package for compatibility with latest Windows 10 versions
- Added Windows 10 in all GUI elements
Notes:
1) Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
2) If program is run on latest Windows 10 builds, seconds source can no longer be added due to incorrectly detected superfloppy format of the USB disk. This is due to changed by Microsoft WMI call results or structure. Fix is being worked on and will be released as soon as it’s ready.
WinSetupFromUSB 1.6-beta2.exe (24 MB ; 407349 downloads)
- Fixed missing EFI boot menu for Windows 10 sources
Note: Windows 10 – single ISOs created by Microsoft Media Creation Tool or downloaded from Microsoft should work. Dual ISOs made by the same tool (x32 and x64 in a single ISO) are NOT supported yet due to the changed structure. Such source can still be added using the previous versions which dump entire contents as they are, 1.0 beta8 for example. Limitations- such source needs to be added first, and any other sources of the same type,but not the same x32+x64, has to be added using 1.6 beta 2 or later.
WinSetupFromUSB 1.6-beta1.exe (24 MB ; 225517 downloads)
WinSetupFromUSB 1.6-beta1.7z (23 MB ; 64759 downloads)
- Added support for Windows Vista/7/8 and above sources larger than 4 GB and FAT32 for EFI compatibility- credits. In other words, now is possible to use FAT32 formatted USB drive and add larger than 4 GB source, say Windows 10, to be able to boot in EFI mode. As this is new feature not yet fully tested, the first version is released as a beta. Any feedback is appreciated.
WinSetupFromUSB 1.5.exe (23 MB ; 345300 downloads)
WinSetupFromUSB 1.5.7z (23 MB ; 73815 downloads)
- added Windows 10 support
- small bug fixes
WinSetupFromUSB 1.4.exe (22 MB ; 1969509 downloads)
WinSetupFromUSB 1.4.7z (22 MB ; 560592 downloads)
- added better handling of illegal characters for Linux/Other ISO source file name
- added advanced option for adding persistence partition for Linux sources. Each source has its own persistence space associated with it
- added better handling for Kon-Boot, source is to be added as ISO file using the Linux/Other ISO option
- added advanced option to add custom folder with boot critical drivers for NT6 sources (Vista and later). These drivers are added in boot.wim and loaded with DrvLoad before start of Setup, scratch space is increased accordingly. Only drivers for present devices will be loaded. Use it to add USB, SATA/SCSI or Chipset/USB drivers for example. Loaded drivers will be staged and available to the OS being installed. For non boot-critical drivers (Lan, WLan, Video etc.), have a look here
- added internal check for NT6 sources with multiple boot.wim, only default osloader entry in BCD store and the corresponding boot.wim will be added
- fixed errors when USB disk was initially prepared with the auto-format option, and on next run of the program it may complain about missing MBR and partition table
WinSetupFromUSB 1.3.exe (22 MB ; 1610758 downloads)
WinSetupFromUSB 1.3.7z (22 MB ; 314686 downloads)
- Fixed bug when adding NT6 source with missing new line feeds in WinPEshl.ini
- Fixed handling of NT6 sources with install.esd
- Fixed bug with NT6 sources with EFI directory but no BCD file in it
- Added Ei.cfg and CVersion.ini Removal Utilities in \tools\winisoutils directory should one needs those files removed from the NT6 source ISO file
- WimLib updated to version 1.6.0 for compatibility with new WIM formats
WinSetupFromUSB 1.2.exe (22 MB ; 303764 downloads)
WinSetupFromUSB 1.2.7z (22 MB ; 77948 downloads)
- Fixed bug where program running on Windows localized in other than English language would not add NT6 source
- Improved handling when program is placed and run from directories which contain special characters- `~@#$%^&()-+=,; Single quote – ‘ is not supported in program directory path and there is a check for that
- Added an advanced option for NT6 (Vista and later) sources to add Q-Dir File Explorer, which starts before Setup. This is useful to quickly browse disk contents and backup and restore files before launching Setup, rather than booting first in another OS to perform the same task. When Q-Dir is closed, Setup starts.
- BootIce updated to version 1.3.2.1
WinSetupFromUSB 1.1.exe (22 MB ; 221984 downloads)
WinSetupFromUSB 1.1.7z (22 MB ; 44882 downloads)
- (U)EFI support for Windows Vista x64 SP1 and later 64 bits Windows. USB disk must be formatted in FAT32 as per EFI specifications to boot under EFI. To prepare USB disk running the program under Windows XP or 2003, which do not include bcdedit.exe, an active internet connection must be present in order to download it
- default auto-format file system has been changed to FAT32 for EFI compatibility
- Firadisk driver is now added to each XP 32 bits source, but disabled by default. A new option in DPMS and custom F6 floppy menus activates it. This should help loading SATA/AHCI/RAID drivers from virtual floppy on problematic machines
- NT6 sources boot menus are now handled by BOOTMGR
- fixed recognition of Windows 8.1 sources which contain INSTALL.ESD instead of INSTALL.WIM
- added check in boot menu for Linux sources to warn if PLoP is loaded. Linux sources would not work with PLoP loaded as it supports only read mode
- removed the ZIP archive as it seems some users tend to launch the program directly from the Windows zip folder view, rather than extracting all files and folders. A self extracting SFX archive is added instead
- updated wimlib to 1.5.3 which would also fix the issues with the first 1.0 versions (downloaded before 14.Nov.2013) and NT6 sources
- various small bug fixes
WinSetupFromUSB 1.0.zip (37 MB ; 758787 downloads)
WinSetupFromUSB 1.0.7z (22 MB ; 75077 downloads)
Windows Vista and above Setup/PE may not start, command prompt may appear saying :
“A winpesh.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name.”
or simply restarts. Please refer to this post for details and fix, or re-download the program if you downloaded it before 14.Nov.2013.
- custom boot menu name when Linux/Other ISO is added
- when XP/2003/2000 source is added and incorrectly the i386 folder is pointed as source directory, program uses its parent directory
- other small fixes and improvements
WinSetupFromUSB 1.0RC4.zip (37 MB ; 53592 downloads)
WinSetupFromUSB 1.0RC4.7z (22 MB ; 43854 downloads)
- Ability to add multiple Windows Vista, 7, 8, Server 2008/2012 sources from ISO file. Use the same option to add PE2 (Vista/Server 2008) and above based utility. Thanks to synchronicity for his amazing wimlib project
- Ability to add almost any Linux based ISO which uses hybrid cd-rom/hard disk mode, credits to cdob . Refer to this page for a non exhaustive list of tested ISOs
- Auto-format option when used with NTFS would do its best when formatting the disk, to avoid fragmented large files on this volume later on by moving $MFT at the beginning of the partition. This way $MFT zone remains at the beginning of the volume and there should be way more contiguous space available large files to occupy
- DPMS updated to DPMS2, thanks to Steve
- the command prompt window during GUI mode of XP/2000/2003 setup is now hidden, thanks to cdob. It’s needed to keep the USB drive mounted throughout the GUI mode of setup
- added ability to copy all log files to the relevant WINSETUP sub-folder during PE phase of NT6 (Vista and later) boot. Create an empty file debugme with no extension in the relevant sub-directory, e.g \WINSETUP\Win7x64\debugme, and all log files from the start of PE phase will be copied next to it
- Updates of the tools included and various bug fixes
WinSetupFromUSB 1.0 beta8.zip (31 MB ; 74273 downloads)
WinSetupFromUSB 1.0 beta8.7z (18 MB ; 19618 downloads)
- added an option for Auto-format, using FBinst internally. This will delete all partitions and create a single one on the target USB disk, use with care
- added an option for Auto-detect and use SATA/RAID/SCSI F6 drivers during XP/2003/2000 Setup thanks to DPMS by Chenall. The boot entry is optional and has to be selected once before booting First part of Setup
- added an option to include a floppy image with F6 SATA/RAID/SCSI drivers during XP/2003/2000 Setup. The boot entry is optional and has to be selected once before booting First part of Setup
- working USB to USB install thanks to WaitBT driver by Shao Miller
- added an option for creating a “kicker” ISO for Vista/7/8/Server 2008 Setup, thus avoiding possible setup failures
- added another debug option for Vista/7/8/Server 2008 Setup, shifting hard disk possitions, thus avoiding possible other setup failures
- added an option for custom folder name and boot menu entry for XP/2003/2000 Setup
- added an option for adding and using custom NTDETECT.COM in order to avoid possible BSOD 0x0000007B on some machines
- fixed partial GUI freezes during large file copy, e.g. install.wim
- fixed bug where changes occur in the small ISO for XP/2003/2000 Setup leading to errors at start of Text mode
- added USB monitor function to refresh list if USB disks when disk is connected or disconnected
- updated versions of the included programs and tools, QEMU should now support booting Vista/7/Server 2008 x64 versions too
- various bug fixes and improvements
WinSetupFromUSB 1.0 beta7.7z (7 MB ; 33563 downloads)
- fixed issues on some new systems when XP/2000/2003 Setup hangs during text mode:
http://www.msfn.org/…all-iso-method/ - fixed grub4dos menu.lst entries when detecting the number of hard drives connected
- fixed custom boot menu titles input box when adding multiple similar XP/2000/2003 sources
- grub4dos, included tools and programs updated
- fixed issue with incorrectly detecting if source is Windows 2000
- flushing USB disk write cache is now performed internally, rather than using external programs
WinSetupFromUSB 1.0 beta6.7z (4 MB ; 41531 downloads)
- fixed bug in the created menu.lst when adding PartedMagic/Ubuntu variants or other ISOs
WinSetupFromUSB 1.0 beta5.7z (4 MB ; 5890 downloads)
- added option to display all connected disks in case one needs to prepare eSATA etc. drives.
- improved detection of USB disks at start of GUI mode in case of 2000/XP/2003 setup
- added support for adding Ubuntu/Kubuntu/Xubuntu ISOs
- added option for shared BTS OEM folder if several sources need to share same OEM folder. Use tooltip for info.
- experimental option to prepare source to be installed on USB, to be tested further.
- better handling in case 2000/XP/2003 install is on machine with 2 or more internal disks
- at start of GUI mode, after own setup.exe and setup.cmd are finished, setup.exe from th e source is executed, no matter another fake or the original one. Thus BTS presetup.cmd for example is executed by its fake setup.exe.
- added option not to check for and install grub4dos MBR. One would have to take care of chainloading grldr by other means.
- updated many of the included programs
WinSetupFromUSB 1.0 beta4.7z (4 MB ; 11831 downloads)
- fixed issue with non-English versions of Windows XP/2003
- fixed bug when program directory is on the same USB disk and partition which is being prepared
- removed dependencies on Windows Scripting Host, in case it’s broken.
- BootIce, Grub4Dos, SysLinux, RMPrepUSB updated to the latest versions
WinSetupFromUSB 0.2.3.exe (4 MB ; 109696 downloads)
i cannot add any iso windows 7 or 8, it gives me the “valid source” error no matter what iso’s i use
Did you extract the folder FILES as well as the program itself from the downloaded archive?
If downloaded the 7z archive, you may have to use 7-zip to extract it, some other programs do not handle well 7z archives, or just download the zip archive.
It would also help if you copy the log file produced to Pastebin and put the link in your reply.
Отличная программа !
Really it’s wonderful application but unfortunately, It’s not working with windows 8.1 [ it’s booting but not starting up the windows setup, I tried all the 3 mentioned solutions for the ADS issue with no success ]
*****for win 7 and 8 it’s working fine.
I am eagerly waiting for the new version.
It does work with Windows 8.1, there must something else in your situation.
Did you use the latest 1.0 version, with the updated libwim-9.dll?
Do you use vanilla Win 8.1 ISO?
Do you happen to boot from USB 3.0 port?
Does the hardware in question support Windows 8.1?
How far does the setup go?
What is the exact error message you are getting and at what stage?
Create an empty file “debugme” with no extension and put it next to the Win 8.1 ISO on the USB disk. That triggers all Setup log files to be copied to the USB disk, next to the debugme file.
This file should end up in something like G:\WINSETUP\W81x64\debugme , where G: is the drive letter for the USB disk.
Start Setup again and when you get to the error message close all dialogs one by one until system reboots by itself. The important part is to NOT force reboot and let setup log files copy to the USB disk.
Put all log files from the USB disk in the mentioned directory in a zip archive, do include WinSetupFromUSB.log file in program’s directory, or if it’s not a fresh one, backup of the previous log files are in cab archives in \backups\ directory, data-time stamped, find the relevant one or just put them all inside the zip archive.
Upload the zip file with all logs to say, http://www.datafilehost.com and reply with a download link.
Thanks a lot for your reply, time, support, and your great application(really i appreciate it).
here-under are the answers for your questions :
Did you use the latest 1.0 version, with the updated libwim-9.dll? Yes
Do you use vanilla Win 8.1 ISO? Yes
Do you happen to boot from USB 3.0 port? USB 2
Does the hardware in question support Windows 8.1? Yes
How far does the setup go? Windows setup dialog not coming ,instead repair question coming and PC restart automatically after 5 seconds [I attached snapshot for your reference]
Issue snapshot: http://www.datafilehost.com/d/cb17a104
Logs files; http://www.datafilehost.com/d/25ca8ec7
For your information same ISO tested in DVD and USB [ by copy its contents to it] and working fine.
again thanks a lot for your time and support.
I think the path “7- Windows ISO & images” breaks some parts of the script, apparently listing ISO contents. That results in:
2013/12/05 22:18:46- Determining if this is NT Setup or PE based utility, looking for install.wim2013/12/05 22:18:46-
7-Zip 9.30 alpha Copyright (c) 1999-2012 Igor Pavlov 2012-10-26
Listing archive: G:\sw-ahd\7- Windows ISO & images\Win8.1\Win8.1x86.iso
--
Path = G:\sw-ahd\7- Windows ISO & images\Win8.1\Win8.1x86.iso
Type = Udf
Comment = Win81-x86-en-US
Cluster Size = 2048
Created = 2013-11-15 04:00:00
Date Time Attr Size Compressed Name
------------------- ----- ------------ ------------ ------------------------
------------------- ----- ------------ ------------ ------------------------
0 0 0 files, 0 folders
2013/12/05 22:18:46-
2013/12/05 22:18:46- Did not find install.wim, assuming PE based utility
Thus Setup.exe is not launched later on at all, since source appeared as WinPE disk/utility, without install.wim in it.
I will try to fix that in the next version.
Meanwhile, please use simple paths, e.g :
G:\sw-ahd\7-Windows ISO-and-images\Win8.1\Win8.1×86.iso
Let me know if that resolves the issue.
Edit: On a second read- is there actually sources\install.wim in that ISO file? I see that 7-zip was actually launched properly, handling the path.
You’re right……….The ISO that am using it seems a modified one as it contains install.esd not install.wim
It seems some copies may contain install.esd instead of install.wim, like upgrade ones.
It’s quite easy to include check for that file as well in the next version, which will be ready in a week or two and includes EFI boot as well, for the Windows versions which support EFI.
Thanks for reporting.
Want an instruction to WinSetupFromUSB 1.1
@Serhiy
What kind of instructions are you expecting?
v1.3.2 x86 download (MD5 of EXE: 92A59B338392041243D0DCA38F3BC952)
BOOTICEx86_1.32.rar
v1.3.2 x64 download (MD5 of EXE: AEA61E21686F92A36DA96E852FA7DAE7)
BOOTICEx64_1.32.rar
@c2448956 – BootIce will be updated in the next version.
Meanwhile, should anyone need the new BootIce, it can be downloaded from author’s home page:
http://bbs.ipauly.com/viewtopic.php?f=2&t=2
The loading hangs when I try to run UBCD4WIN, the latest Ubuntu and some other distros. However I am wondering is there a way to install pre-Vista without copping thousands of installation files. As you know flash memories are no reliable if you have so much files on it. The guys in RMPREPUSB have found a way how to mount any kind of image file and use it successfully like a real CD drive. It’s too complicated for end users. They do not use GRUB4DOS. Is there a way to implement this?
>The loading hangs when I try to run UBCD4WIN, the latest Ubuntu and some other distros.
I cannot reproduce that. Can you give more details? What system (motherboard or laptop model) you are testing on? Are there any modifications to the USB disk?
>However I am wondering is there a way to install pre-Vista without copping thousands of installation files.
It is possible, but for now I’d rather use flat file structure. Why- because it’s rock solid, which I am mostly interested in, and compatible with all NT5 versions, including Windows 2000 and require single start from USB, just for the first part of Setup.
The price is longer build time while copying them, but with USB 3.0, USB hard disks, and even good USB 2.0 sticks with good write speed for small files (the area where slow USB sticks fail at) this is negligible compared to the benefits.
>As you know flash memories are no reliable if you have so much files on it.
A good USB stick can handle hundreds of thousands rewrite cycles. I am still using a few sticks which are 5-6 years old, and you can only imagine how many thousands of times they were rewritten, reformatted, filled up and so on while developing this program or just playing with USB boot. Besides, the real issue would be the rewrite cycles on the memory blocks, thus bunch of files, occupying say 100 MB, would cause roughly similar wear, as a single file of 100MB size. To reduce wear one could avoid NTFS and other journaling file systems, or just (temporarily) disable Last Accessed Time stamp. As said, given a good USB stick, wear is not a real issue at all.
>The guys in RMPREPUSB have found a way how to mount any kind of image file and use it successfully like a real CD drive
This is widely known way since grub4dos appeared to the Western public and indeed makes use of grub4dos, just as WinSetupFromUSB and many other tools do. Steve has done amazing job wrapping all that in good grub4dos scripts which make adding and booting such images much easier.
There is (yet) no magical way to map every and any ISO or hard disk image file and and use it everywhere as a real CD-ROM or hard disk, you may read more here.
Exceptions are such devices, which do that at firmware level- IsoStick, Zalman VE200 and the similar HD enclosures, or writing the ISO file in the protected area for emulated CD-ROM devices on USB sticks which support that, using a program which has access to the device firmware. Such devices present to BIOS and operating systems a real hardware device, no matter being an emulated at firmware level one.
Laptop: ASUS X50GL – probably manufactured in 2008
OS: Windows 7 x64 SP1. Here is a piece of the log:
____________________________________________________________
2013/12/13 15:41:15-WinSetupFromUSB 1.1 started
JetFlash Transcend 16GB USB Device
2013/12/13 15:41:16- DeviceID: \\.\PHYSICALDRIVE1
2013/12/13 15:41:16- PNPDeviceID: USBSTOR\DISK&VEN_JETFLASH&PROD_TRANSCEND_16GB&REV_1100\74XI94307KBZET0U&0
2013/12/13 15:41:16- DiskSize: 15.1 GB Signature: 87717B6B
2013/12/13 15:41:16- Partitions found: 2 MediaType: Removable Media
2013/12/13 15:41:16- Disk–Partition: Disk #1, Partition #0
2013/12/13 15:41:16- Logical Disk:G: File system:FAT32 Primary:True Bootable:True
2013/12/13 15:41:16- FreeSpace: 12.9 GB Partition Size: 15.0 GB
2013/12/13 15:41:16- Partition Starting Offset: 1048576
2013/12/13 15:41:16- Disk–Partition: Disk #1, Partition #1
____________________________________________________________
Before I started to use this flash drive I performed the following commands on it.
diskpart ; list disk ; select disk # ; clean ; create partition primary ; select partition 1 ;
active ; format quick fs=ntfs ; assign
I really had to do this because I could not use it with Windows7-USB-DVD-tool. I can’t use the popular Linux distros. I don’t think it is related to my flash drive.
I’d first test the flash drive for its real capacity to ensure it’s not one of the widely spread “fake” ones.
Next, use the auto-format option and redo it with what you need on it.
Let me know how it goes.
The test passed successfully. Log:
___________________________________________________
Quick Size Test (Destructive)
FAKEFLASHTEST v1.0.9 [SSi]
DRIVE 1 – 15.1GiB JetFlash Transcend 16GB
FFT – Quick Size Test (destructive)
G: MULTIBOOT DRIVE 1 – 15.1GiB JetFlash Transcend 16GB
Test took 1045 seconds.
Device quick test was OK *** PASSED ***
___________________________________________________
Then I ran winsetupfromusb1.1 and asked me to format it. I asked to all questions YES/OK. However I tested Ubuntu in another flash drive and still not working with both of them. I am using my flish drives from almost 1 year and hadn’t any problems. Please try the latest x64 Ubuntu from your side: ubuntu-13.10-desktop-amd64.iso
I have already tested several Ubuntu distros, take a look at supported sources page, all those were tested individually.
Just in case, I’ve just tested freshly downloaded Ubuntu 13.10 32 bits, on auto-formatted USB stick with the NTFS option and it loaded just fine on real machine, in QEMU it hangs.
If you boot from an USB 3.0 port, try USB 2.0 one. If there is no such, look in BIOS for some USB related options.
Did you try on another machine?
Some machines may access only the first 1.44 MB of USB disks, in this case the only hope is BIOS update or some funny option in it, or using early USB driver such as PLoP or the one in the newest grub4dos 0.4.6a versions. With PLoP you won’t be able to use the Linux distros, the rest probably will work, as long as PLoP and the BIOS play well together. If using newest grub4dos 0.4.6a versions you need to use FAT32 and BootIce to install the boot code in PBR, I haven’t tested yet how it works with Linux distros.
Let me know if you need any details, will guide you further. The first thing to try now would be to test it on a few other systems.
I never trust QEMU. I always boot from real machine. Anyway, 32 bit version of Ubuntu works fine but I need 64 bit version. Definitely it is not working. Already tested this to another x64 PC.
64 bit Ubuntu works here just fine as well, using freshly downloaded ubuntu-13.10-desktop-amd64.iso and auto-format in NTFS with 1.1 version of the program.
Add this to the existing menu.lst in USB disk root:
title ubuntu-13.10-desktop-amd64 TESTset ISO=/ISO/ubuntu-13.10-desktop-amd64.iso
ls %ISO% > nul || find --set-root --devices=hf %ISO%
map %ISO% (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=%ISO% splash --
initrd /casper/initrd.lz
Everything between “kernel” and “—” is on one row. Initrd is on a new row.
I’ve removed the “quiet” kernel parameter to let you see more screen output while loading. I assume /ISO/ubuntu-13.10-desktop-amd64.iso is still present.
Does this work? Where does it hang?
Besides, if the 32 bit version works, I see no reason why the 64 bit won’t, if the hardware supports it and the ISO file is intact. Both versions are prepared in absolutely the same way, WinSetupFromUSB does not make any difference between 32 and 64 bits versions, and would put any other Linux distro, no matter 32 or 64 bits, in the very same way.
Did you compare checksums of the downloaded ISO file? Is it the same when copied on the USB disk?