This is really bad news as we use WPA3 here. This regression defects are crazy and the worst is that MS does not inform about them on the release notes nor they have a bug track tool to look for all of the current ones. So we need to expect additional issues with wireless connectivity in the future from MS side as far as they release this KB, or are you reporting them back this so to fix it? ... View more

That's good news @RaphaelL , could you please share the KB Id that seem to dfix these issues please? ... View more

Cisco has released an AP Service Pack to address this on 17.9.3 code (APSP1). This patch is integrated on 17.9.4 and next to be released 17.9.5, but also in 17.12.1 and 17.12.2 ... View more

@RaphaelL do you have a bug id, or ticket number, to which we can reference to Microsoft? In my case, the problem is that WinTel team do not open ticket to MS unless this ould be something critical, which is not the case. ... View more

@RaphaelL do you have any information about that special KB or the defect ID they have associated to this issue? Thanks a lot ... View more

But I see some omprovement has been added into release 30.1:   ... View more

@NitinVats the patch is for Cisco WLAN Infrastructure not for Meraki. They are releasing that patch for all software codes but for Cisco software not MEraki one, unless Meraki will be doing it as well. ... View more

I've experienced the same issues during the past 2 weeks using Cisco WLAN Infrastructure and Catalyst 9800. After discussing this with Cisco BU the engineer told me they were investigating this a month ago. They reached to a conclusion that the problem was that Windows clients were tunring from using OKC to legacy SKC, and that's why the client send a different PMKID to the AP. As the PMKID shared by Windows is not the one that the controller has and share for all APs in the same group, it rejects the client and the client is stuck with no current association. After 3 minutes Windows reset the connection an connect again with a full authentication so a new PMKID is generated until it fails again when roaming. This happen when using non-centralized forwarding such in the Meraki case. Cisco has released a patch for this behaviour to full de-authenticate the Windows client if the controller sees invalid PMKID, but they encourage clients to open a support case with Microsoft to analyse this and solve it. ... View more