Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 3  
14 May 18 04:49
matt sykes
xxxxxx@hotmail.com
Join Date:
Posts To This List: 221
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
  Message 2 of 3  
14 May 18 07:59
Anand A
xxxxxx@gmail.com
Join Date: 05 Aug 2014
Posts To This List: 51
InfVerif fail, default install and manufacturers sections

The current doc (https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-defaultins tall-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.
  Message 3 of 3  
14 May 18 11:34
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11925
InfVerif fail, default install and manufacturers sections

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.
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 15:36.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license