<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Windows KB5127648 Breaking 802.1X Authentication in ExtremeControl</title>
    <link>https://community.extremenetworks.com/t5/extremecontrol/windows-kb5127648-breaking-802-1x-authentication/m-p/122818#M2221</link>
    <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;Just to help others: if you started seeing 802.1X authentication problems (Wi‑Fi or Ethernet) after the October Patch Tuesday, check if the affected devices have KB5127648 installed. There are many reports of issues with PEAP‑MSCHAPv2, and in many cases removing the update restores connectivity.&lt;/P&gt;&lt;P&gt;This looks like another step from Microsoft to move away from older technologies based on NTLMv1/MS‑CHAPv2. There is a workaround by changing the Windows registry (BlockNtlmv1SSO=0), but in the long term it probably makes more sense to move to EAP‑TLS instead of continuing to rely on PEAP‑MSCHAPv2.&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/answers/questions/6036507/kb5127648-breaks-wpa2-enterprise-802-1x-peap-wi-fi?page=2#answers" target="_blank"&gt;https://learn.microsoft.com/en-us/answers/questions/6036507/kb5127648-breaks-wpa2-enterprise-802-1x-peap-wi-fi?page=2#answers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope this is helpful to someone.&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2026 11:01:19 GMT</pubDate>
    <dc:creator>dariusmp</dc:creator>
    <dc:date>2026-10-15T11:01:19Z</dc:date>
    <item>
      <title>Windows KB5127648 Breaking 802.1X Authentication</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/windows-kb5127648-breaking-802-1x-authentication/m-p/122818#M2221</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;Just to help others: if you started seeing 802.1X authentication problems (Wi‑Fi or Ethernet) after the October Patch Tuesday, check if the affected devices have KB5127648 installed. There are many reports of issues with PEAP‑MSCHAPv2, and in many cases removing the update restores connectivity.&lt;/P&gt;&lt;P&gt;This looks like another step from Microsoft to move away from older technologies based on NTLMv1/MS‑CHAPv2. There is a workaround by changing the Windows registry (BlockNtlmv1SSO=0), but in the long term it probably makes more sense to move to EAP‑TLS instead of continuing to rely on PEAP‑MSCHAPv2.&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/answers/questions/6036507/kb5127648-breaks-wpa2-enterprise-802-1x-peap-wi-fi?page=2#answers" target="_blank"&gt;https://learn.microsoft.com/en-us/answers/questions/6036507/kb5127648-breaks-wpa2-enterprise-802-1x-peap-wi-fi?page=2#answers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope this is helpful to someone.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2026 11:01:19 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/windows-kb5127648-breaking-802-1x-authentication/m-p/122818#M2221</guid>
      <dc:creator>dariusmp</dc:creator>
      <dc:date>2026-10-15T11:01:19Z</dc:date>
    </item>
  </channel>
</rss>

