Relaxing the enforcement of new InfVerif validation checks

Published Apr 24 2019 04:57 PM 3,365 Views
Microsoft

With the release of Windows 10, version 1903, new validation checks were added to InfVerif tool, which can result in driver submissions for the Windows Hardware Compatibility Program (WHCP) made to the Partner Center to be rejected. To allow for additional time to prepare for these changes, the InfVerif errors detailed below, will be ignored for WHCP driver submissions.

 

Follow up communications will be made once a date has been established to reintroduce these requirements.

 

When established, these checks will be run against all driver submissions and for all OS levels. Driver submissions which exhibit the following errors, will be rejected:

Error 1217:

InfVerif failed for Driver. Partial Log:Error 1217 in xxxxxxxx.inf, line x : Invalid driver version (1.4.1), expecting w.x.y.z, where each segment is between 0-65536.

Error 1330:

InfVerif failed for Driver. Partial Log:Error 1330 in xxxxxxx.inf, line xxxxx: Cannot copy multiple different sources files ('<filename>' and ' <filename> ') to destination file 'C:\Windows\system32\<filename>'.

Error 1331, 1332, and 1333:

These errors are all the same problem but relating to registy values, registry values within services, and services respectively.  Methods to resolve these errors are similar to the methods used to resolve Error 1330.

 

For more information on the errors and what Windows driver developers can do to address them, please review the information at these links:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-driverver-directive

https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/inf-verif-error-1330 

3 Comments
Regular Visitor

@Andrew_Kovar,

Can you confirm this is now releaxed at the Hardware centre?

RS5 HLKX accepted in the past, now rejected.

Occasional Visitor

202106 Has the InfVerif verification check been enforced?

I need to upload an HLKX file to obtain WHQL certification. But Error 1330 is displayed after uploading. Our source files are copied to the destination files based on different hardware IDs. Why is this not allowed? I read your explanation of this error and feel that there is no need to make such a restriction.

 I submitted an hlkx file on May 24, 2021, which showed success, but failed when I submitted it in June 2021. Does the Microsoft Partner Center update the hardware certification?

Occasional Visitor

@tylorsenna I was told that this relaxing was expired since June 1st, 2021. That's why you see this error. I had a similar issue on June 7th, and have to make a change.

%3CLINGO-SUB%20id%3D%22lingo-sub-482364%22%20slang%3D%22en-US%22%3ERelaxing%20the%20enforcement%20of%20new%20InfVerif%20validation%20checks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482364%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20the%20release%20of%20Windows%2010%2C%20version%201903%2C%20new%20validation%20checks%20were%20added%20to%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdevtest%2Finfverif%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EInfVerif%20tool%3C%2FA%3E%2C%20which%20can%20result%20in%20driver%20submissions%20for%20the%20Windows%20Hardware%20Compatibility%20Program%20(WHCP)%20made%20to%20the%20Partner%20Center%20to%20be%20rejected.%20To%20allow%20for%20additional%20time%20to%20prepare%20for%20these%20changes%2C%20the%20InfVerif%20errors%20detailed%20below%2C%20will%20be%20ignored%20for%20WHCP%20driver%20submissions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollow%20up%20communications%20will%20be%20made%20once%20a%20date%20has%20been%20established%20to%20reintroduce%20these%20requirements.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20established%2C%20these%20checks%20will%20be%20run%20against%20all%20driver%20submissions%20and%20for%20all%20OS%20levels.%20Driver%20submissions%20which%20exhibit%20the%20following%20errors%2C%20will%20be%20rejected%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EError%201217%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EInfVerif%20failed%20for%20Driver.%20Partial%20Log%3AError%201217%20in%20xxxxxxxx.inf%2C%20line%20x%20%3A%20Invalid%20driver%20version%20(1.4.1)%2C%20expecting%20w.x.y.z%2C%20where%20each%20segment%20is%20between%200-65536.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EError%201330%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EInfVerif%20failed%20for%20Driver.%20Partial%20Log%3AError%201330%20in%20xxxxxxx.inf%2C%20line%20xxxxx%3A%20Cannot%20copy%20multiple%20different%20sources%20files%20('%3CFILENAME%3E'%20and%20'%20%3CFILENAME%3E%20')%20to%20destination%20file%20'C%3A%5CWindows%5Csystem32%5C%3CFILENAME%3E'.%3C%2FFILENAME%3E%3C%2FFILENAME%3E%3C%2FFILENAME%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EError%201331%2C%201332%2C%20and%201333%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThese%20errors%20are%20all%20the%20same%20problem%20but%20relating%20to%20registy%20values%2C%20registry%20values%20within%20services%2C%20and%20services%20respectively.%26nbsp%3B%20Methods%20to%20resolve%20these%20errors%20are%20similar%20to%20the%20methods%20used%20to%20resolve%20Error%201330.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20more%20information%20on%20the%20errors%20and%20what%20Windows%20driver%20developers%20can%20do%20to%20address%20them%2C%20please%20review%20the%20information%20at%20these%20links%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Finstall%2Finf-driverver-directive%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Finstall%2Finf-driverver-directive%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdevtest%2Finf-verif-error-1330%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdevtest%2Finf-verif-error-1330%26nbsp%3B%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-534174%22%20slang%3D%22en-US%22%3ERe%3A%20Relaxing%20the%20enforcement%20of%20new%20InfVerif%20validation%20checks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-534174%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F303918%22%20target%3D%22_blank%22%3E%40Andrew_Kovar%3C%2FA%3E%2C%3C%2FP%3E%3CP%3ECan%20you%20confirm%20this%20is%20now%20releaxed%20at%20the%20Hardware%20centre%3F%3C%2FP%3E%3CP%3ERS5%20HLKX%20accepted%20in%20the%20past%2C%20now%20rejected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2492515%22%20slang%3D%22en-US%22%3ERe%3A%20Relaxing%20the%20enforcement%20of%20new%20InfVerif%20validation%20checks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2492515%22%20slang%3D%22en-US%22%3E%3CP%3E202106%20Has%20the%20InfVerif%20verification%20check%20been%20enforced%3F%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20need%20to%20upload%20an%20HLKX%20file%20to%20obtain%20WHQL%20certification.%20But%20Error%201330%20is%20displayed%20after%20uploading.%20Our%20source%20files%20are%20copied%20to%20the%20destination%20files%20based%20on%20different%20hardware%20IDs.%20Why%20is%20this%20not%20allowed%3F%20I%20read%20your%20explanation%20of%20this%20error%20and%20feel%20that%20there%20is%20no%20need%20to%20make%20such%20a%20restriction.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3BI%20submitted%20an%20hlkx%20file%20on%20May%2024%2C%202021%2C%20which%20showed%20success%2C%20but%20failed%20when%20I%20submitted%20it%20in%20June%202021.%20Does%20the%20Microsoft%20Partner%20Center%20update%20the%20hardware%20certification%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2540628%22%20slang%3D%22en-US%22%3ERe%3A%20Relaxing%20the%20enforcement%20of%20new%20InfVerif%20validation%20checks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2540628%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1089939%22%20target%3D%22_blank%22%3E%40tylorsenna%3C%2FA%3E%26nbsp%3BI%20was%20told%20that%20this%20relaxing%20was%20expired%20since%20June%201st%2C%202021.%20That's%20why%20you%20see%20this%20error.%20I%20had%20a%20similar%20issue%20on%20June%207th%2C%20and%20have%20to%20make%20a%20change.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎May 01 2019 10:21 AM
Updated by: