Solved How to add drivers at USB's WinPE

The mounted boot.wim , doesnt have another boot.wim when its mounted.

Click to expand...

Of course it does not. It is not supposed to.

I am not sure what you are misunderstanding.

OP seems to be confusing using the 2nd index of the boot.wim with there being another boot.wim file.

pseymour said:

OP seems to be confusing using the 2nd index of the boot.wim with there being another boot.wim file.

Click to expand...

Ahhh, that makes sense!

Just for clarification and to expand upon what pseymour was saying, the fact that the boot.wim has two indices does not mean that there is another boot.wim within the boot.wim. In fact, if you download the retail edition Windows ISO image, you will find that it has 11 indices (Home, Pro, Pro for Workstations, etc.). The way these individual indices are selected is by including "index:1" (or 2, or 3, or...). As an example, when working with Windows PE, here is a sample command that shows us mounting the 2nd index of the boot.wim:

DISM /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:2 /MountDir:C:\Mount\BootWIM

So, to summarize, there is only one boot.wim and one install.wim. You access the individual indices within these images by specifying an index number to operate upon.

Hey, I have a wild idea: Do you want to simply share the drivers that you need to add to WinPE and WinRE? I can then integrate them into a Windows image for you and share it back to you. I do this often and it's so easy for me that it might simply be easier to let me do it

If you want to do this, here is the info I will need:

1) A share on a cloud service where I can get the drivers.

2) What build of Windows do you want these drivers added to?

3) What editions do you want in the final image? For example, do you want just Home, just Pro, both Pro and Home, all 11 editions, or any other combination of editions?

4) Do you want any other customizations? For example, I could add ALL of the drivers for your system. The end result is that if you do a clean install on your system, after installation is done, ALL of the drivers will already be loaded eliminating the need to install drivers after Windows is installed.

Let me know if this is of interest to you. If it is, let me know your preferences and I'll give you the details on what I need.

For the sake of completeness, here are my personal cheat notes on how to add drivers to Windows images (including to boot.wim).

NOTE: I don't specifically describe updating winre.wim, but it would be done lke this:

Mount the install.wim since the winre.wim is contained within the install.wim. Mount the winre.wim found inside the install.wim (think of this like a ZIP file within another ZIP file). Do the same steps as for upgrading the boot.wim except that winre.wim has only a single index so you only ever need to specify "index:1" in your commands.

@hsehestedt

I use wimlib to findthe bootable image

FOR /F "Tokens=1-3 Delims=: " %%I IN ('%wimlib% info "%wimpath%"') DO IF "%%I %%J"=="Boot Index" SET IndexBoot=%%K
:: then you could do

ECHO BOOT IMAGE IS %indexboot%
and/or use the %indexboot% variable in the dism mount command

long time since I used dism commands but It goes somethinmg like this I think

DISM /Mount-image /imagefile:"%wimpath%" /Index:%indexboot% /MountDir:wherever_that_is

I don't know how to do it in powershell. I can barely manage simple batch files.

hsehestedt said:

For the sake of completeness, here are my personal cheat notes on how to add drivers to Windows images (including to boot.wim).

NOTE: I don't specifically describe updating winre.wim, but it would be done lke this:

Mount the install.wim since the winre.wim is contained within the install.wim. Mount the winre.wim found inside the install.wim (think of this like a ZIP file within another ZIP file). Do the same steps as for upgrading the boot.wim except that winre.wim has only a single index so you only ever need to specify "index:1" in your commands.

Click to expand...

Haahahaha , loooool.
Check my previous #20 post. I said "i tried and it not works".
Why didnt work ? Cause as you can see at my #20 , i never put the new mounted boot.wim with the drivers ,
to its original location at my USB "installation" media (windows ISO).
So i read your notes , and i said lets try again.
This time i copied the new boot.wim at f:\sources , where f: is my USB.



Now i have access to my disk , for Restore Points , Backup Images , and command prompt (as c:\)
The strange thing is the touchpad drivers and thats the reason that i not marked the thread as solved.
While the same drivers work when i put at system's WinRE they work.
When i put them to boot.wim they dont. A possible explanation that i have for that ,
is that the WinRE has touchpad's driver by default (MS) and they work and my added drivers not change something.
Instead , perhaps the boot.wim it hasnt touchpad drivers by default so it not works.
Another possible explanation is that perhaps i have choose wrong drivers from my system.
I select these drivers via Rapr utility. There are 3 .inf files. I went to the folders that contained the .inf and
copied them all to my working directory (C:\users\myusername\Εφαρμογές\WinRE_drivers). There are and the disk's driver (1 .inf file).
So there are 2 issues :
1) You must add the copy of the mounted boot.wim to its original location
2) I have to find how i can add and the touchpad's drivers.
Thanks.

notes :
-sometime i will post here the commands that i used for the created new boot.wim , to simplify for other users
-My boot.wim at F:\ had 2 indexes : 1) WinPE , 2) Windows setup. I added the drivers at both indexes.

Touchpads also require the I2C driver(s) which allows Windows to see the device. You have to import that driver too.

garlin said:

Touchpads also require the I2C driver(s) which allows Windows to see the device. You have to import that driver too.

Click to expand...

I dont see something at rapr. How i can find them , if they exist ?

I select these drivers via Rapr utility. There are 3 .inf files. I went to the folders that contained the .inf and
copied them all to my working directory (C:usersmyusernameApplicationsWinRE_drivers).

Click to expand...

There should also be .sys and .cat files.

It is better to export any relevant drivers .

Look for the 3rd party drivers first and export any relevant ones into your winre_drivers folder.

Then display the inbox drivers and export the relevant drivers into your winre_drivers folder.

I use dism++ for this kind of thing because it is easy to see what you are doing.

Here is how I typically get drivers for my systems for the purpose of then adding them to my .wim images.

Start with a system that is healthy. By "healthy" I mean that all of the drivers are properly installed and I have no errors shown in Device Manager and all my hardware is working properly.

Create a folder to save your drivers to, for example, C:\Drivers_Backup

From an elevated command prompt run this command:

pnputil /export-driver * C:\Drivers_Backup

At least for me, the I2C driver has always been easy to pick out because it has I2C in the name like this:

SIW2 said:

I use dism++ for this kind of thing because it is easy to see what you are doing.

Click to expand...

I've never tried DISM++, maybe because I have this hangup about trying to always use native Windows or Microsoft stuff where I can, but I think that I better check it out to at least familiarize myself with what it can do. It seems that a lot of people really like it.

garlin said:

Touchpads also require the I2C driver(s) which allows Windows to see the device. You have to import that driver too.

Click to expand...

Do you mean this ?:

3rd party drivers shown by default





Tick the box to display Inbox drivers

Bug locker said:

Do you mean this ?:

View attachment 130235

Click to expand...

Yes.

Would it be under this section if it was Inbox.






But in buglockers screenshot it is oem6.inf so a 3rd party driver

SIW2 said:

Would it be under this section

View attachment 130238

Click to expand...

At my PC's product page , they give 3 more drivers with them installation file (sp140314.exe).

As they are few Kb i will add all of them. Thanks.

At my PC's product page , they give 3 more drivers with them installation file (sp140314.exe).
As they are few Kb i will add all of them.

Click to expand...

Yes give it a try



FYI Apparently could use pnputil

PNPUTIL /export-driver oem6.inf <destination>

Hi!
I don´t know if it works for you but i do like this:

1. I create a folder, extract drivers to there (is supose to create another folder with drivers name)
2. i have this batch:
3. Code:

   @echo off
   title Drivers Tool
   setlocal EnableDelayedExpansion
   
   :: BatchGotAdmin
   :-------------------------------------
   REM  --> Check for permissions
       IF "%PROCESSOR_ARCHITECTURE%" EQU "amd64" (
   >nul 2>&1 "%SYSTEMROOT%\SysWOW64\cacls.exe" "%SYSTEMROOT%\SysWOW64\config\system"
   ) ELSE (
   >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
   )
   
   REM --> If error flag set, we do not have admin.
   if '%errorlevel%' NEQ '0' (
       @echo. & @echo. & @echo [1m[31mRequesting administrative privileges...[0m
       goto UACPrompt
   ) else ( goto gotAdmin )
   
   :UACPrompt
       echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
       set params= %*
       echo UAC.ShellExecute "cmd.exe", "/c ""%~s0"" %params:"=""%", "", "runas", 1 >> "%temp%\getadmin.vbs"
   
       "%temp%\getadmin.vbs"
       del "%temp%\getadmin.vbs"
       exit /B
    
   
   :gotAdmin
   ::To CD to the location of the batch script file (%0)
   CD /d "%~dp0"
   Set /p dir="Drivers folder name: "
   Set /p dest="Offline mounted image root: "
   CD /D "%dir%"
   FOR /F "TOKENS=*" %%A IN ('DIR /S /B "*.inf"') DO Dism /Image:"%dest%" /Add-Driver /Driver:"%%A"
   endlocal
   @echo Done!
   @echo.
   pause
   exit

4. Copy/Save code as .bat and paste in the main folder, not drivers folder .
5. Execute it!

Note: Desteny must be a mounted Offline image! And .exe drivers can be extracted! ( can use 7z, winrar, etc)

I hope it helps.

Bug locker said:

Hey all.
I just created a fresh USB with the WinPE.
My disk needs an Intel RST driver and the Windows still dont have a driver. So i cant see C:\ via WinPE
Also , i need to add the touchpad's drivers , because it hasnt and also i have bluetooth mouse.
If it helps i already have C:\Recovery\WindowsRE\Winre.wim , with these drivers added.
Anyone to know the procedure to add the drivers ?
Thanks.

Click to expand...

And with the help of everyone in this thread, the problem was solved !!!!!!!!!!!!!!​

Here are the step by step solution for all :


Solutions data:

-D:\ was the installation media USB stick (decompressed Windows ISO with Rufus in my case)
-F:\ was the external SSD that i used for work with boot.wim
-F:\mount\ was the working directory
-F:\mount\bootwim was the working directory for index 1>WinPE
-F:\mount\bootwimsetup was the working directory for index 2>Windows setup
-Index 1 was the WinPE
-Index 2 was the Windows setup

---

Commands :

1) F:\mount\drivers>dism /get-wiminfo /wimfile:c:\Mount\boot.wim
(checks the indexes)

2) DISM /Mount-Wim /WimFile:f:\Mount\boot.wim /Index:1 /MountDir:f:\Mount\BootWIM
(mounts the WinPE index 1)

3) DISM /Mount-Wim /WimFile:f:\Mount\boot.wim /Index:2 /MountDir:f:\Mount\BootWIMsetup
(mounts the WinSetup index 2)

4) DISM /Image:f:\Mount\BootWIM /Add-Driver /Driver:c:\Users\thana\Εφαρμογές\WinRE_Drivers /recurse /forceunsigned
(Adds all the drivers inside the "WinRE_Drivers" directory, to index 1 , signed or not)

5) DISM /Image:f:\Mount\BootWIMsetup /Add-Driver /Driver:c:\Users\thana\Εφαρμογές\WinRE_Drivers /recurse /forceunsigned
(Adds all the drivers inside the "WinRE_Drivers" directory, to index 2 , signed or not)

6) DISM /Unmount-Wim /MountDir:f:\Mount\BootWIM /Commit
(Unmounts and saves the new Boot.wim Index 1)

7) DISM /Unmount-Wim /MountDir:f:\Mount\BootWIMsetup /Commit
(Unmounts and saves the new Boot.wim Index 2)

After all these , we got the new mounted boot.wim at F:\mount .
Finally we got to copy the F:\mount\boot.wim to D:\sources , e.g i did that with the file explorer.
It will if we want to overwrite the old boot.wim , and yes we do.
We start our machine from the installation media (USB stick in my case) ,
to confirm that all the wanted drivers are there and work properly.

Thats it.