Windows 10: How to enable kernel debug for a new NIC productnot listed in VerifiedNICList.xml

Hi everyone:I am developing a new NIC vendor driver. I want to enable th net kernel debug. Unfortunately the new NIC vendor ID & device ID does not exist in VerifiedNICList.xml.I try the two methodI add my new NIC Vendor ID & device ID into the VerifiedNICList.xml, then I run kdnet hostip port and enable kernel debug mode. when I reboot PC, I only see that my NIC device become a yellow bang deviceCode 35 and can not see kernel debug network device.I change my NIC Vendor ID & device ID ino to Realtek NIC10EC&8168. Then I run the same step, Unfortunately I get the same result

:)

 

Ethernet is showing as Kernel Debug Network Adapater

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you see Kernel Debug Network Adapter in Device Manager. This can happen if debugging is turner on. I would suggest you to turn off debugging by following the steps mentioned below:

1. Type command prompt in the search bar on the
   Taskbar.
   
2. Right click on the command prompt icon and select
   Run as administrator.
   
3. Paste the following commands and hit Enter:
   
   bcdedit /debug off
   

If you still see the Network Adapter, you can disable it from Device Manager without problems. Refer the steps mentioned below:

1. Press Windows Logo key + X, to open
   Device Manager.
   
2. Expand Network adapters.
   
3. Now, right click on the Kernel Debug adapter and select
   Disable device.
   

Let us know how it goes.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Add support for NIC for network kernel debugging

Hello,

We produce NICs and we want them to support network kernel debugging.

What should we do to get this support? Could you please provide what we should start with?

Sincerely,

Egor

 

Add support for NIC for network kernel debugging

Hi Egor,

We see that you would like to know how to add network kernel debugging for the NICs that you produce. However, your question is beyond the scope of what is typically answered in this consumer forum and would be better suited for the developer audience in

MSDN.

Should you have further queries, feel free to post it.