Driver install brings up Found New Hardware Wizard when it shouldn&#39

[solidaltar]

Hello everyone, I have an interesting problem that I couldn't find an answer for via Google.

I have a Lenovo M57 with an Intel 82566DM-2 onboard gigabit ethernet controller. I'm using Windows XP SP3.

I have the path for the driver for this in the proper DevicePath key.

However, when I Uninstall the device in Windows and Rescan for devices, it brings up the Found New Hardware Wizard. I don't understand why this is happening, since if I click to install everything automatically it finds the driver and installs it. I'm not specifying a path.

Why is Windows displaying the Found New Hardware Wizard when it an detect the driver and install it automatically after I hit Next?

Driver Signing is disabled.

Even worse, this problem is preventing the driver from being used during Sysprep, making it so I can't join a domain with a preexisting computer name.

Ideas?

[dochowell]

Hello everyone, I have an interesting problem that I couldn't find an answer for via Google.

I have a Lenovo M57 with an Intel 82566DM-2 onboard gigabit ethernet controller. I'm using Windows XP SP3.

I have the path for the driver for this in the proper DevicePath key.

However, when I Uninstall the device in Windows and Rescan for devices, it brings up the Found New Hardware Wizard. I don't understand why this is happening, since if I click to install everything automatically it finds the driver and installs it. I'm not specifying a path.

Why is Windows displaying the Found New Hardware Wizard when it an detect the driver and install it automatically after I hit Next?

Driver Signing is disabled.

Even worse, this problem is preventing the driver from being used during Sysprep, making it so I can't join a domain with a preexisting computer name.

Ideas?

I would expect to see the wizard here, since you're manually rescanning for hardware. No wizard in mini-setup mode on first boot. There is a line in Sysprep.INF that should reflect your DriverPath reg value, relative from the root of the boot drive. Both must match. So for /HKLM/.../DevicePath: "%SystemRoot%\drivers\network;%SystemRoot%\drivers\video", but for Sysprep.INF: "drivers/network;drivers/video...". Question: if you click thru the wizard, does Windows install the drivers normally, or does it give any warnings or errors?

[solidaltar]

Ok, I believe found the answer to the problem.

This problem will occur when:

-You run sysprep

-You allow Minisetup to start but do not go all the way through

-You close Minisetup and restart

-You go through Minisetup and get to the desktop

Basically, I have a WDS server that I was going to upload to, so I told Sysprep to restart. However, I missed the prompt to hit F12 to boot via PXE. So it started into Sysprep. I realized my mistake and exited out of Sysprep, which restarted the computer.

After this point I had problems with drivers not installing automatically.

Edited May 19, 2010 by solidaltar