This defect isn't new. Users have publicly reported the same failure pattern on Intel's connectivity software since at least 2021. In September 2025, an engineer gave Intel the exact mechanism on Intel's own forum. Intel closed the thread, the engineer posted it again in November, and Intel closed it again.
Intel Connectivity Network Service is causing the ipv6 flowtable attribute set to 0 (first posted 2025-09-12; re-posted 2025-11-03 on the Wireless board)
- On an HP ZBook Firefly 14 G11, the author identifies Intel Connectivity Performance Suite, delivered through Windows Update as "Intel Corporation - SoftwareComponent - 4.1025.207.1". When the TLS handshake starts, it clears the IPv6 flow label. The author explains that this breaks ECMP in large cloud networks, because the flow is "randomly send to different backend device after tcp handshake". The post includes a
curl -6reproduction against an Azure endpoint, and stopping the service fixes it. - Intel asked for details, then closed the inquiry, on 2025-09-22 and again on 2025-11-12: "As I haven't received a response, I will proceed to close this inquiry."
- In June 2026 other organizations added the same symptom to the thread: M365 Search and SharePoint fail with
ERR_CONNECTION_RESETon IPv6, on HP EliteBook X Flip G1i and EliteBook 8 G1i laptops, and disabling the Intel service fixes it. One adds that removing the software "took just one Windows Update and the problem was back".
Intel Connectivity Performance Suite causes intermittent IPv6: on an ASUS Vivobook S 14 with Intel Wi-Fi 7 BE201 and ICPS 40.25.725.165, 40–60% of IPv6 connections to AWS CloudFront were reset, and none after removing ICPS. Intel replied that it had "no confirmed public advisory for this specific behavior" and suggested trying another version.
More reports, by laptop maker: Not only Samsung.
| Date | Where | What users saw | What fixed it |
|---|---|---|---|
| 2021–2022 | jQuery CDN issue on GitHub |
curl -6 reset, curl -4 fine. The CDN found nothing on its side. |
Owners of Dell XPS and Alienware machines traced it to Killer software |
| 2022 | Microsoft Q&A | Connection resets only on Microsoft sites (Bing, Office, SharePoint, LinkedIn) | Uninstalling or disabling Killer, or disabling IPv6. Windows Update reinstalled Killer. |
| 2022–2025 | Intel Community | Resets only over IPv6 | Disabling the Killer Network Service. Intel blamed the user's ISP. |
| 2023–2024 | Intel Community | Teams/SharePoint, OneDrive sign-in and Outlook broken. One user spent three weeks with Microsoft 365 support, then paid for a technician. | Disabling the Killer Prioritization Engine |
| 2024 | Microsoft Q&A |
ERR_CONNECTION_RESET on some sites, including Bing |
Disabling the Killer services or IPv6 |
| 2025 | Brave Community | Resets on several new Lenovo laptops | Disabling the Intel connectivity service |
| 2026 | Vivaldi forum | ERR_CONNECTION_RESET |
Stopping the Intel Connectivity Network Service |
A public remediation script for IT administrators also warns that Intel Connectivity Performance Suite "may cause network issues when IPv6 is enabled".
The reports above are summarized from the linked public pages. The November 2025 Intel thread was checked directly on 2026-10-03.
- Wire-level proof at the Wi-Fi miniport: SYN 24/24 labels kept, ACK/data 0/42. The RST comes from a different machine (hop limit 49 vs 47).
-
The exact component: the
IpV6 Egress Transport CalloutinIntcCo11X64.sys11.5.11.19, registered withFWP_CALLOUT_FLAG_CONDITIONAL_ON_FLOW. - A controlled A/B test showing that stopping only the bandwidth-management service doesn't help, while stopping the traffic-control driver fixes 100% of connections.
- The consumer impact: OneNote desktop silently showing empty notebooks as "Up to date" for nearly three weeks, plus an escalated Microsoft support case that never found the cause.
Intel had the mechanism in writing more than a year before this report and closed the thread twice. Users have been told to blame their ISP, reinstall Office or pay for technicians. Windows Update keeps putting the software back after people remove it.