Help

 

Here you can get help, access FAQ and tutorials, get support, report a bug of make feature request about WinSetupFromUSB by leaving a comment.

FAQ
Tutorials
Useful Links

973 thoughts on “Help

  1. When I start from the USB I set up using winsetupfromusb I see:

    “Loading operating system . . .
    0”

    I have tried multiple USB drives with the same result.

    • You’d need to try various format options starting with the auto-format ones, next the ones in RMPrepUSB and BootIce. There is no need to try different USB drives for now, stick with one and find out which format option works for the particular machine/BIOS by experimenting. Unfortunately there is no fully “universal” way to format USB flash disk, since motherboard manufacturers don’t follow USB booting standard and make their own implementations.
      Let me know if you get stuck and need guidance.

  2. Thanks! I was able to make it work by formatting the USB drive as FAT32 instead of NTFS and it is working great now.

  3. Hi, I have problem with a winpesh.ini in Windows 7 SP1 64bit PL version. I try with two diffrent pendrive, with NTFS and FAT32 – use version 1.3. With Windows XP I don’t have problems. Please help.

          • I can’t Install Windows 7 from USB. When I boot PC from USB pendrive, select Windows 7 setup, Windows is loading and show window with cmd.exe, I write in cmd: winpresetup or type winpeshl.ini but i get access denide. I use program Winsetupfromusb version 1.0, 1.2, 1.3… any help?

            • Have you tried with an original, unmodified source ?
              Does this source work if using 1.0 beta8 for example?
              I cannot test with the one you are using and see what has been modified in it, the log file shows that everything should be fine.

                • Did you use the same file as source?
                  I would like to see what was going wrong, but you will have to help a little since I can’t reproduce the problem with the same source. Up for it?

            • Just tested GSP1RMCHPXFREO_PL_DVD.iso (CRC-32 2da9fe1f, 2,97 GB) which seems to be your source and everything run OK.
              You might be having a corrupted download, an antivirus or another program might be interfering with build process, or the USB disk might be faulty/fake size.
              Re-download your source, and test the USB disk.

              • Yes, I use this same source, but in 1beta8 read source from dir (unpack iso), but in 1.3 from ISO. 1beta8 work OK, but I see only one Windows 7 instance write to pendrive. 1.3 is better but not work for me… I use Windows 7 Home Premium SP1 PL DVD – copy 1:1 from original DVD.

                • Is the CRC-32 hash (CRC-32 2da9fe1f, 2,97 GB) of your ISO file the same as mine?
                  Can you prepare again with version 1.3 and place an empty file debugme without extension next to boot.wim on the USB disk, that’s in F:\WINSETUP\W7_SP1x64\, then start Setup and check if some log files appear in that directory? If they appear, please zip them and upload to http://www.datafilehost.com and give me the download link.
                  If no log files appear, try in the cmd window and once opened in Notepad save them to the USB disk, zip them and upload to datafilehost:
                  notepad %windir%\winpresetup.log
                  notepad %windir%\system32\winpeshl.log
                  notepad %windir%\inf\setupapi.offline.log
                  notepad %windir%\inf\setupapi.app.log

                  • Ok, I run WinSetupFromUSB 1.3 x64, check Auto format it with FBinst (NTFS, align), check Windows 7 and select win7_home_64b_sp1_PL_DVD.iso (CRC: 2da9fe1f, MD5: 653ee28b067337af6e9a82ba21be58c9, SIZE: 3,199,123,456). Logs: winpresetup.log – dosen’t exists, others: http://www.datafilehost.com/d/c4ea8186

                    • Mystery…
                      Testing with the same file and everything works fine, your log file looks fine, winpeshl.ini in it too, but for some reason WinPEShl.exe doesn’t execute WinPreSetup.exe.

                      Just sent you an email, please check it.

                    • For anyone following, this turned out to be messed up NTFS permissions on the folder where program was run from.

    • You have to write what you are putting on the USB disk. You should also start with the auto-format option.
      The log file is not the relevant one. Previous log files are in cab archives in \backups\ directory, date-time stamped, find the relevant one.

    • You could always use datafilehost.com for example to upload files, it seems to be one of the best free file sharing services around.

      As for your problem- please read my previous reply and start using the auto-format option. If doesn’t work- start experimenting with the other options, the reason I keep so many tools there is exactly this- giving user freedom to find the right one since there is no 100% universal one.

      When using RMPrepUSB it’s good idea to select “boot as HD (2 ptns)” option.

      Let me know if you still are having problems, and not what you have tried so far.

  4. Hello. I tried to make a bootable usb flash drive with both XP and WIN7 install kits, and I checked the “Auto format it with FBinst” option. After that, my flash drive is unusable, under any version of windows returning the error “Please insert a disk into removable disk (G:). Under BIOS boot selection menu, the flash drive is detected as “SKYMEDI”, but it is not bootable. Has anyone encountered this particular situation? Is there a solution for fixing my drive? Other info that might help: I used WinsetupFromUSB version 1.0 beta8 under OS: WIN7 x64, flash drive: Kingston Rubber Data Traveler R3.0 16 Gb. Any suggestions would be greatly appreciated. Thank you.

    • If RMPrepUSB and BootIce cannot format it then it’s gone. Just faulty or low quality UFD.
      You may try to recover it to some extent using manifacturer tool or program for the specific controller (flashboot.ru for tools) but I wouldn’t rely on it any longer.

      • It worked just fine before the format, so I presume it was badly formatted because now it is detected as Skymedi with the firmware revision 1.00. I need a way to undo the firmware change or to create a partition on that drive. I don’t think it’s a low quality disk, because it’s a high speed USB 3.0 kingston drive, a brand that never failed me before. RMPrepUSB and BootIce are not even detecting the drive, since it is listed as a removable media with no disk loaded.
        Thank you for taking the time to respond and if you have other solutions I’ll be happy to try them.

        • Neither the program auto-format option, nor any of the other tools included, have such special abilities to work at controller firmware level and make such damage. Thus it’s pure coincidence, which might have happened when formatting with Windows, writing a file and so on, just matter of time.
          Only a tool from manufacturer of the UFD or of the controller used, can damage in such way, and eventually recover it replacing the bad blocks with spare ones, if there are such and is possible. Search in flashboot.ru for the right tool and try. The most tools are not intuitive at all and you are on your own. Or you can simply return it if it’s still under warranty.

          Each manufacturer has good and bad series and models, where different flash memory chips are used. One cannot generalize that any brand is good and other is bad. There are even same model and size with different chips inside.
          There are also lots of fake flash drives, clones of a famous brands on ebay, amazon etc.

          I play with USB disks more than 8-10 years. In the past, 3 genuine Samsung drives failed on me within only a few days of usage.
          Another Patriot Xporter XT 1GB failed in a couple of years.
          Another SanDisk Extreme 32GB failed within 4-5 months of light usage. Hopefully the replacement lasts longer, it’s probably the fastest flash drive currently on the market.

          On the other hand, other few (Buffalo RUF2-R2G-S, Lexar 1GB 100X JumpDrive Lightning) are used on daily basis for 7-8 years now and are still going strong. You can only imagine how many formats with any kind of tool they had, and how many times they have been filled up with data and wiped out. On some of them I had full XP on NTFS and Debian on EXT3 (hell of a lot of writes) for weeks and months.

          In all cases when they fail, they start developing the same or similar symptoms you are describing.

  5. Dear WinSetupfromUSB Team,

    I am trying to create the stick under Windows Vista but I always get the result: Could not create NT6 boot files. I already tried version 1.4 and also version 1.2. Log and cab files can be found here:
    http://www.datafilehost.com/d/b095feed

    Would be great to get a hint to solve this issue…

    Thanks & best regards

    Timo

    • It seems in some bcdedit versions description must be set when creating a new entry.
      Please test this version of the program, extract the archive in the same folder where vers. 1.4 was extracted and run the new exe file. Let me know how this goes.

      Thanks for the report.

Leave a Reply