Here you can get help, access FAQ and tutorials, get support, report a bug of make feature request about WinSetupFromUSB by leaving a comment.
Here you can get help, access FAQ and tutorials, get support, report a bug of make feature request about WinSetupFromUSB by leaving a comment.
Ok thanks for your reply, onther quition about windows to go any ability to add this in the software ? ithink this good push to WSFU , other thing can you but a small tool or opition to customize the backgtound of your software .
http://www.winsetupfromusb.com/downloads/comment-page-3/#comment-285
About the background change- will have a look what can be done, but for sure it will be considered as a lo priority change, there are a lot more important changes to spend time on.
Hello!
Thank you for your very useful tool.
WinSetupFromUSB_1-4_x64
I would like to ask you how to install more than 5 tools in windows platform NT6:
Ex: Win 7 x86 + Win 7 x64 + Aomei Backupper + Aomei Partition Assistant + MiniWindows 7 + *** Elcom Windows Password Changer Windows 8 versions,*** …
In the “boot menu” I can see only 5 tools in platform NT6 + windows XP (NT5), even if the USB sticks are installed over then 5 (NT6).
Thanks again for all your efforts.
Tayfun.
(Google Translate).
I think you need to scroll down using the arrow key. Bootmgr limits the number of displayed entries, showing a little arrow of there are more entries.
Is that the case?
I get an error when I try to use my NT6 install image. Some work but they are smaller. Is there a size limit on the ISO? I’m attempting to use a 20GB iso, loading it onto a 32GB drive.
2014/05/13 14:34:45- Func _GetVistaKickerIsoSize returned an error: 3
2014/05/13 14:34:49- Checking sizes…
2014/05/13 14:34:49- Total source size- 0 bytes
2014/05/13 14:34:49- Target space available- 29.0 GB
Error 3 means that either or all of \bootmgr, \sources\boot.wim, \boot\bcd or \boot are missing in the ISO file, or less likely, 7zip is not listing the archive properly. Are those files and folders present? What are contents of this ISO file?
There is no sources folder in the root of the image, however they do live further down the tree under DEPLOY on this particular image. This is a capture of a reference machine for a Windows 7 deployment via MDT 2012. I was able to build the USB stick using Rufus and it boots and processes fine so this doesn’t appear to be a fatal error. Perhaps it should be a warning and allow the process to proceed instead?
Is in this case boot.wim located in DEPLOY subdirectory? Why actually not using SOURCES as in default NT6 image, out of curiosity?
In order to know where boot.wim is and prepare it for a multiboot scenario, program needs to know the location and the only way is by parsing BCD store, which introduces more possible hiccups, can’t just warn and proceed further. Quite tricky with heavily customized images to be prepared for multiboot.
I will see what I can do to parse BCD to obtain those locations, but until then, SOURCES folder as a placeholder of boot.wim and install.* is expected.
For a single sources like this, you could use 1.0 beta8 for example, which uses flat files structure and copies files to the USB disk as they are, just as Rufus does, but you will be limited to only one NT6 source placed like this. If needed, the next NT6 source might be added using newer version of the program, as miltiboot of such sources is supported. However, Windows Setup was changed several times when picking install.* location, depending on its version it might get confused which one to use if there are 2 available.
This is straight out of MDT. We’ve done nothing special, so I’m not sure why the difference in locations. In our case a single image is fine since we can technically include as many deployments as will fit by building them that way in MDT. That gives us a single WinPE boot and we can apply whichever task sequence/image we want.
Is boot.wim in DEPLOY directory?
If you don’t need multiboot any of the beta versions should work.
There are actually multiple boot.wim instances. The path will change each time, but \Deploy\Operating Systems\VariableName\sources where the VariableName portion changes based on the media definition. It appears to be using the folder name defined when the OS or image was imported into MDT.
Thanks. Such sources are gonna be taken care of, but it’ll take a bit, maybe after a few versions. Meanwhile, such sources should work fine with any of the beta veraions.
I’ve been working with the latest release for the last day or so and it’s been very slick overall. Thanks for a really nice tool. I have noticed a little quirk that you might want to look at. When you prompt for the name of the entry, you take the default after 20 seconds. Because we use pretty long names for identification I’ve yet to be able to key in my preferred choice before the dialog closes and things move on. Is there currently a way to adjust that timer? If not, you might want to consider a bit longer going forward. Ideally I’d say if there’s a way to detect the user has selected the field and started typing just kill the timer, but I don’t know if that’s viable.
Thanks
I’ve found no way to prevent the box closing if the timeout has reached. If you select the advanced option for custom directory an boot menu name it will be 30 seconds for both input boxes.
It’s no problem to increase it to any value, but what do you think it’d be a reasonable one, a trade-off between somewhat unattended USB disk preparation without more interactions with the user and enough time to enter text?
Let me try the advanced setting first. Personally I’d display the default value and just kill the timer entirely, at least in the advanced mode. That makes the user click the button to proceed but I’m not sure that’s a bad thing. Obviously a lot of this is just personal preference. May it could be made configurable?
Winsetupfromusb is the only tool that works for me. Now with Windows 8.1 and a 4 GB stick (the only one I have) it says insufficent space. When I use the xcopy command everything is copied (x64 version) but it won’t boot (I did use the bootmnr.exe command)(my computer seems to be too old). Can you please fix that?
How large is the ISO file exactly? How large is BOOT.WIM in \Sources\?
For single Windows NT6 sources, you could always use the previous beta versions, 1.0 beta8 for example, which use flat file structure and copy contents as they are.
Take a look at FAQ #11 as well.
Hi,
if i understand it right, you´re booting plop, and plop loads grub4dos, correct? Im asking because win7 startup repair mixed up the mbr on the usb drive, it starts directly to the bootmgr of my win7 setup instead to my grub4dos loading screen.. How can i fix that without loosing my files and config?
Thx, Thomas
PLoP is optional, manually selected in case of troubles with the USB.
You can repair MBR easily with FBinstTool if used the auto format option, or put back grub4dos MBR with BootIce for example if you haven’t.