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.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 9 April 2018

Writing WDF Drivers I: Core Concepts, Manchester, NH, 7 May 2018

Kernel Debugging & Crash Analysis for Windows, Manchester, NH, 21 May 2018


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 8  
12 Feb 18 17:59
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

Alert me | Edit | Delete | Change type Question You cannot vote on your own post 0 When I attempt to submit my HLKX via https://developer.microsoft.com/en-us/dashboard/hardware/driver/New I see ---- The file you selected is not a valid format for submission. Verify your selection and, if needed, recreate your submission package and try again. ---- With no additional information. I installed HLK 10.1.16.299.15 on a controller, added a client (after installing my cross signed WFP driver upon it) and ran the HyperVisor Code Integrity Readiness Test. I added the driver folder and the symbols folder (which both were the same as they were sitting in the same folder). I check the box by my driver and set the locales to US. Upon "Create Package", I attempted to sign the HLKX package but the tool didn't accept my cert when provided or when sought in the store. I do not know why the Microsoft site fails on the format of the HLKX and see no useful information. Please let me know if you have any clues. Eva
  Message 2 of 8  
12 Feb 18 18:43
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11891
WHQL New Driver Submission results in "file you selected is not a valid format for su

xxxxx@gmail.com wrote: > ---- > The file you selected is not a valid format for submission. Verify your selection and, if needed, recreate your submission package and try again. > ---- > > With no additional information. > > I installed HLK 10.1.16.299.15 on a controller, added a client (after installing my cross signed WFP driver upon it) and ran the HyperVisor Code Integrity Readiness Test. I added the driver folder and the symbols folder (which both were the same as they were sitting in the same folder). Shouldn't be.  The "driver" folder means the one with your CAT, your INF, and your SYS -- essentially, your driver package.  This is what they will sign. > I check the box by my driver and set the locales to US. Upon "Create Package", I attempted to sign the HLKX package but the tool didn't accept my cert when provided or when sought in the store. You have to sign the HLKX with one of the certificates registered with your dashboard account.  That's required.  What did the signing process tell you? -- Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc.
  Message 3 of 8  
12 Feb 18 21:06
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

Thanks. So, we sign the driver as a part of our jenkins job with a cert from dig cert prior to running the HLK. I tried moving the hlkx file to that system and running a sign but sign tool didn't recognize it as a signable file. It sounds like I need to register that cert with our account. Perhaps that is the step I missed. I'll split the signed files up and generate a new pacakage then verify our cert is associated with the account before moving forward. I thought we had done that part already when we signed the singable file and added it back to the account. Our other problem is that while we have a sha2 cert we sign with a sha1 has due to a problem with signtool interaction with the CSP/KSP/CNG to our HSM. I hope that's not a problem as well because after three weeks work with the vendor we are still stuck with KSP/CNG access for the sha2 process.
  Message 4 of 8  
12 Feb 18 21:17
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

Hi Tim, I verified that the sginature on the cat/syc signed files matches that of the one registered without account. I repackaged to ensure the driver folder contained just inf/cat/sys and symbols folder just the pdb. I gather I need to select cert when creating the package even though the files are already signed. So, now I need to determine why the cert file which would with signtool isn't viable for HLK Any ideas what might be getting in the way there?
  Message 5 of 8  
13 Feb 18 09:36
Gabe Jones
xxxxxx@ni.com
Join Date: 19 Mar 2012
Posts To This List: 45
WHQL New Driver Submission results in "file you selected is not a valid format for su

> I tried moving the hlkx file to that system and running a sign but sign tool didn't recognize > it as a signable file. This is normal. You need to use HLK Studio to sign the HLKX package, so you'll have to figure out why HLK Studio is balking at your cert. What did it tell you when signing failed? Once you get it working, if you ultimately want a more scriptable experience you'll need to investigate the HLK APIs. (e.g., https://docs.microsoft.com/en-us/windows-hardware/test/hlk/api/packagemanagersign -method)
  Message 6 of 8  
13 Feb 18 09:49
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

Hi Tim, Do you know how to specify CSP for the studio sign of a package? Ah, I had a crt not a cer. I converted via https://www.sonicwall.com/en-us/support/knowledge-base/170504597576961 and now studio cannot use my cert"No certificate available meets the application criteria". I suspect that this is caused by the need to integrate with my HSM. For sign tool, I can provide the appropriate CSP provider and container name, but I see no option for this in the studio application.
  Message 7 of 8  
13 Feb 18 16:06
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

ok, I got it. My signatures are no good because I can only use /fd sha1 due to the HSM issues. So, I'm blocked until I dance with the HSM vendor and solve that problem. https://blogs.msdn.microsoft.com/windows_hardware_certification/2017/11/13/starti ng-in-february-2018-packages-signed-using-a-sha-1-digest-algorithm-and-certificat e-chain-will-no-longer-be-accepted/ It could have been great if MS provided a more detailed error as it is possible that the blog artifact above isn't the real problem, just a problem.
  Message 8 of 8  
16 Feb 18 12:02
Eva Brigid
xxxxxx@gmail.com
Join Date: 12 Feb 2018
Posts To This List: 12
WHQL New Driver Submission results in "file you selected is not a valid format for su

Gabe, Thanks for the link. So after "Unable to use the selected certificate to sign the package" I see Could not create submission package - Cannot locate the selected digital certificate. I suspect it is not using the HSM which means using the UI for proof of concept may not be a viable approach and I'll need to use the link you said to use the API. My other problem is that the HSM is only in a secured VPC so I'd prefer to transfer the unsigned HLKX package to a system there and then sign it. Is that scenario supported or must the signing of HLKX package be done upon the Controller? Eva
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 16:53.


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