Partner Center continues to accept HLKX packages created by older HLK releases, so the passing Windows Server 2025 package from HLK 10.1.26100.8328 can be submitted; Microsoft does not document a cutoff date for that acceptance.^1^
Submit the 10.1.26100.8328 results
Your 8328 run meets the publicly documented baseline conditions:
- HLK 24H2 supports Windows Server 2025.
- Version 10.1.26100.8328 is newer than the security-fixed minimum, 10.1.26100.3916.
- The release notes explicitly state that Partner Center continues accepting HLKX packages from older HLK versions.^1^
- Server certification still requires the corresponding HLK version, matching playlist, and supplemental content.^2^
Proceed as follows:
- In the 8328 controller, install the latest HLK filter CAB.
- Close HLK Studio and run
UpdateFilters.exeon the controller. - Reopen the passing project, select Results → Apply Filters, and verify that the final result contains only the expected filters 320241 and 20801.
- Package and sign the project in that same 8328 environment.
- Upload the
.hlkxthrough Partner Center → Hardware → Submit new hardware.
For existing results, filters must be reapplied manually; newly installed filters are applied automatically only to new results.^3^
Do not reopen and resave the package in an older Studio after processing it with a newer release. The July 2025 refresh introduced a newer HLKX schema: newer Studio versions can read older packages, but older Studio versions cannot read packages saved in the newer format. This affects local package interoperability, not Partner Center’s acceptance of older HLKX packages.^1^
Errata 336996 and the 9818 failures
The 336996 entry being shown as Autotriage is important: autotriage provides diagnostic information but does not convert a failure to pass. Only an applicable errata/filter can override an incorrectly failing test.^3^
There is no publicly documented replacement-binary download for errata 336996. A public report also exists for an Audio Codec Wave failure associated with that filter, but it has no accepted or recommended resolution.^4^
Because 9818 fails at IMMEndpointInternal for every endpoint while 8328 passes all required tests on the same system and driver, the logs are suitable evidence for an HLK test-infrastructure escalation. They do not need to block the already-passing 8328 submission.
Obtaining replacement binaries or a fixed kit
First test with the latest publicly listed Windows Server 2025 HLK rather than attempting to copy binaries between kit builds. Microsoft currently recommends the latest updated kit, and mixing components from different releases is not documented as supported.^2^
If the latest kit still fails, open one support issue per failing test and include:
- Exact test name
- Failing
.hlkx - The corresponding
Te.wtl - Complete test logs and relevant event logs
- HLK versions 9818 and 8328
- Server build numbers
-
E_NOINTERFACE(0x80004002) - The
halfapp.cppassertion - Evidence that all endpoints fail under 9818 and all required tests pass under 8328
Those are the artifacts Microsoft requests for HLK test support.^5^
If Engage Center says there are no support entitlements, use its ? → Engage Center Help → How can we help? option to report the entitlement/onboarding problem. That free channel covers Engage Center access and platform issues, but it is not itself an entitlement for engineering investigation or replacement HLK binaries.^6^
There is no public documentation confirming a free Hardware Dashboard engineering-support route for obtaining errata 336996 replacement binaries. If the Engage entitlement issue cannot be corrected, use your Hardware Developer Program/Partner Center contact or Microsoft Support and reference the existing submission-blocking erratum.
References