2 Hardware dashboard API BUGs

Terry Liu 0 Reputation points
2026-03-12T07:30:26.52+00:00
  1. When other partners resell some extension drivers to me, I am able to create a derived package on the web portal. However, when I try to perform the same operation through the API, an error is returned indicating that derive operations are not supported for extension drivers.
  2. In the API, the downloads.items.type.driverMetadata returned by GET https://manage.devcenter.microsoft.com/v2.0/my/hardware/products/{id}/submissions/{id} is calculated differently from the metadata in the AccessUri exported from the web endpoint: https://partner.microsoft.com/en-us/dashboard/hardware/Driver/{id}/submission/{id}/GetDistributionCatalogJson. In some cases, the API method includes extra OS versions, which causes errors when submitting to Windows Update. This has caused a lot of extra work and trouble for my team. Please, Microsoft engineers, pay attention to the development of the API and resolve these issues as soon as possible.
Microsoft Partner Center API
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-03-12T07:30:38.2666667+00:00

    Both issues described are product bugs or design gaps in the Partner Center Hardware API and cannot be fixed from the client side. They require investigation and remediation by the Partner Center engineering team.

    For this type of problem (API behavior inconsistent with the Partner Center web portal, and API responses producing invalid payloads for Windows Update), the supported path is to open a Partner Center / Hardware dashboard support case so the engineering team can:

    1. Reproduce the derive-operation failure for extension drivers via the API.
    2. Compare the downloads.items.type.driverMetadata OS list with the JSON returned by GetDistributionCatalogJson for the same submission.
    3. Correct the API implementation or data mapping so that:
      • Derive operations for extension drivers behave the same in API and portal.
      • The OS list in driverMetadata matches the catalog JSON and does not introduce unsupported OS versions that cause Windows Update submission failures.

    When opening the support ticket, include at minimum:

    • Product ID and submission ID for at least one affected extension driver.
    • The exact API call used for the derive attempt and the full error message returned.
    • A sample of the GET .../products/{id}/submissions/{id} response showing downloads.items.type.driverMetadata.
    • The corresponding JSON from GetDistributionCatalogJson for the same submission, highlighting the OS-version differences.
    • Any Windows Update submission error messages that result from the extra OS versions.

    This information will allow Partner Center support to escalate to the hardware dashboard engineering team with concrete repro data and prioritize a fix.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.