Windows 10 version 20H2 does not connect to the meraki SSID

[Electronic20]

I have windows version 20H2 devices, which do not connect to the SSIDs that have "Meraki Cloud AUthentication" authentication, a user with a password was created in "User management portal" the user is the email and a password.

But using the same account but on a computer that has windows version 22H2 if it connects.

Please help me solve this issue, since in other Wi-Fi solutions the equipment does connect.

[DarrenOC]

Hi @Electronic20 , please reach out to Meraki support.  You can find the contact details within your dashboard 

[alemabrahao]

Try disabling 802.11w and 802.11r.

[Electronic20]

Hi, @alemabrahao 

I have this configuration implemented.

You are using 802.1x with "Meraki Cloud AUthentication", but it does not register with username (email) and password, defined in this option:

With windows 22H2 if you connect, but using the same account you can not connect with computers that have windows 20H2, but if I change it with to PSK if you connect the laptop with windows 20H2.

Would Meraki have any blocking option? If so, which Meraki option should be reviewed to unlock said option?

[alemabrahao]

About Two-factor authentication it's just a recommendation. Is the user authorized on the dashboard?

[Electronic20]

I am not using Two-factor authentication, I am only creating the account for 802.1x for "Meraki Cloud AUthentication", the user is authorized, also that same user I try it on another laptop with version of windows 22H2 and if the account works.

But with the version of windows 20H2 the account does not work, this error message appears:

[cmr]

Is it the same hardware, what is the wireless chipset and if intel, what driver versions are used?

[Electronic20]

update the version of windows 20H2 to 22H2 and if you can connect the wifi with 802.1x of the "Meraki Cloud AUthentication", apparently it is not wireless chipset.

la versión 20H2 tendrá alguna incompatibilidad con el Meraki usando el  "Meraki Cloud AUthentication"?

[alemabrahao]

Just updated the Windows machine. It's not a Meraki issue.

[cmr]

@Electronic20 Windows 10 22H2 will have newer drivers for most wireless chipsets.  If the devices have intel chipsets the driver update that is part of 22H2 could be the fix.  If you cannot update the other devices to 22H2 then try to get the latest wireless drivers on to one and see if that fixes the problem.

[BlakeRichardson]

If updating solves the problem then why not update the devices? 20H2 is very long in the tooth now. 

[Electronic20]

The end customer does not want to update the equipment since there are several and it takes too long, it indicates that with other manufacturers of Wi-Fi equipment it can connect without problems without considering whether Windows 10 has version 20H2 or 22H2

[alemabrahao]

I'm sorry, but in addition to fixing bugs, updates are important to fix system vulnerabilities. Does he have this in mind?