InfVerif fail, default install and manufacturers sections

Morning all.

Got a “InfVerif failed for Driver. Partial Log:Error 1212 in AHKDevHacker.inf, line 35 : Cannot have both [Manufacturer] and [DefaultInstall] sections.” from WHQL

The inf has always had a defaultinstal and a manufacturer section, “windows 10 client version 1607” was selected, as before, yet now we have an error.

So either the rules have changed or there is a bug in WHQL.

Can anyone comment/confirm this, and is there documentaiton/a fix coming?

Thanks

The current doc (https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-defaultinstall-section) says :
If you are building a universal or mobile driver package, this section is not valid and should not be used. Instead, use only the INF Manufacturer Section. Using both DefaultInstall and Manufacturer sections in your INF will cause Universal INF validation failures and can lead to inconsistent installation behaviors.

I agree that the page https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/inf-validation-errors-and-warnings should be updated when new rules are added. I had to fix some other unrelated error in an INF (which was all well and good till my previous submission) that has no mention on the above page.

You can ran InfVerif from the latest WDK to verify things are fine or not.

xxxxx@hotmail.com wrote:

Got a “InfVerif failed for Driver. Partial Log:Error 1212 in AHKDevHacker.inf, line 35 : Cannot have both [Manufacturer] and [DefaultInstall] sections.” from WHQL

The inf has always had a defaultinstal and a manufacturer section, “windows 10 client version 1607” was selected, as before, yet now we have an error.

What is the point of such a thing?  If you are a PnP driver, the
[DefaultInstall] can’t do the job.  Are you trying to simulate a
pre-install in some way?


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