Driverpack Offline Windows 7 64 Bit

0 views

Skip to first unread message

Abigayle Laurenitis

unread,

Aug 3, 2024, 6:10:57 PM8/3/24

to ternejodhtim

See here for the procedure to load a driver to an offline Win7 image using dism. It's pretty simple, but I can't get it to work for loading USB3 drivers (to allow Win7 to use a new motherboard which has only USB3 ports, and no USB2 ports). I know that dism successfully loaded the new drivers to the old image, but the new drivers are not used during boot of the old image.

I suspect that the reason is that the new driver is somehow only activated after a user login, but I've got no idea. Of course, since there are no USB2 ports on this computer, the user doesn't have a keyboard or mouse to log in with, so the new driver is never used.

Made a bootable USB drive from the original Win7 DVD, with the USB3 drivers from the Intel site (using dismgui). This works as expected, and I can use it for Win7 installation and recovery on my new USB3 mobo. It's no use, though, since I want to use the old Win7 HDD

I know that dism has put the new drivers in the right place: 3 drivers in windows\system32\drivers, and the same ones in \windows\system32\DriverStore. This is exactly where they are located in my installation image on the USB stick.

Seems that you have already install the drivers, have you tried to go to Device Manager to check if there is any warnings on the device. If so, right click the device and choose to update the driver.Despite the USB3.0 driver that you should installed, you need to also install mouse and keyboard driver.

now put the card on your new motherboard, and plug the keyboard and mouse into that card. This will get you beyond the login, but it's possible that not much else will work. I had to put in an Ethernet card from the old system, and the old graphics card. I also ran Intel's tool to load drivers for the C236 chipset, but it didn't seem to help. After a few restarts it's all working as before.

MS Office wanted to go online to re-activate. It did this in a couple of seconds, automatically, with no prompting. I re-activated Windows from the control panel - again, a couple of seconds, no problem. So, it's possible, but a hassle.

You can use DISM to install or remove driver packages in an offline Windows or Windows PE image. You can either add or remove the driver packages directly by using the command prompt, or apply an unattended answer file to a mounted .wim, .ffu, .vhd, or .vhdx file.

When you use DISM to install a driver package to an offline image, the driver package is added to the driver store. When the image boots, Plug and Play (PnP) runs and associates the driver packages in the store to the corresponding devices on the computer.

To add driver packages to an offline image, you must use a technician computer running Windows 10 or later, Windows Server 2016 or later, or Windows PE for Windows 10 or later. Driver signature verification may fail when you add a driver to an offline image from a technician computer running any other operating system.

If you're adding driver packages to a Windows PE image, you can add them to the Windows PE image in the output folder you specified when you ran copype, for example: C:\WinPE_amd64\media\sources\boot.wim. This ensures that driver packages will be included in Windows PE each time you build Windows PE media from that folder.

Using /Recurse can be handy, but it's easy to bloat your image with it. Some driver packages include multiple .inf driver packages, which often share payload files from the same folder. During installation, each .inf driver package is expanded into a separate folder. Each individual folder has a copy of the payload files.

Check to see if the driver package was added. Driver packages added to the Windows image are named Oem*.inf. This guarantees unique naming for newly added driver packages. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.

All driver packages in the directory and subdirectories that are referenced in the answer file are added to the image. You should manage the answer file and these directories carefully to address concerns about increasing the size of the image with unnecessary driver packages.

If you need driver packages for Windows PE to see the local hard disk drive or a network, you must use the windowsPE configuration pass of an answer file to add driver packages to the Windows PE driver store. For more information, see Add Device Driver packages to Windows During Windows Setup.

Check to see if the driver package was added. Driver packages added to the Windows image are named Oem.inf. This guarantees unique naming for newly added driver packages. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.