HLK NdisStudio OidRequestTest fails in TestClassSetup — protocolDriver.Create() throws unidentified C++ exception at protocol.cpp:63

All NdisStudio tests under $\Logo Jobs\Device\Network\LAN\Base fail in TAEF TestClassSetup, before the test body runs. The failure is in the NdisStudio framework's own protocol driver creation, and the logged exception carries no error code.

Environment

• HLK controller: Windows Server 2025 / 24H2, kit 10.1.26100.8328
• SUT: Windows 11 25H2, build 26200
• DUT: virtual NetAdapterCx miniport, SIMA_BUS\VIRTUALNETADAPTER\0
• Failing test: [NdisStudio] OidRequestTest - OID_GEN_VENDOR_DRIVER_VERSION Verification

Error (Te.wtl)

Msg    UserText="Root Path: \\?\SWD#NdisStudio#instance_0#{f2ca17e7-61b7-4b8d-98fd-0be8e86cd598}"

Error  File="onecore\net\ndis\studio\testv2\utilities\protocol.cpp"  Line="63"
       ErrCode="0x0"  ErrorText="Error 0x00000000"
       UserText="Caught an unidentified C++ exception during
                 (m_protocolGuid = protocolDriver.Create(m_transaction))"

Error  UserText="Setup fixture 'NdisStudioOidRequestTest::OidRequestTest::TestClassSetup' ... failed."
Result Reason="Setup">Failed

TE.exe exits 1. Time from Root Path: to the exception is ~250 ms in every run.

Already ruled out

• DUT is healthy at failure time — WttEa.log NETWORK_BLOCK shows devicestate 0, mediastate 0, linkspeed 1000000000, IPv4 assigned. NoOfProtocols stays at 2, so the NdisStudio protocol never binds.
• Test body never executes; no OID reaches our miniport.
• Reproduced on two SUTs, both build 26200, identical signature.
• SUT removed and re-registered in HLK Studio (new machine GUID in the log) — unchanged.
• Driver Verifier enabled per the standard HLK task; no violation, no bugcheck.

Questions

1. What causes protocolDriver.Create() to throw at protocol.cpp:63 — SwDevice creation, protocol driver install/start, or something else?
2. With ErrCode=0x0 and no HRESULT reaching the log, how can we surface the underlying error? Is there a WPP/ETW provider for NdisStudio or a TE.exe verbosity switch?
3. Does the NdisStudio protocol driver have a SUT prerequisite that deploying Microsoft-Network-NdisStudio-Runtime.cab does not satisfy?
4. Any known issues running NdisStudio against build 26200 with the 10.1.26100.x kit?

Te.wtl, WttEa.log, WttJobRun.Xml and WTTJQResults.xml from three runs available on request.All NdisStudio tests under $\Logo Jobs\Device\Network\LAN\Base fail in TAEF TestClassSetup, before the test body runs. The failure is in the NdisStudio framework's own protocol driver creation, and the logged exception carries no error code.

Environment

• HLK controller: Windows Server 2025 / 24H2, kit 10.1.26100.8328
• SUT: Windows 11 25H2, build 26200
• DUT: virtual NetAdapterCx miniport, SIMA_BUS\VIRTUALNETADAPTER\0
• Failing test: [NdisStudio] OidRequestTest - OID_GEN_VENDOR_DRIVER_VERSION Verification

Error (Te.wtl)

Msg    UserText="Root Path: \\?\SWD#NdisStudio#instance_0#{f2ca17e7-61b7-4b8d-98fd-0be8e86cd598}"

Error  File="onecore\net\ndis\studio\testv2\utilities\protocol.cpp"  Line="63"
       ErrCode="0x0"  ErrorText="Error 0x00000000"
       UserText="Caught an unidentified C++ exception during
                 (m_protocolGuid = protocolDriver.Create(m_transaction))"

Error  UserText="Setup fixture 'NdisStudioOidRequestTest::OidRequestTest::TestClassSetup' ... failed."
Result Reason="Setup">Failed

TE.exe exits 1. Time from Root Path: to the exception is ~250 ms in every run.

Already ruled out

• DUT is healthy at failure time — WttEa.log NETWORK_BLOCK shows devicestate 0, mediastate 0, linkspeed 1000000000, IPv4 assigned. NoOfProtocols stays at 2, so the NdisStudio protocol never binds.
• Test body never executes; no OID reaches our miniport.
• Reproduced on two SUTs, both build 26200, identical signature.
• SUT removed and re-registered in HLK Studio (new machine GUID in the log) — unchanged.
• Driver Verifier enabled per the standard HLK task; no violation, no bugcheck.

Questions

1. What causes protocolDriver.Create() to throw at protocol.cpp:63 — SwDevice creation, protocol driver install/start, or something else?
2. With ErrCode=0x0 and no HRESULT reaching the log, how can we surface the underlying error? Is there a WPP/ETW provider for NdisStudio or a TE.exe verbosity switch?
3. Does the NdisStudio protocol driver have a SUT prerequisite that deploying Microsoft-Network-NdisStudio-Runtime.cab does not satisfy?
4. Any known issues running NdisStudio against build 26200 with the 10.1.26100.x kit?

Te.wtl, WttEa.log, WttJobRun.Xml and WTTJQResults.xml from three runs available on request.