are you supposed to have microsoft virtual miniport adapter

It is this last call, #4, which fails with 0xC000000D (STATUS_INVALID_PARAMETER). The MiniportInitializeHandler of the SpartaMini.sys driver calls the NdisMSetMiniportAttributes macro several times as part of miniport initialization: once for: (1) registration attributes, (2) general attributes, (3) task offload and (4) NDK. MiniportInitializeHandler: NdisMSetMiniportAttributes(NDK) - 0xc000000d MiniportTemplateTest Driver for WindowsLonghorn

To reveal itself: MiniportTemplateTest Driver for WindowsLonghorn With an attached kernel debugger, the problem is beginning Running 'devcon install SpartaMini.inf *SpartaMini' manually shows the driver installs fine and again fails to start (10). So this doesn't explain why the driver is failing to start. As you can tell from the output, these interfaces never come up due to the adapter start failure: The test log is full of print statements that dump the list of adapter names, as it waits for the expected MAC addresses to appear. Rather it's statically set by the test for some reason. This is not returned by any OS subsystem or component, but Status 0x26c/620 is ERROR_INVALID_PLUGPLAY_DEVICE_PATH. In my case, the latter happens, and is where my test is failing: HlprAddressSetIPv4() +VAR+FAIL : HlprNetworkInterfacesInstall() If there is no match, it still attempts to assign the address. Then attempts to assign a static IP address to the adapter. If there is a match, the loop breaks and the test Looking at the test source code (WFPLogoSetup.js) and the corresponding log output, the test spins in a loop (120 iterations, with short sleeps) waiting for three Sparta interfaces toĬome online by comparing the MAC address of each interface belonging to a pre-defined sparta adapter to a global array of MAC addresses (specNetworkAdapter.MACAddress = SPARTA_MAC_ADDRESSES). Requirement in any of the Filter driver/WFP HLK tests on MSDN, that I could find at least.Īs to why the test actually fails, for future people googling this.

There is also no mention of this 'clean environment' However, the answer in that thread isn't very helpful, as it does not mention what constitutes a 'dirty environment' or how to fix it other than completely starting over with a clean image. The sparta miniport fails to start with code 10 (ERROR_BAD_ENVIRONMENT). I am also seeing this issue on HLK 1607 targeting OS build 14393.rs1_release.161220-1747 (Windows 10 Pro 圆4).

Are you supposed to have microsoft virtual miniport adapter