win7PE SE load drivers at startup does not work

Hello!

I'm building a win7PE SE x32 , I'm trying to load drivers at startup but it does not work!  Selecting the option "load" at startup for the "Driver Integration" script and for the Driver Package Installer script has not solved the problem.

In Components go check HwPNP. Then check on that screen "Autorun HwPNP on startup" and for WPEint.

Then do your build.

After the build place the drivers in the WindowsPESE\Target\Win7PESE\Windows\System32\drivers folder of your Target build folder for Win7PE and HwPNP should find and load the drivers for you automatically on boot.

Lastly goto Finals > PostConfig and do "Create new target image and iso"

This will rebuild your .wim and iso file and when you boot this time your drivers should automatically load.

----------------------

You can also use command "HWPnP -all" if the auto startup feature isnt working correctly.

In Components go check HwPNP. Then check on that screen "Autorun HwPNP on startup" and for WPEint.

Then do your build.

After the build place the drivers in the WindowsPESE\Target\Win7PESE\Windows\System32\drivers folder of your Target build folder for Win7PE and HwPNP should find and load the drivers for you automatically on boot.

Lastly goto Finals > PostConfig and do "Create new target image and iso"

This will rebuild your .wim and iso file and when you boot this time your drivers should automatically load.

----------------------

You can also use command "HWPnP -all" if the auto startup feature isnt working correctly.

Is it obligatory to autorun HwPNP so that all necessary drivers were installed? Shouldn't WinPE load drivers itself on boot?
The fact is that HwPNP takes a very long time to find all drivers for hardware.
If it's no way to avoid using third-party software to install drivers, I would rather use zPNP, it does it's a lot faster that HwPNP. But an index file should be created once. More info at http://nikzzzz.winbuilder.net/index.php?dir=Files%2FzPNP%2F

Actually, the Driver Integration seems to work strange. For example, I don't use the "USB 3.0 Support" plugin in my Win7PESE x86, preferring to add USB 3.0 drivers via the "Driver Integration" plugin. Network and card readers drivers are also added by the latter. However, when my Win7PE boots, I find that the Ethernet driver is not installed while the USB 3.0 controller is working fine with the driver I added via the "Driver Integration" plugin.

Can anybody elucidate what's happening?

Can anybody elucidate what's happening?

It is known issue:

Sometimes driver integration that requires nice info at appropriate .inf of driver not suitable to dism.exe to automatically add to build...
shortly: bad written .inf 
or complex driver...

After boot options:
"Driver Integration"\'Load drivers at Startup", Hwpnp, zPNP and DriverImportPE (Dipe) can also fail on such cases... ,
 well zPNP designed for NT5x where dism.exe was not available at that times .....




when you figure out such thing, you need to find missing things and add project via plugin,
 and share around http://theoven.org/index.php?board=9.0 

Tips:
Utils\PC Packed -> e button at right-bottom -> create new empty plugin
Utils\RegCPE -> convert .reg to plugin format




+
also, you may need to double (or triple) run "driver after integration" ,
 on some cases where driver depends another driver installed first....

I work on lots of different machines and can never be sure of the hardware installed. I found a simple way to add drivers automatically on boot with no intervention on my part. Put the attached script in  Win7PESE 82 / Projects/ Drivers folder and build as usual, including copying to your flash drive. If your only concerned with 1 or 2 machines use something like Double Driver and backup your drivers and drop them in the flash drive / Programs / Driver Package Installer folder and boot it up, Your hardware is detected and the correct driver installed. I have Audio x86,Chipset x86, Mass Storage x86, Graphics Mobile x86, Graphics x86 (both A & B) WLAN x86 from Driverpacks.net  and for Network Drivers from 3dpchip.com,  it is rare indeed that I'm missing a driver.

It is known issue:

Sometimes driver integration that requires nice info at appropriate .inf of driver not suitable to dism.exe to automatically add to build...
shortly: bad written .inf 
or complex driver...

After boot options:
"Driver Integration"\'Load drivers at Startup", Hwpnp, zPNP and DriverImportPE (Dipe) can also fail on such cases... ,
 well zPNP designed for NT5x where dism.exe was not available at that times .....

However, I found zPNP a best solution so far (haven't tested Boxer's plugin yet). It works like charm and easily detects my WLAN, Ethernet and Card reader and installs appropriate drivers.

Regarding driver integration that fails due to a complex driver or bad INF - it's really strange, my Ethernet driver is integrated in Win7PE, but not installed on boot. If I install the driver automatically via the Device Manager, it starts working.

I work on lots of different machines and can never be sure of the hardware installed. I found a simple way to add drivers automatically on boot with no intervention on my part. Put the attached script in  Win7PESE 82 / Projects/ Drivers folder and build as usual, including copying to your flash drive. If your only concerned with 1 or 2 machines use something like Double Driver and backup your drivers and drop them in the flash drive / Programs / Driver Package Installer folder and boot it up, Your hardware is detected and the correct driver installed. I have Audio x86,Chipset x86, Mass Storage x86, Graphics Mobile x86, Graphics x86 (both A & B) WLAN x86 from Driverpacks.net  and for Network Drivers from 3dpchip.com,  it is rare indeed that I'm missing a driver.

boxer, is your plugin compatible with Win7PE x64?

However, I found zPNP a best solution so far (haven't tested Boxer's plugin yet). It works like charm and easily detects my WLAN, Ethernet and Card reader and installs appropriate drivers.

nice to hear zPNP works on SE

Regarding driver integration that fails due to a complex driver or bad INF - it's really strange, my Ethernet driver is integrated in Win7PE, but not installed on boot. If I install the driver automatically via the Device Manager, it starts working.

Device Manager works different than dism ;)

Kvark, Driver Package Installer (DPINST) is a Microsoft product available in 32 or 64 bit, the .xml remains the same. As you know, drivers can be a pain in the keister, this solution provides the builder with the ability to drag and drop driver packages into their flash drive rather than integrating them into the boot.wim, removing them is also effortless.

Gig's of drivers available at boot time make Win7PE SE a pleasure to work with, I can pretty much walk up to to any machine, boot from flash and enjoy native resolution and networking. In those rare cases where a driver is missing, and the machine is bootable after I'm done with my repair, I'll snatch that driver for my collection. It's just that easy.

Kvark, Driver Package Installer (DPINST) is a Microsoft product available in 32 or 64 bit, the .xml remains the same. As you know, drivers can be a pain in the keister, this solution provides the builder with the ability to drag and drop driver packages into their flash drive rather than integrating them into the boot.wim, removing them is also effortless.

Gig's of drivers available at boot time make Win7PE SE a pleasure to work with, I can pretty much walk up to to any machine, boot from flash and enjoy native resolution and networking. In those rare cases where a driver is missing, and the machine is bootable after I'm done with my repair, I'll snatch that driver for my collection. It's just that easy.

Yes, I've already found both x86 and x64 versions of DPInst. In fact, there's no need to add the DPInst script to the project, it's sufficient to autostart DPInst.exe.

On the downside, DPInst doesn't display any progress of it's work if the tag <quietInstall/> is removed from DPInst.xml, the Wizard will popup, which is not convenient.

Additionally, DPInst cannot be used for USB 3.0 and storage drivers 'cause they require reboot after install.