MVP Custom WinPE build not picking up configuration change
My "production" PC is Ehternet connected so I don't need wireless support, but I sometimes use it for testing so I use a USB WiFi adapter. Today I replaced an old N wireless adapter with an AC adapter and deleted the old adapter from Windows.
I rebuilt my custom WinPE recovery medium to see if it would pick up the change, booted it up, and was told there was no WiFi adapter on my PC. After booting back into Windows I saw that the extracted drivers still contained my old adapter's driver, not the new one. All the driver directories had a timestamp from last December. Surprisingly, the Double Driver directory had a timestamp from today so I guess the builder touched the directory but neither it nor DD touched the contents.
It might be a good idea to have the builder ask if there has been a hardware reconfiguration since the last time the builder was run on this computer and invoke DD if the answer is "yes".
Do I just delete the DDBackup directory and rerun the builder? (I've saved DDBackup... just in case the answer is "no".)
Update:
Deleting the DDbackup directory did cause DD to run, but it did not extract the driver for my new wireless adapter. Odd. Last December it extracted the driver for my old wireless adapter, and my new adapter seems to be working so I'm sure the driver is present.
Maybe I'll play around with DD (outside of the Builder) and see what's going on.
I ran DD outside of the builder. It had my new adapter in its list of devices but did not have it selected for backup. Maybe that is why it did not extract the driver when invoked by the builder. I selected only that device, did a backup, copied the extracted driver directory into the builder's Drivers_Custom\x64\ directory and rebuilt the recovery medium.
I can see in the log where the builder inserted the driver, but when booting the recovery medium it still said there was no wireless interface. Odd.
I think I'll try again with the adapter plugged into a USB 2 port. It's a USB 3.0 device, but I don't need to run it that way.
Patrick O'Keefe wrote:I ran DD outside of the builder. It had my new adapter in its list of devices but did not have it selected for backup. Maybe that is why it did not extract the driver when invoked by the builder. I selected only that device, did a backup, copied the extracted driver directory into the builder's Drivers_Custom\x64\ directory and rebuilt the recovery medium.
I can see in the log where the builder inserted the driver, but when booting the recovery medium it still said there was no wireless interface. Odd.
I think I'll try again with the adapter plugged into a USB 2 port. It's a USB 3.0 device, but I don't need to run it that way.
Nope. That didn't work. It just isn't seeing the new wireless adapter.
I finally got it working. A CD containing a driver and utilities came with adapter. The driver is several years older than the one Windows found and used with the adapter. II gave the WinPE Builder the driver from the CD and the recovery medium can now see the adapter.
Odd. The driver Window found obviously works on the full Windows but apparently not in WinPE.