Is there anybody from Microsoft on here who is involved with the partnership program for hardware/driver submissions who can provide assistance with finding out why any particular HLKX package submission goes into any of the following states?
- Pending in “manual review” for multiple days with no explanation as to why.
- Signing failed with an error and the downloadable text file that’s supposed to provide a reason is utterly useless and uninformative when it come to identifying the root-cause of the problem.
Not being able to find out why a submission is failing to be processed at all or in a timely manner is just about as bad as being locked out of the program entirely and not being able to submit a HLKX package.
This is looking more & more like a backend problem on Microsoft’s part. Google searches are turning up multiple identical failures, but only for x64 driver builds; ARM64 builds of drivers built from the exact same source code are getting signed without any issues.
This link is typical of the situation:
When you click on the link to download the full error report for more information about what went wrong and how to fix the issue, the following is what’s actually in the text file it saves locally:
INF validation successful
INF validation successful
Drivers passed Universal check successfully.
INF validation successful
Scanning Notes
{"code":"FileSigningFailed","details":{"error":"FailDoNotRetry returned from Scan service. 4001 [errorInfo, BlockingDetectionFound]"},"innerError":null}
Unless you have some kind of crystal ball, that content fails in every way to identify what went wrong and how to fix the issue.
It makes me shake my head ask just WTF is Microsoft doing to us? If they want to lock out 3rd party driver developers, just end the program entirely. Otherwise, follow through on supporting it properly. Despite the fact that I can use my employer’s account to make the driver package submissions for signing, I have zero access to any method of receiving support when logged on as myself based on every suggested avenue for accessing online support through the developer support site and the partner center site. Even the suggestions to ask Co-Pilot are absolutely useless since Co-Pilot won’t accept an inquiry without going through another authentication gate which cannot be passed.
Yeah, their in-app support system is simply awful. For the Copilot chat sidebar, you have to tell it something first (it doesn't matter what) and then the "Contact support" button takes you to the next step. The problem is, you have to select a workspace first, but for me there is nothing in the list to select. However, from this page I could open a ticket: https://partner.microsoft.com/support