- NETWORK DRIVER WINDOWS 7 DRIVERS
- NETWORK DRIVER WINDOWS 7 FOR WINDOWS 10
- NETWORK DRIVER WINDOWS 7 SOFTWARE
Windows Filtering Platform Callout Drivers Header files that support WSK include the following: Winsock Kernel (WSK) is the kernel mode component of Windows Sockets.įor more info about WSK, see Winsock Kernel. Header files that support the NMR include the following:
The Network Module Registrar (NMR) is an operating system module that facilitates the attachment of network modules to each other.įor more info about the NMR, see Network Module Registrar. Header files that support wireless networking include the following:
NETWORK DRIVER WINDOWS 7 FOR WINDOWS 10
For Windows 10 and later, Wi-Fi drivers use the WLAN Universal Windows driver model, or WDI. Header files that support WiFiCx include the following:įor Windows Vista, Windows 7, Windows 8, and Windows 8.1, Wi-Fi drivers use the Native 802.11 Wireless LAN model. The client driver interacts with WiFiCx for Wi-Fi media-specific functionality in addition to being based on NetAdapterCx and WDF.įor more info about WiFiCx, see Introduction to the Wi-Fi WDF class extension (WiFiCx). Starting in Windows 11, the Windows Driver Kit (WDK) includes a Wi-Fi WDF class extension (WiFiCx) that enables you to write a KMDF-based Wi-Fi client driver for Wi-Fi devices. Header files that support MBBCx include the following: The client driver interacts with MBBCx for mobile broadband media-specific functionality in addition to being based on NetAdapterCx and WDF.įor more info about MBBCx, see Mobile Broadband (MBB) WDF class extension. Starting in Windows 10, version 1809, the Windows Driver Kit (WDK) includes a class extension module (MBBCx) that enables you to write a KMDF-based mobile broadband (MBB) client driver for MBB devices. Windows network drivers support both Wi-Fi and Mobile Broadband. Header files that support virtualized networking include the following: NDIS supports technologies for packet transfer and management within a Hyper-V virtual environment such as Single Root I/O Virtualization (SR-IOV), Virtual Machine Queue (VMQ), and Hyper-V Extensible Switch.įor more info about virtualized networking, see Virtualized Networking.
Header files that support scalable networking include the following: Windows includes technologies for scalable networking such as Header-Data Split, NetDMA, PacketDirect Provider Interface, Network Virtualization using Generic Routing Encapsulation (NVGRE) Task Offload, Receive Segment Coalescing (RSC), Receive Side Scaling (RSS), and TCP/IP offload.įor more info about scalable networking, see Scalable Networking. Header files that support NDIS core functionality include the following: NDIS forms the network driver platform that bridges the gap between the NIC and upper layers in the network stack.įor more info about NDIS Core Functionality, see NDIS Core Functionality. The foundation for all kernel mode Windows network technologies is the Network Driver Interface Specification, or NDIS. Header files that support NetAdapterCx include the following: The client driver interacts with NetAdapterCx, which acts as a bridge to traditional NDIS.įor more info about NetAdapterCx, see Network Adapter WDF Class Extension (Cx). Starting in Windows 10, version 1703, the Windows Driver Kit (WDK) includes a class extension module (NetAdapterCx) that enables you to write a KMDF-based networking (NDIS) client driver for Network Interface Cards (NICs). The following sections contain information for each area of network driver technology: NetAdapterCx This is a complete list of all headers in the WDK for network drivers headers that support particular network technologies are listed in the following sections. The header files that contain the topics defined in this section are included in the Windows Driver Kit (WDK).įor the programming guide, see Network Driver Design Guide. This section lists functions, event callbacks, macros, structures, and enumerations used in Windows network device drivers.
NETWORK DRIVER WINDOWS 7 SOFTWARE
When the software is updated to remove the language, this article will be updated to be in alignment. The word or phrase is used in this article for consistency because it currently appears in the software. This article contains references to terminology that the Microsoft style guide for bias-free communication recognizes as exclusionary. Microsoft supports a diverse and inclusive environment.