Posted  by  admin

Microsoft Kernel Debug Network Adapter Driver

  • Install/Update Network Adapter Driver. Open Run command. You can either go to Start Run.
  • When the target adapter is removed from the chassis, the Microsoft Kernel debug adapter is enabled and uses the hardware for the built-in adapter. The Microsoft Network Adapter Multiplexor Protocol service is a kernel mode driver.
  1. Kdnic
  2. Microsoft Kernel Debug Network Adapter Driver
  3. Windows Kernel Debug
  4. Free Network Adapter Driver

Overview

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.

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? Run Intel® Driver & Support Assistant to automatically detect driver or software updates.

Which file should you download?

Kdnic

Note:10 Gb adapters are only supported by 64-bit drivers.

  • PROWin32.exefor 32-bit (x86) editions of Windows*
  • PROWinx64.exefor 64-bit (x64) editions of Windows

How to use this download

Download the self-extracting archive and run it. It will extract the files to a temporary directory, run the installation wizard, and remove the temporary files when the installation is complete. All language files are embedded in this archive. You do not need to download an extra language pack.

See readme.htm if you want to extract the files without installing.

See the release notes in readme.txt for installation instructions, supported hardware, what is new, bug fixes, and known issues.

Supported devices

This software may also apply to Intel® Ethernet Controllers. Support for built-in network connections is provided by the system or board manufacturer.

About Intel® software and drivers

The driver or software for your Intel component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.

See list of computer manufacturer support websites.

-->

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

Adapter

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

Vendor ID 10DF, Emulex Corporation

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

0720E220

Vendor ID 15B3, Mellanox Technology

Microsoft Kernel Debug Network Adapter Driver

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

1000100110021003100410051006100710081009100A100B100C100D100E100F10101013101510171019101B101D101F10211023102510271029102B102F63406341634A634B635463686369637267326733673C673D674667506751675A67646765676E6778

Windows Kernel Debug

Vendor ID 1137, Cisco Systems Inc

For vendor ID 1137, these device IDs are supported:

Free Network Adapter Driver

Windows 10 kernel debug

0043

XML Supported NIC List

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

Related topics