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.
Dear WinSetupfromUSB Team,
it seem to be somthing rong with adding an unuttendd ver. of windows xp when i added a coustmizable ver. many errore come one of the is missed programme on runonce when windows started , my idea is to add an option to add xp source ass iso file not ass extract file only .
It all depends how the customizations were made and whether customized scripts use hardcoded paths, rather than system variables. Installing from an ISO file, although now possible thanks to firadisk and winvblock drivers, still has some limitations on specific hardware and not all nt5 Windows are supported. In next versions I do intent to add such option, but it may not be in the next few months. Besides, XP not being officially supported anymore I don’t feel like spending a lot of time adding only minor advantages to the otherwise perfectly running in my opinion current procedure.
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.
why use winpeshl.ini and WinPreSetup.exe to setup windows7/8
you can use Firadisk its great driver
you edit boot.wim
you can add Firadisk to boot.wim
I use dism.exe to do these
dism /Mount-Wim /WimFile:C:\Win7\sources\boot.wim /Index:2 /MountDir:C:\Win7_Mount
dism /Image:C:\Win7_Mount /Add-Driver /Driver:C:\firadisk\firadisk.inf /forceunsigned
bcdedit /store C:\Win7\boot\BCD /set {default} testsigning on
dism /Unmount-Wim /MountDir:C:\Win7_Mount /Commit
With
/forceunsigned
bcdedit testsigning on
there isn’t any blog with this method in x64
I tested it very will in many old and new PCs and laptops
I am well aware of firadisk and winvblock and how to use them and there are plenty of resources about them.
Instead, I’ve opted for imdisk which is also great piece of software, rock solid and this method does not require any messing with dism, which I’d avoid at any cost because of Xp/Vista computers, on which I’d not install drivers and such in order to get dism working.
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?
HI itaushanov
I want to help you
Again why use winpeshl.ini
your method make many problem for me in many old PCs and new Laptops
We can still use the Trick of fake setup.exe from Windows XP in NT6 boot.wim (driver form cd)
topic (http://www.msfn.org/board/topic/12566-solved-drivers-from-cd)
here is my method
1- change winpeshl.exe permission by Icacls.exe or setacl.exe in the boot.wim
takeown /f %BOOTDRIVE%\windows\system32\winpeshl.exe /a
Icacls.exe %BOOTDRIVE%\windows\system32\winpeshl.exe /grant Everyone:f
1- rename winpeshl.exe to winpeshlORG.exe in boot.wim
2- copy setup.exe to boot.wim with name winpeshl.exe
3- copy setup.cmd to boot.wim
4- set Variables to ISO name (win7.iso) and ISO Folder (Win7_sp1) in setup.cmd
5- you can add more than one driver
here is my setup.cmd
@echo off
setlocal EnableExtensions EnableDelayedExpansion
cd /d %~dp0
rem http://www.msfn.org/board/topic/12566-solved-drivers-from-cd
rem
rem setup.cmd v0.05
rem
rem created by Memoarfaa
rem
rem used applications:reg.exe , net.exe ,Icacls.exe
rem
rem fake winpeshl.exe setup
rem
rem FiraDisk
rem http://reboot.pro/topic/8804-firadisk-latest-00130
rem
rem ImDisk
rem http://www.ltr-data.se/opencode.html#ImDisk
REM +=======================================================+
REM | setup FiraDisk parameters |
REM |——————————————————-|
echo setup FiraDisk parameters
reg.exe add “HKLM\SYSTEM\ControlSet001\Control\FiraDisk” /f /v “StartOptions” /d
“cdrom,vmem=find:\WINSETUP\W80\Win8.ISO;”
REM +=======================================================+
REM | Install FiraDisk Virtual Disk Driver |
REM |——————————————————-|
SET BIT=32
if “%PROCESSOR_ARCHITECTURE%”==”AMD64” SET BIT=64
SET ISODRIVE=
FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\WINSETUP
\MultDriver\firadisk.inf SET ISODRIVE=%%i:
cd /d %ISODRIVE%\
REM Load driver
if “%BIT%”==”64” \WINSETUP\MultDriver\ia64\devcon64 install \WINSETUP\MultDriver\firadisk.inf
root\firadisk
if “%BIT%”==”32” \WINSETUP\MultDriver\i386\devcon install \WINSETUP\MultDriver\firadisk.inf
root\firadisk
REM +=======================================================+
REM | Install ImDisk Virtual Disk Driver |
REM |——————————————————-|
cd /d %ISODRIVE%\WINSETUP\MultDriver\
rundll32 setupapi.dll,InstallHinfSection DefaultInstall 132 .\imdisk.inf
net start imdsksvc > nul
net start imdisk > nul
REM +=======================================================+
REM | Finally start the installation |
REM |——————————————————-|
FOR %%G IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%G:\windows
\system32\winpeshlORG.exe SET BOOTDRIVE=%%G:
cd /d %BOOTDRIVE%\windows\system32\
;imdisk -a -o rem -f %ISODRIVE%\WINSETUP\W80\Win8.ISO -m #:
takeown /f %BOOTDRIVE%\windows\system32\winpeshl.exe /a
Icacls.exe %BOOTDRIVE%\windows\system32\winpeshl.exe /grant Everyone:f
takeown /f %BOOTDRIVE%\windows\system32\winpeshlORG.exe /a
Icacls.exe %BOOTDRIVE%\windows\system32\winpeshlORG.exe /grant Everyone:f
if exist winpeshl.exe ren winpeshl.exe winpeshlold.exe
if exist winpeshlORG.exe ren winpeshlORG.exe winpeshl.exe
rem often winpeshl.exe
FOR /F “tokens=1-2*” %%a IN (‘reg.exe query “HKLM\SYSTEM\Setup” /v “CmdLine”‘) DO (
set CmdLine=%%c)
IF “%CmdLine:~-2%”==”” set CmdLine=%CmdLine:~0,-2%
cmd.exe /c “%CmdLine%”
EXIT
goto :eof =============================================================
I tested it and it work fine
I ask you to support firadisk into boot.wim
If you really want to help, you’d better give details about the problems you are experiencing so the program can be improved.
If you are using customized sources, share these details so program can be amended with such customizations in mind as well, should be easy task as long as I am informed with details about any issues.
In addition:
1) Why using both firadisk and imdisk, just in case?
2) Why not starting fake setup via transparent, documented and officially supported way, from winpeshl.ini, but messing with winpeshl.exe?
3) What are the advantages of the proposed method, compared to the one I am using now?
By the way- if a comment contains more than 3 links, it’s automatically held for manual approval, that’s why your posts did not appear right away.
hi itaushanov
here is details about the problems
1- winpeshl.ini, make this error at some machine
A- winpesh.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name.
B- in some Windows 7/8 – OEM Recovery Partition there is a winpeshl.ini try to load recovery\recovery.exe or recoveryamd64.exe
and it conflict with winpeshl.ini present in USB boot.wim and you can’t mount the ISO use WinPreSetup.exe, “/mountiso= —-”
c -your WinPreSetup.exe in some laptops like (acer aspire 5610) can’t find the Volume or drive letter of the USB and here is the message appear :-
please wait …..
13:10:16-waiting usb disls to initialize please wait
13:10:17 – same thing
So …
Other then the message appears after a minute or more
please reinsert the usb disk
usb disk is not yet available.
please unplug it, wait 5 seconds, and plug it back in
if you are using usb 3.0 disk try using usb 2.0 port
Why using both firadisk and imdisk,
2- in some machine ImDisk can’t correctly manage the setup
A-ImDisk mount ISO as udf file system and it fail in old PCs
B-ImDisk fail to mount ISO in some new core lenovo laptops during setup
C-FiraDisk take long time more than Imdisk to mount the ISO but it correctly mounted ISO with CDFS file system
d- if we mounted ISO with ImDisk FiraDisk can manage setup and find ISO were we mounted it in ram drive
1.A This should be fixed since version 1.3 if it’s the same case. Can you upload a few such winpeshl.ini files to datafilehost.com and give me the download link?
1.B I don’t get it- are you talking about Recovery CD/DVD ? Program should modify if there is an existing winpeshl.ini in such way, that ISO is loaded, then all existing commands executed as they are. Can you upload such winpeshl.ini as well?
1.C I think you got wrong conclusion- programs scans for the ISO passed as a parameter in all available drive letters, as they are presented by Windows, nothing fancy. If PNP manager has not initialized the USB disk yet, for example because of old or funny hardware and/or using Vista/Server 2008 which need quite a lot of time to initialize all USB hardware, it may take a few minutes until USB hardware is fully initialized, hence USB disk volumes mounted and available, you just have to wait, program can’t force Windows to work faster… Every other method would error out or be delayed just the same way. You can have a look at Setup log files to find out how long it takes Windows in such cases to initialize the hardware.
2.A What does UDF have to do with old or new hardware? Can you name an ISO file which ImDisk mounts incorrectly?
2.B Why don’t you inform its author with details about this problem? He is quite responsive and a will have it fixed quickly, but first make sure that’s the case indeed.
2.C All NT6 (Vista and above) install DVDs are using UDF, why you are involving CDFS at all? This has nothing to do with the problems you are having, the root cause is something else you are missing.
2.D If ImDisk mounted the image successfully, why would you need Firadisk as well?
To stay on the productive side, I’d prefer you to go through each issue you are having, one by one, providing details, rather than posting what the solution should be.
Get to the first problem, provide enough details to deal with it, such as hardware used, ISO file name and Windows version used, and details what and when exactly happens. Once solved, move to the next one.
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.