devcon failed.

Hagen

I am trying to bringup an older test project which installs a root enumerated test driver.

On my current Windows 10 test machine devcon with admin rights fails with an incredibly informative error:

devcon install my_testl.inf my_test
devcon failed.

setupapi.dev.log does not get touched.
Is devcon still be able to install something under Windows 10? Or, is there an alternative to install a root enumerated driver? (My build process always does a complete chain including building an .msi, but I believe its a bit cumbersome trying to install this type of driver with wixtoolsets difx.)

Test wise the driver currently matches against an arbitrary free device node, but I would like to get it to install again as root enumerated device.

Thanks, and cheers,
Hagen.

Doron_Holan

The beauty of devcon is that you have the source. Build a private and see where it is failing. The tool works on win10.

As an aside, difx has been deprecated since at least win8. Furthermore, it won't work in certain win10 scenarios (such as declaring a win10 build floor in the inf).

d

Bent from my phone
________________________________
From: [email protected] on behalf of [email protected]
Sent: Saturday, February 3, 2018 11:50:41 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] devcon failed.

I am trying to bringup an older test project which installs a root enumerated test driver.

On my current Windows 10 test machine devcon with admin rights fails with an incredibly informative error:

devcon install my_testl.inf my_test
devcon failed.

setupapi.dev.log does not get touched.
Is devcon still be able to install something under Windows 10? Or, is there an alternative to install a root enumerated driver? (My build process always does a complete chain including building an .msi, but I believe its a bit cumbersome trying to install this type of driver with wixtoolsets difx.)

Test wise the driver currently matches against an arbitrary free device node, but I would like to get it to install again as root enumerated device.

Thanks, and cheers,
Hagen.

---
NTDEV is sponsored by OSR

Visit the list online at:

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

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

JiaBang_Lin

this looks suspicious to me. shouldn't the hardware ID be something like
"root\my_test" ?

devcon install my_testl.inf my_test
devcon failed.

weilin_jiang

Hi, What does the "root\" mean? thanks.



[email protected]

From: [email protected]
Date: 2018-02-05 09:56
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] devcon failed.
this looks suspicious to me. shouldn't the hardware ID be something like "root\my_test" ?

devcon install my_testl.inf my_test
devcon failed.

--- NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at

JiaBang_Lin

did you read the f* manual?
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/hardware-ids


2018-02-05 11:25 GMT+08:00 [email protected] :

> Hi, What does the "root\" mean? thanks.
>
> ------------------------------
> [email protected]
>
>
> *From:* [email protected]
> *Date:* 2018-02-05 09:56
> *To:* Windows System Software Devs Interest List
> *Subject:* Re: [ntdev] devcon failed.
> this looks suspicious to me. shouldn't the hardware ID be something like
> "root\my_test" ?
>
> devcon install my_testl.inf my_test
> devcon failed.
>
> --- NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at
>
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
>

Tim_Roberts

On Feb 4, 2018, at 5:56 PM, [email protected] wrote:
>
> this looks suspicious to me. shouldn't the hardware ID be something like "root\my_test" ?
>
> devcon install my_testl.inf my_test
> devcon failed.
>

Not necessarily. A hardware ID can literally be any combination of printable characters.
—
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.

Hagen

Thanks for the suggestions, and yes, of course I tried with root\something as well, as some of the examples used that. However it already was working the last time I tested it (I think with Windows 7....).

And, thanks Doron, I will step into devcon with the debugger on the way to the beach, but currently I am not too keen to put additional work on top to find out why certain tools that used to work all of a sudden do stop. But as I think its a handy technique to match a driver against root for testing I will have a look as soon as the beach is calling...

Thanks,
Hagen.