Windows 7 UAC hardware prompt for mysterious driver

=Actual Problem=

See if there is a device stuck with 'Install Action' needed

Install Action problem
findstr /c:"Install Action" \\xxxxxxxx\c$\windows\inf\setup*

If there is you should see lines like this

\\xxxxxxxx\c$\windows\inf\setupapi.dev.log:    ven:                     Finish Install Action is needed 08:45:07.635 \\xxxxxxxx\c$\windows\inf\setupapi.dev.log:    ndv:      Device has a Finish Install Action that needs to be run.

Quicker way to see is look at USB and PCI devices that have 'Install Action' needed

reg query "\\xxxxxxxx\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI" /s /f "ConfigFlags" reg query "\\xxxxxxxx\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB" /s /f "ConfigFlags"

ConfigFlags should be all be DWORD 0x0's.

Example of problem with USB one.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_045E&PID_00CB\5&201fb416&0&2 ConfigFlags   REG_DWORD    0x20000

Thus the problem stems from VID_045E&PID_00CB as can be seen below, which corresponds to a "Microsoft Hardware USB Mouse", you can now skip to fix below or read on for some more info.


 * Note I just renamed the 64bit devcon.exe to devcon64.exe so I can have both versions and know which is which!

c:\>devcon64.exe -m:\\xxxxxxxx findall * | findstr /i "VID_045E&PID_00CB\5&201fb416&0&2" USB\VID_045E&PID_00CB\5&201FB416&0&2                       : Microsoft Hardware USB Mouse

If you wish to you can also find out what the corresponding inf is (shame windows doesnt have grep built in!). Sadly this has to go via psexec as of course devcon can't manage to do this query on a remote machine! If you dont care skip to resetting the reg below.

Z:\>psexec -ches \\xxxxxxxx devcon64.exe drivernodes *

Relevant part of output

USB\VID_045E&PID_00CB\5&201FB416&0&2 Name: Microsoft Hardware USB Mouse DriverNode #0: Inf file is C:\Windows\INF\oem244.inf Inf section is IPCdless_Install Driver description is Microsoft Hardware USB Mouse

Then look at oem244.inf (yours will have a different name this is machine dependant on what else has been installed), in this case it corresponds to ipcdless.inf

You can also find the original .inf in c:\Windows\System32\DriverStore\FileRepository\ipcdless.inf_amd64_neutral_635da1077258556d

Just to check this is inf contents

[MS.Mfg.NTAMD64.6.1] %DeviceDesc% = IPCdless_Install, USB\Vid_045E&Pid_0023 %DeviceDesc% = IPCdless_Install, USB\Vid_045E&Pid_0024  %DeviceDesc% = IPCdless_Install, USB\Vid_045E&Pid_00CB

Reset ConfigFlags to 0 to fix
This has to be done with psexec via System account as just a normal reg add will get 'access denied'.

USB
From above example

psexec -hes \\xxxxxxxx reg add "HKLM\SYSTEM\CurrentControlSet\Enum\USB\VID_045E&PID_00CB\5&201fb416&0&2" /v "ConfigFlags" /t REG_DWORD /d 0 /f

PCI
This example is the known issue with Radeon drivers

psexec -hes \\xxxxxxxx reg add "HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1002&DEV_6759&SUBSYS_3130103C&REV_00\4&3a87666f&0&0008" /v "ConfigFlags" /t REG_DWORD /d 0 /f

Other devices found causing this problem
Microsoft Mice that like triggering this I have found are; VID_045E&PID_00CB\5&201FB416&0&2 VID_045E&PID_0040\5&1a9117ce&0&3 VID_045E&PID_0040\5&1a9117ce&0&4

=References=

ATI Radeon problem