My WIN11 pc is capped at 10mbs via ethernet cable after KB5077241 Preview update.

Question

Title: Realtek PCIe GbE (RTL8168) stuck at 10 Mbps after KB5077241 on Windows 11

System Info:

• OS: Windows 11 (26200.7922)
• NIC: Realtek PCIe GbE Family Controller (RTL8168)
• Driver before issue: v1168.16.1123.2023 (from motherboard manufacturer)
• Affected update: KB5077241 (2026-02 Preview Update, installed 25-02-2026)

Problem Description:

After KB5077241 was automatically installed, my Realtek PCIe GbE NIC (ETHERNET_MAIN) dropped from 100 Mbps to 10 Mbps link speed. Wi-Fi on the same network continues to deliver 60-70 Mbps, confirming the issue is isolated to the wired NIC driver.

Steps Already Attempted:

1. Forced Speed & Duplex to 100 Mbps Full Duplex via Device Manager Advanced tab — no effect
2. Disabled Energy Efficient Ethernet, Green Ethernet, Advanced EEE, Power Saving Mode, Gigabit Lite — no effect
3. Disabled 'Allow computer to turn off this device to save power' in Power Management tab — no effect
4. Reset TCP/IP stack via 'netsh int ip reset' and 'netsh winsock reset' — no effect
5. Attempted to uninstall KB5077241 via 'wusa /uninstall /kb:5077241' — failed with error 0x800f0825 (protected cumulative update)
6. Attempted DISM removal — also failed
7. Attempted System Restore — no restore point exists from before the update
8. Reinstalled the official motherboard manufacturer's Realtek driver — temporarily fixes the issue, but after reboot Windows Update silently overwrites it with the broken generic driver again
9. Added registry key ExcludeWUDriversInQualityUpdate = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate — did not prevent the driver from being overwritten via cumulative update
10. Added Hardware ID block via Device Installation Restrictions policy for PCI\VEN_10EC&DEV_8168 — did not prevent overwrite

Root Cause (suspected):

KB5077241 bundles a generic Realtek driver that overrides the motherboard-specific driver, causing the NIC to fall back to 10 Mbps. The bundled driver ignores forced Speed & Duplex settings and EEE configurations. Standard driver blocking policies are ineffective because the driver is embedded inside a cumulative security update rather than delivered as a standalone driver update.

Expected Behavior:

Windows Update should not overwrite a functioning, manufacturer-provided NIC driver with a generic version that causes a severe performance regression. Driver exclusion policies (ExcludeWUDriversInQualityUpdate) should also apply to drivers bundled within cumulative updates.

Question:

Is there any supported method to permanently prevent KB5077241 (or future cumulative updates) from overwriting a specific device driver, particularly when standard driver exclusion policies and Hardware ID blocks are being bypassed? Is this a known regression in KB5077241?

Answer 1

There is no supported policy-based method in the provided information that can reliably roll back or permanently block a specific driver version when it is delivered as part of a cumulative Windows update like KB5077241.

From the available guidance:

• Windows always installs drivers from the driver store, and Windows Update can add newer drivers there and then apply them to devices. If Windows Update detects a missing or older driver, it can reinstall or replace it, even after manual changes.
• To permanently remove a driver package so it cannot be re-used, the supported method is to delete that specific driver package from the driver store using pnputil (for example, pnputil /delete-driver <Published Name> /uninstall). However, if Windows Update later decides that driver is required, it can download and stage it again, so this is not a guaranteed long‑term block when the driver is embedded in cumulative updates.
• Intune/Windows Update for Business driver policies explicitly do not support driver rollback. The documented recommendation is to avoid broad deployment of problematic drivers by using deployment rings and manual approvals, not to centrally enforce a rollback once a problematic driver is already deployed.

Relevant points from the documentation:

1. Driver selection behavior
   • Windows searches the driver store first, then Windows Update and other locations, and selects the “best” matching driver package based on its internal ranking rules. When a better match is found (for example, a newer or higher-ranked Realtek driver), Windows stages it into the driver store and installs it, replacing the existing driver.
   • This behavior is by design and is not described as being overridden by ExcludeWUDriversInQualityUpdate or by hardware ID restrictions when the driver is part of a cumulative update.
2. Removing driver packages
   • The supported way to ensure a specific driver package is not reused locally is to remove that package from the driver store using pnputil /delete-driver <Published Name> /uninstall. This forces devices to fall back to another available driver package (for example, the OEM-supplied one) or to have no driver if no alternative exists.
   • The documentation also warns that Windows Update can reinstall a “necessary” driver, and that Windows Update settings might need to be adjusted to prevent this. No additional mechanism is documented that would prevent a cumulative update from reintroducing the same driver.
3. Policy limitations for rollback/blocking
   • Windows Update client policies do not support driver rollback.
   • The guidance for avoiding problematic drivers is to use deployment rings and manual approval so that issues are detected before broad rollout, not to block or roll back a specific driver once it is included in a cumulative update.

Based on this information, the only supported levers described are:

• Manually managing the driver store (using pnputil) to remove the problematic driver package and reinstall the OEM driver.
• Adjusting Windows Update behavior at a policy level to control which driver updates are approved and deployed in the first place (for managed environments using Intune/Autopatch), so that problematic drivers are not broadly deployed.

However, there is no documented, supported mechanism here that guarantees a specific driver embedded in a cumulative update like KB5077241 will never be reinstalled, nor any statement that this specific Realtek regression in KB5077241 is a known issue.

---

References:

• Using Device Manager to uninstall devices and driver packages
• How Windows selects a driver package for a device
• Step 2: A Driver Package for the Device is Selected
• Configure Windows driver update policies
• Windows Driver Update Policies FAQs