Solved Adding touchpad driver to rescue ISO

kelper · Oct 15, 2024

I am trialling many backup programs but have yet to find one where my touchpad works in the PE environment.

I know how to inject drivers into a WIM with Macrium Reflect, Acronis, EaseUS and Hasleo. But booting into each PE does not enable the touchpad.

Is this just te way the PEs or REs work? Macrium Reflect RE does have wifi access but I have never found ause for this. I just want my touchpad to work.

Meanwhile, I have bought a USB mouse, which works with all the common backup rescue disks and ISOs. I had a Bluetooth mouse which worked with MR but I can't find it.

hsehestedt · Oct 15, 2024

kelper said:
I am trialling many backup programs but have yet to find one where my touchpad works in the PE environment.

I know how to inject drivers into a WIM with Macrium Reflect, Acronis, EaseUS and Hasleo. But booting into each PE does not enable the touchpad.

Is this just te way the PEs or REs work? Macrium Reflect RE does have wifi access but I have never found ause for this. I just want my touchpad to work.

Meanwhile, I have bought a USB mouse, which works with all the common backup rescue disks and ISOs. I had a Bluetooth mouse which worked with MR but I can't find it.

Standby. I'll get you a procedure for updating your WinPE based media.

Might take me just a little while

hsehestedt · Oct 15, 2024

This will allow you to inject a driver(s) into boot.wim (WinPE).

Technical Note: The boot.wim may have 2 indices. Index 1 is WinPE, Index 2 is Setup (also WinPE based). We repeat the procedure below for both indices. If your image only has 1 index, you don't need to repeat for index 2. We will check how many indices your image has below.

Adding Boot Critical Drivers to the boot.wim (WinPE)

Create three folders. In this example I will use the following:

C:\Mount < Will contain the boot.wim to inject drivers into
C:\Mount\Drivers < Will contain drivers to inject
C:\Mount\BootWIM < A temporary directory to mount the boot.wim into

Copy the drivers you wish to inject into the C:\Mount\Drivers folder.
NOTE: The drivers need to be extracted so that the .INF file(s) are accessible. If you need help with this, let me know.

Copy the boot.wim file to the C:\Mount folder.

Open a CMD prompt as Administrator.

You can see information about the image file (including available indexes) with this command:

dism /get-wiminfo /wimfile:c:\Mount\boot.wim

Note the available indexes from the above command. A boot.wim will typically have 2 indices.

Repeat the below procedure twice. Once using an index of "1" and again for index "2".

Use the following DISM commands to mount the Boot.wim:

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

Use the following DISM command to add the driver(s):

DISM /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse

Use the following DISM command to unmount the Boot.wim:

DISM /Unmount-Wim /MountDir:C:\Mount\BootWIM /Commit

End Procedure for Adding Boot Critical Drivers to the boot.wim

antspants · Oct 15, 2024

I searched device manager for the touchpad driver needed for my Dell, downloaded it and extracted the inf file from the exe, added it into the Hasleo rescue media creation process.
Unless it was a fluke, or unless there was nothing really wrong with it and it was just a bad boot the first time, it seemed to work

garlin · Oct 15, 2024

I think this was re-hashed on a previous Macrium WinPE thread. Some touchpad drivers require the Intel Serial IO I2C driver be present, in order to work.

hsehestedt · Oct 15, 2024

garlin said:
I think this was re-hashed on a previous Macrium WinPE thread. Some touchpad drivers require the Intel Serial IO I2C driver be present, in order to work.

Precisely. My Lenovo requires the I2C driver in order for the touchpad to work. I also have an ASUS laptop that needs I2C for both the touchpad and the touch screen.

hsehestedt · Oct 15, 2024

Related to this discussion: The best way of handling recuse media that I have seen so far is for Veritas System Recovery (formerly known as Norton Ghost). You can add drivers to your image, take that recovery media or ISO image to a different machine, and continue to add drivers. You can add drivers for as many systems as you want, and it can automatically add them for each machine you take it to. That way a single recovery disk easily handled all your systems. I wish Reflect handled it that way.

kelper · Oct 15, 2024

When you say, "Copy the drivers you wish to inject into the C:\Mount\Drivers folder." is that just the inf or does it need to include the *.sys file as others.

SIW2 · Oct 15, 2024

kelper said:
I am trialling many backup programs but have yet to find one where my touchpad works in the PE environment.

I know how to inject drivers into a WIM with Macrium Reflect, Acronis, EaseUS and Hasleo. But booting into each PE does not enable the touchpad.

Is this just te way the PEs or REs work? Macrium Reflect RE does have wifi access but I have never found ause for this. I just want my touchpad to work.

Meanwhile, I have bought a USB mouse, which works with all the common backup rescue disks and ISOs. I had a Bluetooth mouse which worked with MR but I can't find it.

If you manage to find the asus recovery media for that model and if it includes touch screen capabilty, examining their bootable wims might give a clue. (assuming it is the asus in your specs)

There could be dependencies for the touch screen drivers.

I have a very large winre.wim from dell ( I think it win10 ) which has touchscreen stuff and net framework and a bunch of other things. It is a whopper about 1.3gb as I recall. So it is possible but not necessary easy. Cant remember where I have put it.

garlin · Oct 15, 2024

kelper said:
When you say, "Copy the drivers you wish to inject into the C:\Mount\Drivers folder." is that just the inf or does it need to include the *.sys file as others.

Normally you feed it the extracted driver folder. When a program is loading drivers, it reads the *.INF file for instructions on which files to copy, and what reg settings to update.

kelper · Oct 15, 2024

garlin said:
Normally you feed it the extracted driver folder. When a program is loading drivers, it reads the *.INF file for instructions on which files to copy, and what reg settings to update.

I understand that. But these PE/RE environments only seem to load boot-critical drivers.

garlin · Oct 15, 2024

Some people work around this limitation by having a WinPE wrapper script force the driver load:

Code:

drvload.exe X:\Windows\inf\netrtx32.inf

Depending on your rescue media, you'd have to check how they launch themselves and where you're allowed to insert new commands in the launch script.

kelper · Oct 15, 2024

But, do any of these wheezes enable the touchpad in a PE or RE environment?

SIW2 · Oct 15, 2024

Have you tried integrating it using dism or more easily with dism++

you could integrate these 3 and see what happens

https://www.acer.com/us-en/support/product-support/SF114-34/downloads

hsehestedt · Oct 15, 2024

kelper said:
When you say, "Copy the drivers you wish to inject into the C:\Mount\Drivers folder." is that just the inf or does it need to include the *.sys file as others.

Copy the entire driver. It is simply that the .INF needs to be present as well as all the other files.

SIW2 · Oct 15, 2024

dism++ integrate drivers to a wim

kelper · Oct 16, 2024

I will try later today to add the Serial IO driver.

hsehestedt · Oct 16, 2024

@kelper,

If you prefer, I can whip up that integration for you. Just tell me where to get the driver and the WinPE image you are using, and I'll make it for you if you encounter any difficulties.

kelper · Oct 16, 2024

hsehestedt said:
@kelper,

If you prefer, I can whip up that integration for you. Just tell me where to get the driver and the WinPE image you are using, and I'll make it for you if you encounter any difficulties.

I'll try myself at first. Thanks for the offer. I plan to add drivers to all the bootable ISO's on my Ventoy USB stick. That's Hasleo, Macrium, EaseUS, Acronis and any other backup solution I am testing. Just for learning purposes.

kelper · Oct 16, 2024

I solved this for Macrium Reflect at least, by using the RE option when making the Rescue disk/iso.

My current setup does not have a recovery portion so I had to restore from and old backup and use DiskGenius to copy the winre.wim from the recovery partition. This incorporates the driver(s) for the touchpad. I used this with the custom wim option in MR 8.1.

When I boot from a USB device, the touchpad and wifi work! But when I boot from the Windows boot menu, only the touchpad works.

Solved Adding touchpad driver to rescue ISO

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Similar threads