Microsoft Kernel Debug Network Miniport (NDIS 6.20) is a kernel device driver. In Windows 10 it is starting only if the user, an application or another service starts it. If Microsoft Kernel Debug Network Miniport (NDIS 6.20) fails to start, the failure details are being recorded into Event Log. Intel Network Adapter Driver for Windows 10 installs base drivers, Intel PROSet/Wireless Device Manager, advanced networking services for teaming and VLANs (ANS), and SNMP for Intel Network Adapters. This download is valid for the product(s) listed below. In this Video we are going to see how to disable Microsoft Kernel Debug Network Adapter. And to disable adapter. We have to go to 'cmd' and just type 'cmd'. For remote kernel debugging, you need a kernel module to allow it. This is that module. In the Previous editions of Microsoft® Windows Operating Systems Kernel Debugging was performed through Serial Cable, USB and 1394 (Firewire). Installs base drivers, Intel® PROSet/Wireless Software for Windows Device Manager., advanced networking services for teaming and VLANs (ANS), and SNMP for Intel® Network Adapters for Windows 8. Not sure if this is the right driver or software for your component?

1. Network Adapter Driver Windows 7
2. Network Adapter Driver Windows 10
3. Driver De Rede Microsoft Kernel Debug Network Adapter
4. Microsoft Kernel Debug Network Adapter Driver Download

1. Name [00000000] Microsoft Kernel Debug Network Adapter
2. Product Type Microsoft Kernel Debug Network Adapter
3. PNP Device ID ROOTKDNIC0000
4. Index 0
5. IP Address Not Available
6. Default IP Gateway Not Available
7. DHCP Server Not Available
8. DHCP Lease Obtained Not Available
9. Driver c:windowssystem32driverskdnic.sys (6.1.0.0, 22.50 KB (23,040 bytes), 7/10/2015 3:59 AM)
10. Name [00000001] Intel(R) Wireless-N 7260
11. Product Type Intel(R) Wireless-N 7260
12. PNP Device ID PCIVEN_8086&DEV_08B2&SUBSYS_42628086&REV_730C8BFDFFFF4A950C00
13. Index 1
14. IP Address 192.168.1.66, fe80::6c87:82cb:c71c:b660, 2602:306:c537:4260:48d2:7aa1:13c1:764f, 2602:306:c537:4260:6c87:82cb:c71c:b660
15. Default IP Gateway 192.168.1.254, fe80::6eca:8ff:fe41:34a0
16. DHCP Server 192.168.1.254
17. DHCP Lease Obtained 10/17/2015 11:24 AM
18. Memory Address 0xB0400000-0xB0401FFF
19. Driver c:windowssystem32driversnetwbw02.sys (18.11.0.8, 3.60 MB (3,776,792 bytes), 6/21/2015 11:16 PM)
20. Name [00000002] Realtek PCIe FE Family Controller
21. Product Type Realtek PCIe FE Family Controller
22. PNP Device ID PCIVEN_10EC&DEV_8136&SUBSYS_380517AA&REV_0801000000364CE00000
23. Index 2
24. IP Address Not Available
25. Default IP Gateway Not Available
26. DHCP Server Not Available
27. DHCP Lease Obtained Not Available
28. I/O Port 0x00003000-0x00003FFF
29. Memory Address 0xB0500000-0xB05FFFFF
30. Driver c:windowssystem32driversrt630x64.sys (8.15.410.2013, 783.07 KB (801,864 bytes), 8/25/2013 7:34 PM)
31. Name [00000003] Microsoft Wi-Fi Direct Virtual Adapter
32. Product Type Microsoft Wi-Fi Direct Virtual Adapter
33. PNP Device ID {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}VWIFIMP_WFD5&31394B11&1&05
34. Index 3
35. IP Address Not Available
36. Default IP Gateway Not Available
37. DHCP Server Not Available
38. DHCP Lease Obtained Not Available
39. Driver c:windowssystem32driversvwifimp.sys (10.0.10240.16384, 39.00 KB (39,936 bytes), 7/10/2015 3:59 AM)
40. Name [00000004] Microsoft ISATAP Adapter
41. Product Type Microsoft ISATAP Adapter
42. PNP Device ID SWDIP_TUNNEL_VBUSISATAP_1
43. Index 4
44. IP Address Not Available
45. Default IP Gateway Not Available
46. DHCP Server Not Available
47. DHCP Lease Obtained Not Available
48. Driver c:windowssystem32driverstunnel.sys (10.0.10240.16412, 151.50 KB (155,136 bytes), 8/7/2015 12:39 AM)
49. Name [00000005] WAN Miniport (SSTP)
50. Product Type WAN Miniport (SSTP)
51. PNP Device ID Not Available
52. Index 5
53. IP Address Not Available
54. Default IP Gateway Not Available
55. DHCP Server Not Available
56. DHCP Lease Obtained Not Available
57. Adapter Type Not Available
58. Installed Yes
59. Last Reset 10/14/2015 3:46 AM
60. Service Name RasAgileVpn
61. IP Subnet Not Available
62. DHCP Enabled No
63. DHCP Lease Expires Not Available
64. MAC Address Not Available
65. Name [00000007] WAN Miniport (L2TP)
66. Product Type WAN Miniport (L2TP)
67. PNP Device ID Not Available
68. Index 7
69. IP Address Not Available
70. Default IP Gateway Not Available
71. DHCP Server Not Available
72. DHCP Lease Obtained Not Available
73. Adapter Type Not Available
74. Installed Yes
75. Last Reset 10/14/2015 3:46 AM
76. Service Name PptpMiniport
77. IP Subnet Not Available
78. DHCP Enabled No
79. DHCP Lease Expires Not Available
80. MAC Address Not Available
81. Name [00000009] WAN Miniport (PPPOE)
82. Product Type WAN Miniport (PPPOE)
83. PNP Device ID Not Available
84. Index 9
85. IP Address Not Available
86. Default IP Gateway Not Available
87. DHCP Server Not Available
88. DHCP Lease Obtained Not Available
89. Adapter Type Not Available
90. Installed Yes
91. Last Reset 10/14/2015 3:46 AM
92. Service Name NdisWan
93. IP Subnet Not Available
94. DHCP Enabled No
95. DHCP Lease Expires Not Available
96. MAC Address Not Available
97. Name [00000011] WAN Miniport (IPv6)
98. Product Type WAN Miniport (IPv6)
99. PNP Device ID Not Available
100. Index 11
101. IP Address Not Available
102. Default IP Gateway Not Available
103. DHCP Server Not Available
104. DHCP Lease Obtained Not Available
105. Adapter Type Not Available
106. Installed Yes
107. Last Reset 10/14/2015 3:46 AM
108. Service Name NdisWan
109. IP Subnet Not Available
110. DHCP Enabled No
111. DHCP Lease Expires Not Available
112. MAC Address Not Available
113. Name [00000013] Microsoft ISATAP Adapter
114. Product Type Microsoft ISATAP Adapter
115. PNP Device ID Not Available
116. Index 13
117. IP Address Not Available
118. Default IP Gateway Not Available
119. DHCP Server Not Available
120. DHCP Lease Obtained Not Available
121. Name [00000014] Microsoft Teredo Tunneling Adapter
122. Product Type Microsoft Teredo Tunneling Adapter
123. PNP Device ID SWDIP_TUNNEL_VBUSTEREDO_TUNNEL_DEVICE
124. Index 14
125. IP Address Not Available
126. Default IP Gateway Not Available
127. DHCP Server Not Available
128. DHCP Lease Obtained Not Available
129. Driver c:windowssystem32driverstunnel.sys (10.0.10240.16412, 151.50 KB (155,136 bytes), 8/7/2015 12:39 AM)
130. Name [00000015] Bluetooth Device (RFCOMM Protocol TDI)
131. Product Type Bluetooth Device (RFCOMM Protocol TDI)
132. PNP Device ID BTHMS_RFCOMM7&306FD9D&1&0
133. Index 15
134. IP Address Not Available
135. Default IP Gateway Not Available
136. DHCP Server Not Available
137. DHCP Lease Obtained Not Available
138. Driver c:windowssystem32driversrfcomm.sys (10.0.10240.16384, 164.00 KB (167,936 bytes), 7/10/2015 3:59 AM)
139. Name [00000016] Bluetooth Device (Personal Area Network)
140. Product Type Bluetooth Device (Personal Area Network)
141. PNP Device ID BTHMS_BTHPAN7&306FD9D&1&2
142. Index 16
143. IP Address Not Available
144. Default IP Gateway Not Available
145. DHCP Server Not Available
146. DHCP Lease Obtained Not Available
147. Driver c:windowssystem32driversbthpan.sys (10.0.10240.16384, 125.50 KB (128,512 bytes), 7/10/2015 3:59 AM)
148. Name [00000017] Microsoft Wi-Fi Direct Virtual Adapter
149. Product Type Microsoft Wi-Fi Direct Virtual Adapter
150. PNP Device ID Not Available
151. Index 17
152. IP Address Not Available
153. Default IP Gateway Not Available
154. DHCP Server Not Available
155. DHCP Lease Obtained Not Available

To do kernel debugging over an Ethernet network cable, the target computer must have a supported network interface card (NIC).

During kernel debugging, the computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer. For more information, see Setting Up KDNET Network Kernel Debugging Automatically.

To do kernel debugging over a network cable, the target computer must have a supported network adapter. When the target computer is running Windows, the network adapters listed here are supported for kernel debugging.

Version Information

This topic lists the supported adapters for the following versions of Windows

• Windows 10, version 2004 (20H1) Build 19041
• Windows Server 2019

Adapter Support for Previous Releases of Windows 10

See these topics for information on supported versions of NICs in previous versions of Windows 10.

Determining NIC support using VerifiedNicList.xml

To determine which set of NICs is supported for any particular release of Windows, examine the VerifiedNicList.xml file that is in the debuggers directory installed by the WDK that shipped with that particular release of Windows. For 64 bit Windows, by default, it will be installed in this directory:

C:Program Files (x86)Windows Kits10Debuggersx64VerifiedNicList.xml

Checking the VerifiedNicList.xml that ships in the WDK for a particular release, is required because additional hardware support is added to new releases of Windows that is not present in previous releases. So you must check the VerifiedNicLIst.xml file for that particular release.

Finding the vendor ID and device ID

To find the vendor ID and device ID of the network adapter on your target computer.

• On the target computer, open Device Manager (enter devmgmt in a Command Prompt window).
• In Device Manager, locate the network adapter that you want to use for debugging.
• Select and hold (or right-click) the network adapter node, and choose Properties.
• In the Details tab, under Property, select Hardware Ids.

The vendor and device IDs are shown as VEN_VendorID and DEV_DeviceID. For example, if you see PCIVEN_8086&DEV_104B, the vendor ID is 8086, and the device ID is 104B.

Vendor ID 8086, Intel Corporation

For vendor ID 8086, these device IDs are supported:

00010008000C000D0438043A043C0440047010001001100410081009100C100D100E100F1010101110121013101410151016101710181019101A101D101E1026102710281049104A104B104C104D105E105F1060107110751076107710781079107A107B107C107D107E107F108A108B108C109610981099109A10A410A510A710A910B510B910BA10BB10BC10BD10BF10C010C210C310C410C510C610C710C810C910CB10CC10CD10CE10D310D510D610D910DA10DB10DD10DE10DF10E110E510E610E710E810EA10EB10EC10EF10F010F110F410F510F610F710F810F910FB10FC11A91501150215031507150A150B150C150D150E150F151015111514151615171518151C152115221523152415251526152715281529152A1533153415351536153715381539153A153B1546154A154D155715581559155A15601563156F1570157B157C15A015A115A215A315AA15AB15AC15AD15AE15B715B815B915BB15BC15BD15BE15D615D715D815DF15E015E115E215E317D01F401F411F451F631F72211B2159294C8976

Vendor ID 10EC, Realtek Semiconductor Corp.

For vendor ID 10EC, these device IDs are supported:

250226003000812581368137816181668167816881698225

Vendor ID 14E4, Broadcom

For vendor ID 14E4, these device IDs are supported:

1600160116141639163A163B163C163D163E16411642164316441645164616471648164A164C164D164E164F1650165316541655165616571659165A165B165C165D165E165F16621663166516681669166A166B166D166E1672167316741676167716781679167A167B167C167D167F168A168D168E1680168116821683168416861687168816901691169216931694169616981699169A169B169D16A016A116A216A416A516A616A716A816AA16AC16AE16B016B116B216B316B416B516B616B716C616C716C916CA16CE16CF16D016D116D216D516D616D716D816D916DD16DF16E016E216E316E416E916F016F116F716FD16FE16FF170D170E170FD802

Vendor ID 1969, Atheros Communications

For vendor ID 1969, these device IDs are supported:

10621063107310831090109110A010A110B010B110C010C110D010D110E010E110F010F120602062E091E0A1E0B1E0C1E0D1E0E1E0F1

Vendor ID 19A2, ServerEngines (Emulex)

For vendor ID 19A2, these device IDs are supported:

02110215022107000710

Network Adapter Driver Windows 7

Vendor ID 10DF, Emulex Corporation

For vendor ID 10DF, these device IDs are supported:

0720E220

Vendor ID 15B3, Mellanox Technology

For vendor ID 15B3, these device IDs are supported:

1000100110021003100410051006100710081009100A100B100C100D100E100F10101013101510171019101B101D101F10211023102510271029102B102F63406341634A634B635463686369637267326733673C673D674667506751675A67646765676E6778

Vendor ID 1137, Cisco Systems Inc

For vendor ID 1137, these device IDs are supported:

0043

Network Adapter Driver Windows 10

XML Supported NIC List

Driver De Rede Microsoft Kernel Debug Network Adapter

This is the same information shown above in the XML format.

Microsoft Kernel Debug Network Adapter Driver Download

Related topics