Not able to install using INF

hello,
currently i am working on keyboard upper filter driver and was able to install using Devcon and but when installing using inf right click it is not getting installed. Below is final logs form setupapi

Is that driver is test signed do i need to see about driver ranking if so how to proceed , I have reading online MSDN but no help. So please provided any solution…

thanks in advance

Search options: 0x00000081

(setup log content removed at request of OP)

<<< Section end 2017/07/07 11:20:05.427
<<< [Exit status: FAILURE(0x00000103)]

The driver package is not considered signed. Did you include the inf in the list of files the catalog verifies? Is the catalog file in the same directory as the inf?

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com xxxxx@lists.osr.com
Sent: Friday, July 7, 2017 1:50:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Not able to install using INF

hello,
currently i am working on keyboard upper filter driver and was able to install using Devcon and but when installing using inf right click it is not getting installed. Below is final logs form setupapi

Is that driver is test signed do i need to see about driver ranking if so how to proceed , I have reading online MSDN but no help. So please provided any solution…

thanks in advance

Search options: 0x00000081

(setup log content removed at request of OP)

<<< Section end 2017/07/07 11:20:05.427
<<< [Exit status: FAILURE(0x00000103)]


NTDEV is sponsored by OSR

xxxxx@gmail.com xxxxx@lists.osr.com wrote:

currently i am working on keyboard upper filter driver and was able to install using Devcon and but when installing using inf right click it is not getting installed. Below is final logs form setupapi

EXACTLY how did you install it using “devcon”? When you say “inf right
click”, do you mean you right-clicked the INF in Explorer and picked
“Install”, or do you mean you did “Update Driver” inside Device
Manager? Those two methods trigger ENTIRELY different processes. The
Explorer right-click thing is essentially a cheap batch file; it does
file copies and registry entries, but it’s not an installation in the
PnP sense. “Devcon” is used for full PnP installs.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

@Tim

Actually we changed the right-click->install behavior for Win8. Right-click->install first does the old stuff you’re talking about (processing the [DefaultInstall] section), then it calls DiInstallDriver to perform a full PNP driver install. Update driver ends up calling DiInstallDevice (more or less), so they end up going down very similar codepaths.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 7, 2017 10:24 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not able to install using INF

xxxxx@gmail.com xxxxx@lists.osr.com wrote:
> currently i am working on keyboard upper filter driver and was able to
> install using Devcon and but when installing using inf right click it
> is not getting installed. Below is final logs form setupapi

EXACTLY how did you install it using “devcon”? When you say “inf right click”, do you mean you right-clicked the INF in Explorer and picked “Install”, or do you mean you did “Update Driver” inside Device Manager? Those two methods trigger ENTIRELY different processes. The Explorer right-click thing is essentially a cheap batch file; it does file copies and registry entries, but it’s not an installation in the PnP sense. “Devcon” is used for full PnP installs.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

The devcon command line is still an important piece of data. If you are calling devcon install […], you are creating a root enumerated device whose hardware ID probably doesn’t match on an inbox INF so your unsigned driver will be the only match, and once the user consents, installed as there is no signed INF to compete against it in the ranking process. If you are using devcon update […] (which is the same code path as right click install as Zac describes) and getting different behavior for the same package, you should look at setupapi.dev.log in both instances and see why the system is behaving differently.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Zac Lockard
Sent: Friday, July 7, 2017 11:13 AM
To: Windows System Software Devs Interest List
Cc: Zac Lockard
Subject: RE: [ntdev] Not able to install using INF

@Tim

Actually we changed the right-click->install behavior for Win8. Right-click->install first does the old stuff you’re talking about (processing the [DefaultInstall] section), then it calls DiInstallDriver to perform a full PNP driver install. Update driver ends up calling DiInstallDevice (more or less), so they end up going down very similar codepaths.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 7, 2017 10:24 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not able to install using INF

xxxxx@gmail.com xxxxx@lists.osr.com wrote:
> currently i am working on keyboard upper filter driver and was able to
> install using Devcon and but when installing using inf right click it
> is not getting installed. Below is final logs form setupapi

EXACTLY how did you install it using “devcon”? When you say “inf right click”, do you mean you right-clicked the INF in Explorer and picked “Install”, or do you mean you did “Update Driver” inside Device Manager? Those two methods trigger ENTIRELY different processes. The Explorer right-click thing is essentially a cheap batch file; it does file copies and registry entries, but it’s not an installation in the PnP sense. “Devcon” is used for full PnP installs.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:></https:></https:></https:>

Zac Lockard wrote:

Actually we changed the right-click->install behavior for Win8. Right-click->install first does the old stuff you’re talking about (processing the [DefaultInstall] section), then it calls DiInstallDriver to perform a full PNP driver install. Update driver ends up calling DiInstallDevice (more or less), so they end up going down very similar codepaths.

How can it do that, if it doesn’t have a PnP hardware ID to install
against?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

It will install against all devices that the INF applies to, assuming it outranks the existing driver - so it may install against many (or no) devices.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 7, 2017 1:07 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not able to install using INF

Zac Lockard wrote:
> Actually we changed the right-click->install behavior for Win8. Right-click->install first does the old stuff you’re talking about (processing the [DefaultInstall] section), then it calls DiInstallDriver to perform a full PNP driver install. Update driver ends up calling DiInstallDevice (more or less), so they end up going down very similar codepaths.

How can it do that, if it doesn’t have a PnP hardware ID to install against?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

Zac Lockard wrote:

It will install against all devices that the INF applies to, assuming it outranks the existing driver - so it may install against many (or no) devices.

I’m still not sure I know what that means. Are you saying that, after
running [DefaultInstall], it now does a PnP pre-install into the driver
store, and then does a “scan for hardware changes”? That’s a very
significant change in behavior, and I can imagine this might cause great
surprise in some cases.

I guess I will have to try this, because in my mind, that behavior might
eliminate the need for DPInst.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

It does the following:
-Run the [DefaultInstall] logic (call setupapi!InstallHInfSection on it) as always
-Calls DiInstallDriver on the INF (https://msdn.microsoft.com/library/windows/hardware/ff544717)

DiInstallDriver will:
-Import the driver into the driverstore
-Identify all devices on the system that have a hardware ID match with the INF
-For each of the identified devices, install the INF if it outranks the currently installed one

It is a rather big change in behavior, yes, but in my mind it’s more in line with what users would expect when clicking install.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, July 7, 2017 1:43 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not able to install using INF

Zac Lockard wrote:
> It will install against all devices that the INF applies to, assuming it outranks the existing driver - so it may install against many (or no) devices.

I’m still not sure I know what that means. Are you saying that, after running [DefaultInstall], it now does a PnP pre-install into the driver store, and then does a “scan for hardware changes”? That’s a very significant change in behavior, and I can imagine this might cause great surprise in some cases.

I guess I will have to try this, because in my mind, that behavior might eliminate the need for DPInst.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

Thanks for the comments, But still dint resolve the issue , here i give little more info.

Using Devcon:- devcon.exe update c:\somepath\mydriver.inf ACPI\MyDevicehardwareId
and result is successfully installed and working as expected.

When i say right click install(selecting installing option form menu) or from device Manager update: its failing to install the driver. From setupapi.log i see the last step in inf log “DIF_SELECTBESTCOMPATDRV” is been called and inbox driver keyboard.inf is been installed.
{Build Driver List - exit(0x00000000)} 11:20:05.350

(setup log content removed at request of OP)

<<< Section end 2017/07/07 11:20:05.427
<<< [Exit status: FAILURE(0x00000103)]

So i would like to know if this is the behavior i may not install the driver from windows update. as i am thinking windows update may use same mechanism like right click install. I also tried installing pnputil i got message as installed successfully but driver.sys files where not copied in stack. Thank you

This is why:
dvi: Rank - 0x80ff0001
dvi: Signer Score - Not digitally signed

PNP doesn’t consider the package signed, so it won’t install it over a signed one (the inbox driver). While devcon will install the specified driver on the device regardless, right-click->install, pnputil, and Windows Update will only install it if it’s the best ranked driver for the device. So you’ll have to figure out why it’s not considered signed.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com xxxxx@lists.osr.com
Sent: Monday, July 10, 2017 11:08 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Not able to install using INF

Thanks for the comments, But still dint resolve the issue , here i give little more info.

Using Devcon:- devcon.exe update c:\somepath\mydriver.inf ACPI\MyDevicehardwareId and result is successfully installed and working as expected.

When i say right click install(selecting installing option form menu) or from device Manager update: its failing to install the driver. From setupapi.log i see the last step in inf log “DIF_SELECTBESTCOMPATDRV” is been called and inbox driver keyboard.inf is been installed.

(setup log content removed at request of OP)

ndv: {Update Device Driver - exit(00000103)} <<< Section end 2017/07/07 11:20:05.427 <<< [Exit status: FAILURE(0x00000103)]

So i would like to know if this is the behavior i may not install the driver from windows update. as i am thinking windows update may use same mechanism like right click install. I also tried installing pnputil i got message as installed successfully but driver.sys files where not copied in stack. Thank you


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>