Is there a way to turn off the Found New Hardware Wizard, so that Windows will just automatically search its driver cache for good drivers when a hardware device is inserted, without asking for user input?

I've been searching everywhere and haven't been able to find an answer. Any help is greatly appreciated!

If the driver is signed that's what usually happens. No user intervention.

The following registry Keys enhance the behaviour of the Hardware Wizard.

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DriverSearching]
"DontSearchWindowsUpdate"=dword:00000001
"DontPromptForWindowsUpdate"=dword:00000001
"DontSearchCD"=dword:00000001
"DontSearchFloppies"=dword:00000001

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000000

[HKEY_USERS\.DEFAULT\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000000

Well, here's what's happening.

I am getting the Found New Hardware Wizard whenever I plug anything in that wasn't plugged in during the Setup. This is bad, because I'm switching keyboards and mice around and then I can't click Next!

If I could turn it OFF and have Windows just search, it would find what it wants. If I click Next on the wizard, then it finds what it wants and installs it automatically (without warning about the driver signing, because the drivers are signed).

I was originally using RyanVM's packs, nLite, and BTS DriverPacks. I am now testing each progressively, starting from a standard SP2 slipstream, to figure out where the problem gets introduced.

With plain SP2, I can plug in my usb keyboard and it installs totally unattended.

If I use nLite to integrate RyanVM's packs, the wizard pops up.

Starting over...

If I integrate RyanVM's packs by hand (with __integrate.exe and the file editing), my USB devices install totally unattended.

Good! Moving on..

If I use nLite at all, the wizard pops up.

Starting over...

I then re-integrated RyanVM by hand and slipstreamed BTS DriverPacks via Method 2. Wizard pops up.

At this very moment, I've re-slipstreamed BTS DPs via Method 1, and am installing Windows with that. It does appear that BOTH nLite and BTS DPs will cause this problem, though, which sucks, because I really wanted to use BTS DPs.

in my unattended setup the wizard also pops up during the RunOnceEX part...
does anybody has a solution for this?

I just recently discovered this board and got very interested in building an unattended XP installation media for myself...

Anyawy, this same annoying "feature" has now appeared in my setup as well. Right now I'm pretty clueless as to what exactly causes it and I haven't had too much time to troubleshoot it yet. I'm using the nLite 1.0 b5 to import RyanVM's 1.2.2 Full hotfix pack and 10-15 other hotfixes which are not included in the pack. Also to remove some stuff (not too much) from and tweak the setup. This worked fine at first, but evidently I did something somewhere to invoke this behaviour...

The Wizard first pops up to install some SoundBlaster-related drivers during when RunOnceEx is installing software. I might even be able to live with that since it doesn't really interfere and can be ignored, but where it gets particularly annoying is when it pops up for anything that wasn't plugged in during the installation -- even hard drives. First it asks to install drivers for the newly attached HD itself and then once for every partition that is found from the drive. This is clearly not acceptable.

I don't want to disable the wizard since that would probably just leave all new-found hardware driverless, just find how to restore its original behaviour. Gotta continue the tests when I get off work later...

Ok, after numerous tests I finally managed yesterday to install the nLightened (1.0b5) XP without the annoying wizard ever popping up...

What I did earlier with nLite was:

1. first import the RyanVM's hotfix pack without doing anything else at that time and close nLite.
2. then start nLite again and imported all other hotfixes -> close nLite
3. started nLite 3rd time, do remove/tweak/patch/unattended, and close nLite
4. added SI3112A RAID controller drivers manually and tweaked $OEM$ directories
5. started nLite and made an ISO
6. burn and install -> Wizard pops up

Yesterday I did 1-3. in one sitting, although only imported the RyanVM's pack and not the other hotfixes and closed nLite. Then again added SATA drivers and $OEM$ dirs and made the ISO with nLite. This time there was no Wizard. Now I just need to try to import the rest of the hotfixes and see what happens...

Hi everybody, one question about Hardware Wizard, i have used the tweak.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DriverSearching]
"DontSearchWindowsUpdate"=dword:00000001
"DontPromptForWindowsUpdate"=dword:00000001
"DontSearchCD"=dword:00000001
"DontSearchFloppies"=dword:00000001

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000000

[HKEY_USERS\.DEFAULT\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000000

but the wizard shows me more than one inf file to use to install hardware. Maybe this the reason why the wizard ask me to select one inf file, because it has more than one file to select ????

Here's how I got this to work:

Manually integrate RyanVM
Don't use nLite at all (I couldn't get it to work, anyway, and it was quicker to do the things I needed manually than to mess around with it)
Use BTS DPs with Method 1 (Method 2 was causing the Wizard to appear, Method 1 does not appear to)
Change production folders how I want, add modified system files, etc.

thanks.

Please I use xpcreate. Would you mind to explain me easily what I have to do. My native spanish. thanks again

Couldn't honestly say. I've never seen/used XPCREATE -- still on the waiting list.

I just use RyanVM's latest pack and then manually integrate the remaining updates.

I like to use nLite to remove and tweak some stuff. Just doing everything in one go (except the ISO creation, it-of course-has no affect) seemed to resolve my Wizard problem.

GO INTO DEVICE MANAGER

GO TO VIEW

SELECT SHOW HIDDEN DEVICES

CLICK THE PLUS SIGN NEXT TO PRINTERS....

IS THEIR AN EXCLAMATION POINT ? if so select properties check and see what it says
TRY SELECTING DISABLE from the properties of it OR SELECT UNINSTALL SEE IF THE PRINTER STILL WORKS...

Control chaos??

use nforce slipstreaming driver inside my unattended dvd...
after installation and 1st time get in windows....
the popup will said found cd-rom drive... need click finish....
restart and second popup... found disk drive.... need click finish....

dunno how to get rid of it...


Problem fix... who carez =)

UPnPDev.cmd


It's how i install external modem that wasn't plugged in during the Setup.
Drivers (not digitally signed) are installed first with Unlimited number of drivers schalti method & Pyron tool (post #4).
UPnpDev.cmd is run to update registry
Restart or shutdown box
Plug external modem and power up
let PnP detection install my device ('Found New Hardware Wizard' windows popup but automatically disappears when detection is done by RunOnceEx instruction).

I looked for answers on how to suppress the Found New Hardware Wizard dialog, but found little that worked. So I wrote a little VBS script that uses the taskkill command to kill windows where windowtitle eq Found New Hardware Wizard. I found this approach to be preferable to all the others tried to this point.

So I wanted to post it for what its worth. If you have a new hardware wizard giving you grief and new to kill it, this may be what you seek.

The script is written to take two inputs, one mandatory and one optional. The mandatory input is for a timeout value (e.g., /TimeOut:20). In other words, the amount of time, in seconds, the thing will run. The second input, the /Name:[yourtexthere], is optional and can be used to help you track when you dispatched this script. This info is written into the WizKilla.vbs log file. For example, lets say when installing the WLAN driver the Found New Hardware Wizard is giving you grief. Simply dispatch the WizKilla.vbs immediately before launching your unattended driver install. Use the following syntax:

cscript.exe //nologo wizkilla.vbs /Timeout:20 /Name:WLAN


---- Begin WizKilla.vbs -----
'-----------------------------------------------------------------------------
' This script Loops a set number of times based on user supplied input value
' Where each loop is eqaul to 1 second in duration.
' During each loop a taskkill command is executed to kill the window(s)
' titled 'Found New Hardware Wizard'
'
' Date: 08.21.06
' Author: Bruce Inciardi
' Revision: original
'-----------------------------------------------------------------------------
strComputer = "."

Const ForAppending = 8
Set oArgs = wscript.Arguments

Set colNamedArguments = WScript.Arguments.Named
strName = colNamedArguments.Item("Name")
strTimeout = colNamedArguments.Item("Timeout")


Set WshNetwork = WScript.CreateObject("WScript.Network")
Set WshShell = WScript.CreateObject("WScript.Shell")
compname = WshNetwork.ComputerName

set FSO = CreateObject("Scripting.FileSystemObject")
strLogFile = "\LOGS\" & Split(WScript.ScriptName, ".")(0) & ".log"
pathtologfile = WshShell.ExpandEnvironmentStrings _
("%SystemRoot%" & strlogfile)
If FSO.FileExists(PathToLogFile) Then
'' Wscript.Echo "File exist."
Set objLogFile = FSO.OpenTextFile(pathtologfile, ForAppending)
Else
'' Wscript.Echo "File does not exist."
Set objLogFile = FSO.CreateTextFile(pathtologfile, TRUE)
End If

objLogFile.WriteLine(Now & ": " & WScript.ScriptFullName & " Started." & vbCrLf)
objLogFile.WriteLine("Current Computer Name: " & compname)
objLogFile.WriteLine("Log File/Path: " & pathtologfile)
objLogFile.WriteLine("Script loops 'x' times based on user provided input and kills 'New Hardware Found Wizard' dialogs." & vbCrLf)

If Not colNamedArguments.Exists("TimeOut") Then
objLogFile.WriteLine("Input in error")
objLogFile.WriteLine("Correct Usage:")
objLogFile.WriteLine("cscript WizKilla.vbs /TimeOut:10 /Name:" & Chr(34) & "Intel WLAN" & Chr(34))
Wscript.quit(0)
End If

iTimeout = strTimeout
iTimeout=CInt(strTimeout)

objLogFile.WriteLine("Launched with parms: /Timeout:" & strTimeout & " /Name:" & strName & vbCrLf)

Wscript.Echo "Shhhh, be vewy qwiet..."
Wscript.Echo "...I'm hunting Found New Hardware Wizard Dialogs."

iLoop = 0
Do Until iLoop > iTimeout
iLoop=iLoop+1
WScript.Sleep 1000
If iLoop > iTimeout Then
Exit Do
Else
' "Perform taskkill cmd here"
killacmd = "taskkill /FI " & Chr(34) & "WINDOWTITLE eq Found New Hardware Wizard" & Chr(34)
Set oExecObject = WshShell.Exec("%comspec% /c " & killacmd)
Do Until oExecObject.StdOut.AtEndOfStream
strLine = oExecObject.StdOut.ReadLine()
if (Instr(strLine,"INFO:")<>0) Or (Instr(strLine,"SUCCESS:")<>0) Then
If Instr(strLine,"SUCCESS:")<>0 Then Wscript.Echo "Got One!"
objLogFile.WriteLine(Now & ": (" & iLoop & ") " & strLine)
End If
Loop
End If
Loop

objLogFile.WriteLine("Script Completed; Timeoutvalue reached" & vbCrLf)

objLogFile.WriteLine(Now & ":" & vbTab & WScript.ScriptFullName & " Ended." & vbCrLf)

---- End WizKilla.vbs -----

Hope this helps someone.

Bruce

Just come across this, it turns out that it thinks usbstor.sys is unsigned -the one I had mismatched the one listed in usbstor.inf - just copied them from a good setup dir