Hello Mike, in this case we recommend creating two installation images, one for Intel® 7 Series Chipset and the other one for Intel® 8/9 Series Chipset.
For now, I have found a workaround for Windows PE (a script will detect the PC model and load the appropriate drivers), but for Windows itself this is still an issue. I am looking into workarounds for Windows at this time.
I don't have the option of creating separate images. Our deployment scenario involves giving our end-users an image and cannot require any steps on their part to setup the machine. That means no selecting which image to use nor installing a driver on their own.
Ultimately, I would like to know if there is any possibility for Intel to update the driver packages with the appropriate hardware IDs?
1 of 1 people found this helpful
Your suggestion has been forwarded to the appropriate support department so it can be taken into consideration for future releases.
I encounter exactly the same problem (I'm glad someone else noticed this problem !). An unified driver would be appreciable or a clear segmentation based on HardwareID between packages.
I would like to know if the following workaround would be helpful (not tested yet) ? I would like to run the setup packages (through command line) first from the 7-Series, then after the 8/9-Series during the OOBE pass (by using synchronous commands in the FirstLogonCommands node). Is there a good idea to avoid the HardwareID conflict ?
I register here just to say "Thank you very much!". I've encounter same problem while imaging win7 for HP Compaq 8300 (7 series chipset) and HP Elite 800 G1 (8 series chipset). The hardware ID workaround is worked pefrect! I've integrated usb 3.0 drivers using DISM utility with /ForceUnsigned and there is no more BSOD during OOBE, driver installed correctly on bouth models.
And yes, unifed, or corrected drivers would be nice!