• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
ilko_t

How to install Windows from USB- WinSetupFromUSB with GUI

2,139 posts in this topic

It is supported both as host and target OS, even the very first versions should support it.

What does make you think it is not, did I miss to put an info anywhere?

0

Share this post


Link to post
Share on other sites

No, all is right! A question appeared after I tried add to USB Win8.1 AIO setup from image I made myself. After AIO image creating I was tested it in VMWare. There all installations works. It looks like it's only my fault. Never mind!

0

Share this post


Link to post
Share on other sites

Put an empty file called debugme next to the Win8 ISO file and restart the setup, get to the point when the error is displayed and cancel/close setup windows one by one until it restarts. All log files from PE phase will be copied next to it. Put them all in a zip file and post it here. Did you happen to use an USB 3.0 port? Use 2.0 instead. Did you try Win8 on another computer? Is it vanilla source?

i tried, unfortunately setup doesn't write anything in that file. He is remaining empty after cancelling setup. I never used USB 3.0 , just 2.0. Tried another computer, and virtual machine , the result is the same. The source is from a original OEM multilanguage DVD that we're using in our organisation. Those DVD's we are receiving from MS, for further delivering to end-user

0

Share this post


Link to post
Share on other sites

It should not write to the debugme file itself, but copy all log files next to it.

Did you place it next to the Win8 ISO file?

It must be without an extension.

Can you manually copy x:\windowds\winpresetup.log when you get the error?
Shift+F10 will bring up command prompt, then copy it to the USB disk.
It would really help if you copy the other log files as well to see what is happening:

x:\windows\inf\setupapi.offline.log

x:\windows\inf\setupapi.app.log

x:\windows\system32\winpeshl.log

x:\windows\setupact.log

x:\windows\setuperr.log

Just in case- you are using 1.0 version of the program, right?

0

Share this post


Link to post
Share on other sites

i am using the version that i asked here, http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/?p=1049812, page 81. X:\windows\winpresetup.log and inf\setupapi.app.log - no such files. The others are here files.zip

The thing is that this is not like a error, maybe it shouldn't write in logs, it is more like a prompt to install the required drivers

Edited by Goblin
0

Share this post


Link to post
Share on other sites

I think you should just use the latest version:

www.winsetupfromusb.com/downloads/

Let me know if there are still issues.

0

Share this post


Link to post
Share on other sites

I think you should just use the latest version:

www.winsetupfromusb.com/downloads/

Let me know if there are still issues.

i guess that solved the problem :)

thanks for the great job you are doing

0

Share this post


Link to post
Share on other sites

I'm having a problem with installing a nlited version of XP Pro. I run WinSetupFromUSB and it completes successfully and it boots into the XP textmode installation. The problem is that the installation lists the partitions of the USB drive that the installer is on and not the internal HDD. Is there anything I could do to get it to show the internal HDD?

0

Share this post


Link to post
Share on other sites

Program updated to 1.1, list of changes:

  • (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
  • 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
  • various small bug fixes

Download:

http://www.winsetupfromusb.com/downloads/

0

Share this post


Link to post
Share on other sites

Hi all, this is the first time I write here, so because there are many many pages sorry If next question was already discussed...

I created an usb key with win2003 and win2008 OS, is It possibile to add other win OS to the drive OR the limit is 2 win OS's? I tried but I receive an error says "could not prepare NT6 boot files"

However very nice job, thank you

0

Share this post


Link to post
Share on other sites

The only limit for Windows OS is disk free space, you can put as many as you need.

Can you post the log file when the error appeared?
The last lost file in next to WinSetupFromUSB.exe, previous log files are in cab archives, data-time stamped, in the backups folder.

Find the relevant one, or just put them all in a zip archive and upload it to www.datafilehost.com for example.

0

Share this post


Link to post
Share on other sites

2013/12/17 17:36:31- WinSetupFromUSB 1.1 started

2013/12/17 17:36:31- OS: WIN_7 Architecture type: X64 ServicePack: Service Pack 1 OS Language: 0410

2013/12/17 17:36:31- Program directory: C:\Users\VITO\Desktop\WinSetupFromUSB\WinSetupFromUSB-1-1

...

log.txt

Edited by ilko_t
Log file added as attachment
0

Share this post


Link to post
Share on other sites

The output of bcdedit seems to differ when run on Windows with Italian localization and the function parsing BCD store fails. Other languages maybe affected too. I've tested on English and Bulgarian localizations so far.

I will have a look what is happening.

Meanwhile, if you need to get going quickly and do not need EFI support, use the 1.0 version which does not edit BCD store at all.

Please post long text output as attachment or upload it to file sharing service.

0

Share this post


Link to post
Share on other sites

Program updated to 1.2, list of changes:

  • 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 1.3.2.1

Download:

http://www.winsetupfromusb.com/downloads/

0

Share this post


Link to post
Share on other sites

Revealed a problem, the program refuses to work with images > 4GB in FAT32. In the image max file size <4GB

Image - 5jvf.png Maz size file - g3le.png Error - ou2l.png

Edited by FoxMan
0

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

You have the following options with this ISO:

1) Use FAT32 and 1.0 beta versions, which do not copy the whole ISO, but support only one source of this type. If you need EFI, it should need no further modifications if source is Windows 8.X

2) Use 1.0 and later versions and NTFS, multiple sources of this kind are supported, but no EFI support with NTFS, unless you load a NTFS driver, for EFI or motherboard manufacturer added NTFS EFI driver.

http://www.rodsbooks.com/refind/drivers.html

http://forums.mydigitallife.info/threads/46981-Install-Win8-Windows-8-1-UEFI-With-a-Over-sized%28over-4GB%29-install-wim

0

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

You have the following options with this ISO:

1) Use FAT32 and 1.0 beta versions, which do not copy the whole ISO, but support only one source of this type. If you need EFI, it should need no further modifications if source is Windows 8.X

2) Use 1.0 and later versions and NTFS, multiple sources of this kind are supported, but no EFI support with NTFS, unless you load a NTFS driver, for EFI or motherboard manufacturer added NTFS EFI driver.

http://www.rodsbooks.com/refind/drivers.html

http://forums.mydigitallife.info/threads/46981-Install-Win8-Windows-8-1-UEFI-With-a-Over-sized%28over-4GB%29-install-wim

Ok, thanks. Thou shalt not return the old way as an additional?

0

Share this post


Link to post
Share on other sites

One could always use any of the beta versions to add it the old way, I wouldn't add it as an option for now, unless there is lots of interest in such option.

0

Share this post


Link to post
Share on other sites

Ok. But I still torments the previous question. Program, as I understand it, turns the image to stick, and not at her blankly copies the image file. Then why the author evaluates the maximum size as the image, rather than contained within the image file with a maximum size, ie install.esd?

0

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

...

Again, the image is copied as is, the whole ISO, it is not extracted. Have a look at the contents of <USB disk>\WINSETUP\W71\ or whatever the name of the directory is, there are boot.wim and WindowsXYZ.ISO. How do you fit larger than 4GB WindowsXYZ.ISO on FAT32? :)

0

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

...

Again, the image is copied as is, the whole ISO, it is not extracted. Have a look at the contents of <USB disk>\WINSETUP\W71\ or whatever the name of the directory is, there are boot.wim and WindowsXYZ.ISO. How do you fit larger than 4GB WindowsXYZ.ISO on FAT32? :)

I understand that the loader will start directly from the image. And UEFI, respectively, will be. In my case optionally use fat32?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.