Vendor reports and status

Last updated: 2026-10-28. "Filed" means submitted or published. It does not mean a vendor has acknowledged, reproduced or fixed anything.

Intel

Channel Visibility Status
Intel Community, Wireless board Public Posted 2026-10-02.
Intel Customer Support case Private Opened 2026-10-02. On 2026-10-06 Intel asked for a test with its generic ICPS package. Results sent 2026-10-07: the generic 50.26.623.243 does not have the bug. Asked Intel which version fixed it, to get the fix to OEMs and Windows Update, and to publish an advisory. On 2026-10-07, sent Intel the list of other affected laptop makers and organizations. Intel Customer Support replied (by 2026-10-08) that it had passed requests to its team for an advisory naming the affected and first fixed versions, notice to every OEM shipping affected builds to supersede them on Windows Update and in their own tools, work with Microsoft to stop Windows Update offering the broken builds, and an engineering escalation to confirm which driver version fixed the flow label and why the release notes don't say so. Intel promised a status update by 2026-10-13. On 2026-10-13 Intel replied that the installed package is Samsung's OEM build, recommended asking Samsung for its latest OEM version, and said that the advisory, OEM notification and Microsoft coordination requests fall within Samsung's scope as the OEM. In the same reply Intel acknowledged in writing, citing the owner's tests, that its generic 50.26.623.243 (driver 12.10.14.33) does not zero the flow label. The same day, Intel was asked, as the maker of the driver, whether driver 11.5.11.19 in the OEM package is Intel's own unmodified build, which driver version first keeps the flow label, whether Intel has told the laptop makers, and what came of each request it listed on 2026-10-08. A written answer was requested by 2026-10-21. On 2026-10-14 Intel replied that "The information previously shared represents the full extent of what we are currently able to provide", and, on the request for a contact at a higher level, that the owner "will be reached out to as soon as possible". No such contact as of 2026-10-28. On 2026-10-20 a different Intel agent wrote that Intel is "still actively reviewing this matter internally", asked whether Samsung had sent any update, and said the case would be "temporarily closed" without a reply by 2026-10-22. The same day, the owner replied that Samsung had sent nothing since 2026-10-09, reported Microsoft's status, and restated the questions only Intel can answer. On 2026-10-21 Intel asked for "some additional time", then for a copy of Microsoft's written confirmation, a Microsoft case number or a link to a Microsoft support thread, before it would "proceed with the requested re-escalation". On 2026-10-26 Intel closed the case. It wrote that its engineering team "has successfully shared and submitted your feedback to the appropriate OEM teams as well as Microsoft for their awareness and review", without saying which laptop makers or when, and sent all further follow-up to the laptop maker. None of the questions has been answered, and no one at a higher level has made contact.

Microsoft

Channel Visibility Status
Feedback Hub: OneNote Public Filed 2026-10-02 with the full root-cause report attached.
Feedback Hub: Windows networking / WFP Public Filed 2026-10-02 with the full root-cause report attached.
Feedback Portal idea (OneNote) Public Opened 2026-08-27 for the symptom. Root cause added as a comment on 2026-10-02.
Microsoft Q&A thread Public Answer with the root cause and workaround posted 2026-10-02, for other users with the same symptom.
Microsoft Support case Private Opened 2026-08-27 and escalated to OneNote engineering. It never found the cause. No further message from Microsoft Support has been received in the case since the escalation. Full root cause sent 2026-10-02. On 2026-10-07, asked for a case owner and escalation to the Windows Update driver-distribution team and Azure Front Door. No answer as of 2026-10-28.
Microsoft Executive Customer Relations Private Letter to the Office of the CEO sent 2026-10-07, asking for a named owner for the support case. On 2026-10-08, a relationship manager from Executive Customer Relations opened a new case. After a phone call on 2026-10-09, the full write-up was sent the same day. The owner asked Microsoft to consider a goodwill gesture in recognition of the root cause that Microsoft's own engineers are acting on, and cited no contract, license or warranty. On 2026-10-14, Executive Customer Relations turned the request down, called its decision final, and named no review channel, reference, owner or date for a Windows Update fix. The owner asked for a review of the decision by an Executive Customer Relations manager, for the reference, owning team and Windows Update date of the engineering review, and for how to deliver the logs. On 2026-10-16 it replied by citing the warranty terms of the Windows license, under which remedies are limited to repair, replacement or refund, and any recovery that the law still allows is limited to the amount paid for Windows, or up to US$50 if Windows was obtained without charge. It wrote that "Microsoft did not commission or enter into an agreement to purchase your investigation, testing, or findings", and that its decision "will not be reconsidered through this case". The reply was signed by the same relationship manager and named no manager to review the decision, and no engineering reference, owning team or date. For the logs, it sent a ten-step guide to Feedback Hub, where the owner had filed two reports with the full root cause on 2026-10-02, as the owner had told it on 2026-10-14. It added: "A submission does not guarantee an individual response, an engineering owner, or a remediation date."
Azure Networking engineering Private Packet-level evidence sent to Azure Front Door engineering leadership on 2026-10-07. On 2026-10-08, Microsoft confirmed the problem: when a client changes the flow label after the SYN, routers that hash on the label send the rest of the connection to a different Azure Front Door server. Microsoft said it has asked its team to work with the Windows team on a fix, and is working on the Azure Front Door side to reduce the impact. No date given. A request for a rough timeline, sent the same day, has had no answer as of 2026-10-28.
Microsoft support escalation Private On 2026-10-08, a senior Microsoft leader passed the support case to his escalation team, which "should be reaching out shortly". No message identifying itself as coming from that team has been received as of 2026-10-28. Executive Customer Relations opened its own case the same day.

Samsung

Channel Visibility Status
Samsung Community US, Computers board Public Posted 2026-10-02, hidden by Samsung's spam filter, restored by a moderator. Update with the October 7 results posted 2026-10-07.
Samsung Care live chat (Laptop Department) Private Case opened 2026-10-02 and noted for escalation to Galaxy Book software engineering. No follow-up from Samsung. In a second chat on 2026-10-07, Samsung said the first case was "only for documentation" and that it has no software engineering escalation department, and referred the owner to Amazon and a US phone line. A supervisor offered troubleshooting or a repair, then gave the address of Samsung Electronics America's Office of the President. A second case was opened. In another chat on 2026-10-09, a supervisor opened an escalation ticket for the Office of the President under Samsung Electronics America, and said the team would make contact "within 24 to 48 business hours". No contact as of 2026-10-28.
Samsung Electronics America, Office of the President Private Formal complaint sent 2026-10-07, asking Samsung to put the fixed package on Windows Update and for a written reply from a named contact within 14 days. An escalation for it was opened through live chat on 2026-10-09 (see above). The complaint was forwarded to Samsung Russia, apparently because the owner's email address ends in .ru (the owner does not live in Russia). Samsung Russia replied on 2026-10-09 that it could not help or pass the information to the "Galaxy Book Software development department", and recommended contacting the Samsung office of the country where the laptop was purchased, which is Samsung in the US, where the complaint started; a reply pointing this out went to the Office of the President the same day. No contact or answer as of 2026-10-28; a follow-up was sent on 2026-10-28 after the 2026-10-22 deadline passed.

Not yet received