Silent Connectivity Failures Linked to Intel Driver Bug
According to a recent report by the German technology blog BornCity, a user discovered a critical bug in an Intel network driver installed via Windows Update. This flaw silently disrupts IPv6 network connections, rendering essential services such as Microsoft OneNote, Microsoft 365, OneDrive, Teams, and the Azure portal completely unusable.
The user explained that OneNote on their Samsung Galaxy Book continuously displayed empty notes for approximately three weeks, despite showing an “up to date” status. Consequently, they escalated the issue to Microsoft support in August of this year. However, five weeks elapsed without any resolution or identified root cause.
Forensic Investigation Exposes the Flaw
Ultimately, the user leveraged the Claude artificial intelligence model to conduct a comprehensive, packet-level forensic analysis overnight. Claude successfully captured Windows network traffic, measured the precise timing of connection resets, and systematically disabled network filter drivers. This rigorous troubleshooting isolated the true culprit: the Intel Connectivity Performance Suite (ICPS).
According to CircleID, the underlying problem originates within the ICPS traffic control driver. When processing IPv6 packets, the driver erroneously resets the IPv6 Flow Label field to zero for every TCP packet following the initial handshake. Under the strict RFC 6437 specification, the Flow Label must remain consistent throughout the entire lifespan of a connection. Microsoft’s cloud-edge load-balancing system relies heavily on this specific field to determine which backend server should receive the incoming packet. Once the label is cleared, subsequent packets are incorrectly routed to a different server that never participated in the original connection, prompting that bewildered server to return a reset signal.
Technical analysis from the official Intel community forum identifies the defective driver component as IntcCo11X64.sys version 11.5.11.19. This component functions as the traffic control engine for Rivet Networks, a company acquired by Intel, corresponding to the internal ICPS build 40.25.926.173.
Widespread Impact Across Major Manufacturers
Furthermore, this severe vulnerability extends far beyond the Samsung Galaxy Book. By examining the Microsoft Update Catalog, the user discovered 1,086 ICPS entries originating from 19 distinct companies, yet only a single entry corresponded to a verified, patched version. The potentially compromised driver packages affect prominent hardware manufacturers, including Samsung, Lenovo, VAIO, ASUS, HP, Dynabook, and Huaqin.
User diagnostics revealed that while ICPS remained active, zero out of 42 outbound packets retained their Flow Label, resulting in only four successful connections out of 10 IPv6 attempts. Upon disabling the INTCCoSvc driver, all 65 test packets maintained their labels flawlessly, yielding a 100 percent success rate across 10 connections. Notably, IPv4 connections remain completely unaffected, primarily because the IPv4 protocol lacks a Flow Label field entirely.
Partial Fixes and Frustrating Vendor Silence
On October 7, the user tested the official generic ICPS driver version 50.26.623.243 provided directly by Intel. The results demonstrated a flawless execution, successfully establishing all 169 attempted IPv6 connections. In stark contrast, the original OEM version installed via Windows Update succeeded only 138 times out of 170 attempts. Previously inaccessible platforms, such as the Azure portal and the Visual Studio Marketplace, now function perfectly on every single attempt. Curiously, Intel deliberately omitted any mention of an IPv6-related defect resolution in its official release notes.
The dedicated user has already submitted detailed feedback regarding this critical issue to Intel, Microsoft, and Samsung. On the Samsung community forum, moderators temporarily flagged the post as spam before eventually restoring it. Microsoft support transferred the case to the “OneNote Engineering Team” in August 2026, yet the user has received absolutely no further communication for six weeks. Similarly, Samsung created a formal support ticket on October 3, 2026, but has taken no subsequent action. Frustratingly, archival records from the Intel community forum indicate that another engineer described this exact problem back in November 2025; nevertheless, Intel simply asked a few preliminary questions before permanently closing the thread.
