I’ve developed a class upper filter keyboard driver using KMDF for Windows XP that filters PS/2 keyboards. After our installation program installs the driver we ask the admin to reboot. If after reboot a non-admin user logs in then a “New hardware found” message is displayed (shows our raw pdo device name - Keyboard_Filter_01) and the user is prompted to provide admin credentials to complete the install.
What’s also interesting is that the filter driver is already installed a working at the time of the above message and prompt. If the user “cancels” the credentials prompt dialog our product works just fine. If they then log out and in they are not prompted again. If they restart Windows and login then they are prompted again.
Is this to be expected or have I done something wrong?
Everything works fine if the admin logs in after reboot. Subsequent log ins by the non-admin user do not result in any device install prompts even after Windows startup.
Yes, this is expected b/c your driver package is unsigned. If it were signed, a normal user would not need to elevate to admin to install the INF
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@panologic.com
Sent: Wednesday, September 17, 2008 10:44 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Keyboard filter driver install requires reboot and then admin login
I’ve developed a class upper filter keyboard driver using KMDF for Windows XP that filters PS/2 keyboards. After our installation program installs the driver we ask the admin to reboot. If after reboot a non-admin user logs in then a “New hardware found” message is displayed (shows our raw pdo device name - Keyboard_Filter_01) and the user is prompted to provide admin credentials to complete the install.
What’s also interesting is that the filter driver is already installed a working at the time of the above message and prompt. If the user “cancels” the credentials prompt dialog our product works just fine. If they then log out and in they are not prompted again. If they restart Windows and login then they are prompted again.
Is this to be expected or have I done something wrong?
Everything works fine if the admin logs in after reboot. Subsequent log ins by the non-admin user do not result in any device install prompts even after Windows startup.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Thanks Doron for the quick reply!
Okay, but if the non-admin user does not provide admin credentials and just dismisses the dialog the driver still works fine in that user’s session so obviously it is installed anyway. Seems quite strange to prompt for something that is not needed, don’t you agree?
Is it possible to disable this credential prompt by configuring the XP Driver Signing Options via Control Panel to “Ignore” and checking the “Make this action the system default” field in the “Administrator Option” group box?
For completeness just want to add that we’ve modeled our KMDF class filter install implementation on the “devcon ClassFilter” command and wdffltrinstall sample available from OSR.
My guess is your PDO is a raw PDO which means that it can run w/out an INF install. Instead of hacking the system to fit your driver install, just get it signed.
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@panologic.com
Sent: Wednesday, September 17, 2008 1:17 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Keyboard filter driver install requires reboot and then admin login
Thanks Doron for the quick reply!
Okay, but if the non-admin user does not provide admin credentials and just dismisses the dialog the driver still works fine in that user’s session so obviously it is installed anyway. Seems quite strange to prompt for something that is not needed, don’t you agree?
Is it possible to disable this credential prompt by configuring the XP Driver Signing Options via Control Panel to “Ignore” and checking the “Make this action the system default” field in the “Administrator Option” group box?
For completeness just want to add that we’ve modeled our KMDF class filter install implementation on the “devcon ClassFilter” command and wdffltrinstall sample available from OSR.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer