Partner Center Hardware: V4 print-driver attestation stuck at "signing" and fails packageInfoValidation with an empty error

Service Microsoft Hardware Dev Center / Partner Center hardware dashboard — attestation signing (no HLK) for a V4 XPS print-driver package (dll + cat + cab).

Scenario I am submitting a V4 print-driver package for attestation signing. All binaries are EV code-signed (Securelink EV certificate) before submission: the driver DLLs for amd64 and i386, the catalog (.cat), and the .cab itself. I need the package MS-signed so it can install on Windows 11.

Result / Problem Two submissions will not complete, and I cannot tell whether they are queued or have genuinely failed, because no actionable error is returned.

Submission A — signing appears stuck (48h+):
  Submission ID: 1152921505701327568
  The workflow stays at "signing / started" for over 48 hours with no error
  report and never advances to finalizeIngestion.

Submission B — packageInfoValidation fails with an empty message:
  Submission ID: 1152921505701342362
  The API reports the workflow failed at packageInfoValidation
  (commitStatus = commitFailed), but the errorReport / messages field is
  EMPTY, so there is nothing to act on. The Partner Center web UI, however,
  still shows this submission as "sign in progress" — which contradicts the
  API status.
```  **Environment**
- Product type: V4 XPSDrv print filter (Class = Printer, DriverPackageType = V4)
- Package: signed .cab containing amd64 + i386 driver DLLs, .cat, INF, GPD,
manifest, pipeline-config
- requestedSignatures: the 13 WINDOWS_v100_X64_*_FULL OS codes
- deviceType: internalExternal
- Submitted via the Hardware Dev Center REST API
(manage.devcenter.microsoft.com/v2.0/my/hardware/products)

  **Troubleshooting already done on my side**
- Verified with signtool that the DLLs, the catalog, and the cab are all
EV-signed and the certificate chain is valid.
- A separate KERNEL driver package submitted from the SAME account completed
attestation signing within about one day — so the account, the EV
certificate, and the general signing queue are known-good. Only these V4
print-driver submissions are affected.
- Reviewed the recent HDC policy on signing unreferenced files; the package
contains only INF-referenced files.

  **Questions**
1. For submission 1152921505701327568, is signing genuinely stuck, and can it
be re-kicked or cancelled?
2. For submission 1152921505701342362, what caused packageInfoValidation to
fail? The empty error message leaves me no way to diagnose it.
3. Why does the web UI show "sign in progress" while the API reports
commitFailed for the same submission? Which status is authoritative?

  Thank you.