May 11, 201016 yr Hi, I have been googling for the last week and have yet to find a solutionCurrently we have a Base Windows 7 WIM that gets applied to a machine, we also have a Seperate Wim for each PC model that contains drivers specific to that model, this gets extracted to c:\drivers before the Base WIM gets applied. This is all fine.However, some of the drivers are unsigned, so we get the Unsigned Drivers warning box.We use HP Desktops and have a range of approx 20 diff models currently, but this is always changing - hence we don't want to inject drivers in the Base windows 7 wim.my question is, does anyone know how to get the pnpunattend.exe to skip displaying the message if it encounters an unsigned driver?or another method of installing drivers?fyi...I captured the Wim with the /audit mode, then I have a Driverpath in Microsoft-Windows-PnpCustomizationsNonWinPE and then I have a RunSync command sysprep /oobe /reboot in "audit user"
May 11, 201016 yr In general all HP models supporting Windows 7 have signed drivers, but you can create a certificate and sign the driver(s) your self... problem solved
May 11, 201016 yr Hi, I have been googling for the last week and have yet to find a solutionCurrently we have a Base Windows 7 WIM that gets applied to a machine, we also have a Seperate Wim for each PC model that contains drivers specific to that model, this gets extracted to c:\drivers before the Base WIM gets applied. This is all fine.However, some of the drivers are unsigned, so we get the Unsigned Drivers warning box.We use HP Desktops and have a range of approx 20 diff models currently, but this is always changing - hence we don't want to inject drivers in the Base windows 7 wim.my question is, does anyone know how to get the pnpunattend.exe to skip displaying the message if it encounters an unsigned driver?or another method of installing drivers?fyi...I captured the Wim with the /audit mode, then I have a Driverpath in Microsoft-Windows-PnpCustomizationsNonWinPE and then I have a RunSync command sysprep /oobe /reboot in "audit user"This is what we did, inject all drivers for all models into the Install.wim dir and winodws will install the correct drivers for each model you install it on, then make a base.wim for you pc models and role out...
May 12, 201016 yr Author In general all HP models supporting Windows 7 have signed drivers, but you can create a certificate and sign the driver(s) your self... problem solved Yeah, the drivers on the main machine I am using for test creation that are causing issues are a couple of drivers for the i5 chip, the NIC and the added on NVidia Quadro FX 380 Video Card...Could you point me to a guide to self signing drivers?
May 12, 201016 yr Author Hi, I have been googling for the last week and have yet to find a solutionCurrently we have a Base Windows 7 WIM that gets applied to a machine, we also have a Seperate Wim for each PC model that contains drivers specific to that model, this gets extracted to c:\drivers before the Base WIM gets applied. This is all fine.However, some of the drivers are unsigned, so we get the Unsigned Drivers warning box.We use HP Desktops and have a range of approx 20 diff models currently, but this is always changing - hence we don't want to inject drivers in the Base windows 7 wim.my question is, does anyone know how to get the pnpunattend.exe to skip displaying the message if it encounters an unsigned driver?or another method of installing drivers?fyi...I captured the Wim with the /audit mode, then I have a Driverpath in Microsoft-Windows-PnpCustomizationsNonWinPE and then I have a RunSync command sysprep /oobe /reboot in "audit user"This is what we did, inject all drivers for all models into the Install.wim dir and winodws will install the correct drivers for each model you install it on, then make a base.wim for you pc models and role out...Yeah thats not really feasible for us. we don't want to have all drivers in the main WIM. Waste of space
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now