An Ethernet driver lets Windows operate a wired network interface controller. Depending on the controller and package, it may expose link negotiation, offload, buffer, flow-control, jumbo-frame, and power-management settings. The same controller family can appear in different PC, motherboard, card, and dock designs, so a chip name alone is not enough to select a package. Start with the exact system or board support page, identify its hardware revision and controller hardware ID, and check the package's supported Windows release. For a separate adapter, use that adapter maker's documentation.
A support-page listing is not proof of universal firmware pairing, certification, or a guaranteed improvement. Link speed and throughput also depend on the cable, switch, connection path, and the other endpoint. Keep a local copy of an applicable driver before changing the connection you depend on. We do not host installers or regard third-party updater recommendations as compatibility evidence. Follow exact-product guidance for any advanced setting or firmware change rather than assuming a generic fix applies.
An Ethernet driver is the software that lets Windows operate the network interface controller on your board or card. Its most visible job is bringing up the link and negotiating a speed with the switch at the other end, but it does considerably more underneath. It offloads checksum and segmentation work to the controller to spare the processor, moderates interrupts so a busy link does not flood the CPU, and manages energy-efficient Ethernet, which lowers power on an idle line.
The driver also exposes the adjustable behavior of the adapter through its Advanced properties: speed and duplex, jumbo frames for large transfers, flow control, and receive and transmit buffer sizes. These settings are where fine-tuning and, occasionally, trouble live, because an aggressive power-saving or duplex option can turn a healthy link intermittent. Most users generally do not touch them, and the correct driver ships sensible defaults.
Finally, the driver is the bridge between the physical port and the rest of the Windows networking stack. Everything above it, from IP addressing to the applications using the connection, depends on it presenting a stable, correctly negotiated link. That is why a mismatched Ethernet driver shows up not as a dramatic failure but as dropped connections, wrong link speeds, or throughput that does not reach the port's rating.
Expanded guide insight
The practical ethernet & lan context
Wired networking is mature and dependable. A bad cable, router port, link speed, or address configuration is commonly the real cause—not a missing Ethernet driver.
Test a known-good cable before reinstalling an adapter.
A 100 Mbps link often points to a cable pair problem.
Ethernet working while Wi-Fi fails is a useful isolation clue.
Take care: Skip network optimizer software; it can add a new layer of failure to a working Windows network stack.
Fast checks for common ethernet & lan problems
What you see
Likely area to check
Safe first move
Windows reports an unidentified network
Addressing or network configuration failed
Run the built-in Network troubleshooter
Gigabit connection negotiates at 100 Mbps
Cable or router-port path is limited
Try a known-good Cat 5e/6 cable and another port
Connection drops when idle
Adapter power saving is too aggressive
Review the adapter Power Management setting
Start with the lowest-risk check that matches what you see, then return to the detailed sections below if it does not resolve the issue.
Identify your exact device first
Open Device Manager, expand Network adapters, and read the exact controller name, such as a Realtek PCIe GbE Family Controller or an Intel Ethernet Connection.
Open the adapter's Details tab and view the hardware ID if you need to pin down the precise controller model.
Check the adapter's Advanced tab to see whether it exposes multi-gig speeds like 2.5 Gbps, which distinguishes newer controllers from plain gigabit parts.
Note whether the port is integrated on the motherboard, on an add-in card, or on a USB or dock adapter, since each points to a different driver source.
For a branded laptop or prebuilt, record the model, service tag, or serial number and compare its listed controller with Device Manager.
Look at the link light and negotiated speed in the adapter's status to confirm whether it is reaching gigabit or multi-gig or falling back.
Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Located by Acer model or serial number
Scan the list first, then open the family that matches your hardware for the full reference.
Reference coverage summarizes the Windows releases discussed in this catalog; it is not certified compatibility. Confirm the exact device or PC model, hardware revision, current Windows release, and current package requirements on the publisher source before making a change.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
This is the single most common wired-LAN controller in consumer computing, integrated on a huge range of desktop boards and laptops as the standard gigabit port. It handles link negotiation up to 1 Gbps along with the usual offload and power-saving features. Because the same chip sits behind so many brand names, read the exact controller string in Device Manager, then on a branded machine fetch the version your PC maker validated rather than a bare Realtek build.
How you recognize it
Reads as Realtek PCIe GbE Family Controller in Device Manager
Single gigabit RJ-45 port integrated on the board
Advanced tab tops out at 1.0 Gbps full duplex
Common integrated gigabit LAN on many desktops and laptops.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
This is the multi-gig sibling of Realtek's gigabit part, found on newer motherboards that offer a 2.5 Gbps wired port. It falls back cleanly to 1 Gbps on older switches, so reaching its full rate requires 2.5 Gbps-capable networking gear and adequate cabling end to end. If the port negotiates at gigabit when you expect more, check the switch and cable before the driver, since the controller itself will step down automatically.
How you recognize it
Reads as Realtek PCIe 2.5GbE Family Controller
Advanced tab lists a 2.5 Gbps speed option
Falls back to 1 Gbps on older switches
2.5 Gigabit controller found on newer motherboards.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
This controller powers a large share of USB dongles and dock-based Ethernet ports rather than a soldered motherboard NIC. Because it rides on a USB or Thunderbolt link, its dependability depends partly on the host port and, on a dock, the dock's own firmware and USB stack. When such an adapter drops out, update the dock firmware and USB controller driver first, then this adapter driver, and try a port directly on the PC to rule the dock out.
How you recognize it
Reads as Realtek USB GbE Family Controller
Backs a USB dongle or dock Ethernet port
Appears and disappears with the USB or dock connection
Used by many USB and dock-based Ethernet adapters.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
The I219 is Intel's integrated gigabit LAN found on a great many business desktops and laptops, valued for stable links and a mature driver. It commonly appears in fleet machines where consistent behavior matters more than raw speed. On such systems the OEM ships a validated build tied to the platform firmware, so prefer that over the generic Intel package to keep the link steady across power states.
How you recognize it
Reads as Intel Ethernet Connection I219 in Device Manager
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Intel identifies I225-V as a single-port controller in the I225 series, and the I225/I226 product brief describes operation through 2.5 Gbps. Host boards and controller revisions can have different driver or NVM guidance. Check the cable, switch, settings, driver, and exact host advisories rather than prescribing a generic firmware alignment or Energy Efficient Ethernet change.
How you recognize it
Reads as Intel Ethernet Controller I225-V
Supports rates through 2.5 Gbps with a compatible link partner
Exact host board and controller revision control advisories
2.5GbE controller; follow only host- and revision-specific driver or NVM guidance.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Intel identifies the I226-V as a single-port client Ethernet controller in the I226 series, and Intel's I225/I226 product brief describes 10M/100M/1G/2.5G operation. Reaching 2.5 Gbps still requires compatible cabling and network equipment. Intel's product page does not substantiate a blanket claim that I226-V fixes I225-V stability issues or that every board requires a user-serviceable firmware pairing, so follow the exact board maker's package and advisories.
How you recognize it
Reads as Intel Ethernet Controller I226-V
Member of Intel's I226 controller series
Supports up to 2.5 Gbps with a compatible link partner
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
The I210 is a discrete Intel gigabit controller aimed at workstation and small-server boards, chosen for its dependable driver and features suited to typically-on use. It often appears as a second, dedicated NIC alongside a consumer port. Because it is a server-class part, match its driver to the board or system it ships in and keep it aligned with any firmware updates to preserve the dependability it is bought for.
How you recognize it
Reads as Intel Ethernet Server Adapter I210
Discrete gigabit controller on workstation and server boards
Frequently a second, dedicated NIC in the system
Discrete gigabit controller used on workstation boards.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Dell lists network packages by system model and configuration because its desktops and laptops use different LAN controllers. Look up the Service Tag on Dell's support site and confirm that the listed package names the installed controller and Windows version. A model-matched package may include Dell-specific power-management settings, but it does not by itself guarantee link stability.
How you recognize it
Delivered as a Dell package matched to a Service Tag
Listed for a specific Dell model and Windows version
Underlying controller varies by configuration
Look up your Service Tag for the validated network driver.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
HP lists integrated-LAN packages by product or serial number on its support site. Device Manager may identify the underlying Realtek or Intel controller; compare that identity with the package details and Windows version. The HP listing is a sensible first reference for model-specific power or firmware dependencies, while actual negotiation and sleep behavior also depend on the controller, settings, cable, and network equipment.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Lenovo lists wired-network packages by machine type and model, while similar systems can contain different controller options. Identify the machine type on Lenovo's support site, then compare the package details with Device Manager and your Windows version. The model listing can account for system-specific dependencies, but power-state link stability still needs to be verified on the actual configuration.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
ASUS motherboard LAN controllers and packages vary by exact board and revision. Use the board support page, identify whether its controller is Realtek, Intel, or another vendor, and verify Windows applicability. The listing does not by itself establish a driver/firmware pair or guarantee that a package prevents intermittent drops.
How you recognize it
Downloaded from a specific ASUS motherboard support page
Controller must match the exact board revision
Rated speed depends on the fitted controller
Download from your specific motherboard support page.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
MSI LAN packages are selected by exact motherboard and controller. Verify the board revision, controller identity, package notes, and Windows release. A board download listing does not by itself substantiate firmware alignment or improved link stability.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Gigabyte and Aorus boards use different LAN controllers across models and revisions. Choose the exact board, then verify controller identity, package notes, and Windows applicability. A per-board listing does not itself establish a driver/firmware pair or superior stability.
How you recognize it
Chosen by exact Gigabyte or Aorus board model and revision
Controller identity must match the package
Rated speed depends on the fitted controller
Choose your motherboard model on Gigabyte support.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
For an ASRock-based build, this is the LAN driver ASRock provides for the network controller on that particular board, matched to its firmware. ASRock boards carry a mix of gigabit and multi-gig Realtek and Intel controllers, so finding your board's support page helps ensure the correct pairing. Using the board-specific package rather than a generic controller driver is what keeps the wired link stable on ASRock hardware.
How you recognize it
Found on the specific ASRock board's support page
Matched to that board's firmware
Covers the gigabit or multi-gig NIC on the board
Find your board's support page for the matching driver.
Reference coverage: Varies by exact controller, hardware revision, system or board package, and release; verify the official support page
Acer lists wired-network packages for desktops and laptops by model or serial number. Because configurations can use different Realtek or Intel controllers, compare the support-page package with Device Manager and the installed Windows version. Use the model-specific listing as the first reference for any Acer dependencies, then verify link and sleep behavior after a change.
How you recognize it
Located by Acer model or serial number
Listed for a specific Acer system
Underlying controller may be Realtek or Intel
Use Acer support with your model or serial number.
Device Driver Guide does not host, mirror, or alter driver files. The official-source citations below are maintained separately from this reference material and never point to third-party mirrors.
Where the correct package usually comes from
For a branded laptop or prebuilt desktop, start with the PC maker's exact-model page and verify the controller and Windows applicability. Its listed package may include system-specific components, but a general support page does not prove testing, firmware tuning, or a guaranteed stability result for an unnamed system.
For a PC you built yourself, start with the motherboard support page for the exact board and revision, then compare the listed controller and Windows release. A silicon-vendor package can also be appropriate when it explicitly lists that controller. A support-page listing does not by itself prove a LAN driver is paired with board firmware.
A USB or dock Ethernet path can involve the adapter, USB or Thunderbolt controller, cable, and dock. Isolate the adapter by testing a direct port when possible, then apply only driver or dock-firmware updates whose notes name the exact product and symptom. Do not assume every dock Ethernet controller is Realtek or that firmware must be updated first.
Official sources and citations
These links serve two different purposes. A manufacturer support selector helps you find an exact model, but does not prove that a package or feature exists for every product in a family. Claim-specific documents explain the cited technology, requirement, lifecycle, or bounded package example. In either case, check the publisher domain, exact model and hardware revision, operating-system release, supported-products list, and package notes before making a change.
Microsoft Lifecycle: Lifecycle documentation for Windows 10 Home and Pro; separately governed editions and servicing channels can have different dates.
Realtek: Use this publisher-maintained page to match the exact Realtek model and operating-system release before selecting a package.
Device Driver Guide is an independent reference, not a repair or technical-support service. It does not host or mirror installers and receives no payment for these links. A named-model package example applies only to the systems and operating systems on that publisher page; it is not a recommendation to install the package across a family. Report a moved or incorrect link through the correction form.
Ethernet & LAN reference tables
Where to get the wired-network driver
Machine type
Primary source
Fallback
Branded laptop or prebuilt
PC maker by model or Service Tag
Silicon vendor only if no OEM build
Self-built desktop
Motherboard vendor for the exact board
Realtek or Intel download center
USB or dock adapter
Exact adapter and dock documentation
Test a direct PC port before choosing an update
Fresh Windows install
Keep the exact model's applicable package locally
Windows Update only if it offers a compatible driver
Any machine
Not a third-party updater tool
Not a mirror or driver-pack site
The right source depends on how the machine was built, not just on the chip name.
Wired-network symptoms and first checks
Symptom
Possible causes
First safe step
Link at 100 Mbps not gigabit
Cable or forced Speed and Duplex
Try Cat 5e or better, set Auto Negotiation
Drops when the PC idles or sleeps
Link partner, cable, settings, driver, or system issue
Read exact-product guidance before changing EEE or power settings
Yellow mark after an update
Bad driver install
Roll Back Driver, or uninstall and reinstall
No adapter appears at all
Missing hardware, disabled port, connection, or driver issue
Confirm installed hardware and the exact model's enablement instructions
Multi-gig port drops intermittently
Cable, switch, settings, driver, or revision-specific issue
Check the physical path and exact product advisories
USB adapter unrecognized on a dock
Adapter, cable, dock, port, or software issue
Test a direct PC port; follow only the exact product's update sequence
A symptom can have several causes; identify the connection path before changing drivers or settings.
What actually caps your link speed
Link target
Also required
If missing
1 Gbps
Cat 5e cable and a gigabit switch port
Falls back to 100 Mbps
2.5 Gbps
Multi-gig switch and Cat 5e or better
Falls back to 1 Gbps
Stable multi-gig
Compatible controller, cable, switch, and documented settings
Link rate or stability can be limited
Steady link across sleep
Supported hardware, driver, and documented power behavior
Investigate the exact system rather than assuming one power setting
Transfer throughput
Sufficient capacity across endpoints, storage, and network path
Application throughput can remain below nominal link speed
A driver alone cannot deliver multi-gig if the rest of the path does not support it.
When updating helps, and when it does not
Use the exact-product release notes to weigh security fixes, Windows support changes, features, and known issues. A larger version number alone is not a reason to update, but a working connection does not make a security advisory irrelevant.
Consider a driver update when its release notes address the exact controller, Windows release, and symptom. Some host products publish separate NVM or firmware advisories, but their applicability is revision-specific; do not infer a mismatch or update firmware from an intermittent link alone.
Because you are updating the very connection you rely on, download the installer locally before you begin so a dropped link mid-install cannot leave you stranded. Then update deliberately, test, and stop rather than chasing every release.
Before you install anything
Read and record the exact controller name and, if needed, the hardware ID from Device Manager before downloading anything.
Save the installer to local storage first, since updating the network driver can temporarily drop your connection.
For a branded machine, match the model, controller, hardware revision, and Windows release to the package's supported-system list.
Note your current Advanced settings, especially Speed and Duplex, so you can restore them if a new driver resets them.
For a USB or dock adapter, follow only the update sequence documented for that exact product; there is no universal dock-firmware-first order.
Keep the previous working installer on hand so a rollback is one step away if the new release misbehaves.
How to update ethernet & lan drivers
1
Identify the controller in Device Manager
Press Win + X, open Device Manager, and expand Network adapters. Note the exact controller name (for example, Realtek PCIe GbE or Intel Ethernet Connection I219) and, if needed, its hardware ID from the Details tab.
2
Match the driver to your machine, not just the chip
If you have a branded laptop or prebuilt desktop, get the network driver from that maker's support site using your model, Service Tag, or serial number. For self-built PCs, use the motherboard vendor or the silicon vendor's download center.
3
Download the Whql-signed package
Choose the driver that lists your Windows version and, where offered, the signed Whql release. Avoid third-party updaters and mirror sites; download only from your PC maker, motherboard vendor, or the silicon vendor's own support site.
4
Install over a stable connection or offline
Because you are updating the network driver, save the installer locally first. If the link drops during installation, you can still complete the process without needing the internet.
5
Reboot and verify link settings
Restart the PC, then reopen Device Manager and confirm the adapter is active. Check the Advanced tab for Speed and Duplex, and leave it on Auto Negotiation unless your switch requires a fixed value.
Confirm the install actually worked
Reboot, then confirm in Device Manager that the adapter is active with no warning icon.
Check negotiated link speed against the capabilities of both endpoints and the cable path, not just the adapter's maximum rating.
Leave Speed and Duplex on Auto Negotiation unless your switch specifically requires a fixed value, and verify the link holds.
Let the PC idle or sleep and wake it to confirm the connection does not drop, especially on a multi-gig controller.
Test a transfer to a known local endpoint and watch for interruptions. Protocol overhead, storage, and the other endpoint can keep throughput below the nominal link rate.
For a USB or dock adapter, verify it survives unplugging and reconnecting the dock.
Undoing a bad ethernet & lan install
The fastest recovery from a bad Ethernet driver is Device Manager's Roll Back Driver on the adapter, which returns Windows to the previous version in a single step and may restore the link immediately. Because the network may be down while you do this, having kept the previous installer locally means you are not dependent on an internet connection to fix the connection.
If Roll Back is unavailable, uninstall the adapter in Device Manager, reboot, and reinstall the OEM package for a branded machine or the board or silicon vendor's package for a self-built PC. Install from the local copy you saved so a dropped link during the process cannot interrupt it. After reinstalling, confirm the speed negotiates correctly and the link survives an idle period.
For a controller with separately published NVM or firmware, driver rollback does not reverse that firmware. Do not attempt a firmware downgrade unless the board, system, or adapter maker explicitly documents it for the exact hardware revision; otherwise use its recovery guidance or support channel.
A package that lists the controller but not the exact system may omit system-specific requirements. Check the maker's instructions before substituting it.
Changing Energy Efficient Ethernet or power-management settings without exact-product guidance can alter power use or behavior without fixing the actual problem.
Forcing a fixed Speed and Duplex value that the switch does not expect leads to a mismatch and an unstable or slow link.
Cable quality, length, termination, and the supported rates at both endpoints can limit negotiation; a cable label or driver update alone does not prove the achievable rate.
Some I225-V systems received board- or system-specific NVM, firmware, or driver guidance; apply only instructions that name the exact controller revision and host product.
USB and dock Ethernet adapters can fail because of the dock's firmware or USB stack rather than the adapter driver, misdirecting troubleshooting.
Mistakes to avoid with ethernet & lan
Substituting a silicon-vendor package without checking the host system's model-specific requirements.
Disabling Energy Efficient Ethernet or power management as a default fix without exact-product guidance.
Forcing a fixed Speed and Duplex the switch does not expect, producing a slow or unstable link.
Using a cable below the needed category, which silently caps a multi-gig port at a slower speed.
Applying NVM or firmware guidance for a different controller revision or host product.
Blaming the adapter driver for a USB or dock failure that is really the dock's firmware or USB stack.
Updating the network driver online without a local copy, so a dropped link mid-install leaves you stranded.
Trusting a third-party driver updater, which installs mismatched versions or bundles unwanted software.
Situations readers arrive with
My gigabit port only ever connects at 100 Mbps no matter what I do.
This is usually the cable or a forced Speed and Duplex setting, not the driver. Confirm the cable is at least Cat 5e and undamaged, and try a different switch port. In the adapter's Advanced properties, set Speed and Duplex back to Auto Negotiation and let the link renegotiate.
My wired connection drops every time the PC sits idle or wakes from sleep.
Check the cable, switch port, driver version, and system event details. Change EEE or power settings only when exact-product guidance recommends that step, and record the original values. These controls may not exist on every adapter, and the symptom alone does not identify them as the cause.
After updating the network driver, the adapter shows a yellow exclamation mark.
Open Device Manager, right-click the adapter, and choose Roll Back Driver to return to the previous version in one step. If that is unavailable, uninstall the device, reboot, and reinstall the OEM or board package from a copy you saved locally, so a dropped link during the process cannot strand you.
My new 2.5 Gbps port keeps losing the link during light use.
Check the cable, switch port, negotiated rate, and adapter power settings first. Then read the exact board or system advisories for its controller revision. Apply a driver, NVM, or firmware change only when that document lists the product and procedure; do not assume Energy Efficient Ethernet or a firmware mismatch is the cause.
My USB Ethernet adapter on a dock is not recognized at all.
Test the adapter on a direct PC port if its design permits and check the dock's power and cable connections. Identify the exact adapter and dock before selecting software. Apply firmware only when that product's documentation identifies an applicable update and sequence; do not assume the dock must be updated first.
Symptom-by-symptom troubleshooting
Adapter shows a yellow exclamation mark after an update
Open Device Manager, right-click the adapter, and choose Roll Back Driver. If that is unavailable, uninstall the device, reboot, and reinstall the OEM or silicon-vendor package for your exact model.
Link negotiates at 100 Mbps instead of 1 Gbps or 2.5 Gbps
Check the supported rates at both endpoints and the cable specifications, length, and condition. Try a known-good cable and port. Compare negotiation settings with the exact adapter and switch documentation before changing them.
Connection drops when the PC sleeps or idles
Check the connection path and exact system or adapter advisories. Change EEE or power settings only when exact-product guidance recommends that step; record the original values and test whether the documented change addresses the symptom.
No Ethernet adapter appears at all
Confirm installed hardware, physical connections, and the exact model's enablement instructions. A missing entry does not prove a Bios setting or driver is at fault. Keep an applicable package locally if installation is recommended.
Slow or erratic throughput on large transfers
Test with known-good cabling and a known local endpoint, accounting for storage and connection-path limits. Do not change interrupt moderation or buffers without exact-product guidance and a way to compare and restore the original settings.
Intel I225-V or I226-V loses link intermittently
Confirm the exact controller and board revision, test the cable and switch port, and review that host product's advisories. Apply only the driver, NVM, firmware, or setting change that explicitly covers the hardware and symptom.
USB Ethernet adapter is not recognized on a dock
Try the adapter directly on the PC to isolate the dock, identify the actual USB Ethernet controller, and check both product support pages. Update dock firmware, USB/Thunderbolt software, or the adapter driver only when the exact listing is applicable.
Frequently asked questions
How do I know which Ethernet driver I need?
Open Device Manager and read the controller name under Network adapters. Most systems use a Realtek or Intel controller. Download the matching package from your PC or motherboard maker, or from the silicon vendor's download center.
Should I use the driver from Windows Update or the vendor?
Compare the package offered by Windows Update with the exact system maker's applicable release notes. Neither source alone guarantees stability, extra features, or coverage of every controller revision. Match the hardware, system, and Windows release.
My laptop is HP, but Device Manager says Realtek. Whose driver do I install?
Start with HP's exact-model page and compare its listed controller and Windows release with your system. Check HP's guidance before substituting a Realtek package; a generic controller listing does not establish model-specific applicability.
Do I need a driver for a basic gigabit connection to work?
Windows includes in-box drivers for many Ethernet controllers and may provide basic connectivity during setup. A model-appropriate vendor or OEM package can add controller-specific settings or address documented issues, but it does not guarantee better stability or speed. Gigabit negotiation also requires compatible cabling and network equipment.
What is the difference between 1GbE, 2.5GbE, and multi-gig?
Those numbers describe maximum negotiated link speed. Reaching them requires a compatible controller, cabling, and switch. A 2.5GbE controller like the Intel I225-V or I226-V will fall back to 1 Gbps on older equipment.
Why does my new 2.5GbE port keep dropping the link?
Possible causes include the cable, switch, negotiation, power settings, driver, or a revision-specific issue. Identify the exact controller and host product, then follow only advisories that explicitly list them; do not apply a generic firmware downgrade or assume Energy Efficient Ethernet is the cause.
Are third-party driver updater tools safe for network adapters?
We do not recommend them. They often install mismatched versions or bundle unwanted software. Download only from your PC maker, motherboard vendor, or the silicon vendor's own support site.
Terms used on this page
NIC
Network interface controller, the chip or card that provides the wired Ethernet port and needs a driver to operate.
Auto negotiation
The process by which the adapter and switch agree on the highest link speed and duplex they both support.
Duplex
Whether the link sends and receives at the same time (full duplex) or one direction at a time (half duplex).
Jumbo frames
Larger-than-standard Ethernet packets that can improve efficiency on big transfers when the whole path supports them.
Energy Efficient Ethernet
A link power-saving feature. Availability and troubleshooting guidance depend on the controller, driver, and link partner.
Whql
Windows Hardware Quality Labs, a name associated with Microsoft's hardware testing programs. A signature does not prove suitability for every system or Windows release.
Device Driver Guide stores a local consent preference to remember your choice. Replit Project Analytics may measure visits and selected site interactions. These local choices do not turn hosting analytics on or off. Custom events exclude form entries and other free-form content. No advertising scripts are active. Read the Cookie Policy.
