An open discussion list for topics related to the geteduroam service

["Yannis Naumann" <naumann AT hrz.uni-marburg.de>]

Hi Paul,

Thank you for your response. It seems to be a bug in the Realtek 8922AE 
driver.
I've checked two devices with this issue; both were Lenovo Yogas with the 
same Wi-Fi chip and driver version, but with different Windows 11 builds. I 
will report back if we encounter the same issue with a different Wi-Fi chip.
Thanks for the help!

Device 1:
Lenovo Yoga 7 (2-in-1) 16akp10
Windows:
Windows 11 Home 25H2 26200.8655
Driver:
Realtek 8922AE WiFi 7 PCI-E NIC
14.04.2026
6102.24.108.353

Device 2:
Lenovo Yoga 7 (2-in-1) 16akp10
Windows:
Windows 11 Home 25H2 26200.8737
Driver:
Realtek 8922AE WiFi 7 PCI-E NIC
14.04.2026
6102.24.108.353

Kind regards,
Yannis

Am Freitag, 19. Juni 2026 18:59 CEST, schrieb "Paul Dekkers" (via geteduroam 
Mailing List) <geteduroam AT lists.geant.org>:

> Hi Yannis,
> 
> On 12/06/2026 09:12, "Yannis Naumann" (via geteduroam Mailing List) wrote:
> > Hello everyone,
> > 
> > We are currently experiencing some issues with the geteduroam app on 
> > Windows 11 devices. Our eduroam Wi-Fi uses WPA3-Enterprise (CCMP128). 
> > When setting up eduroam via geteduroam.exe, the profile is added, but a 
> > connection cannot be made because the installer chooses WPA2-Enterprise 
> > as the security type. Some devices don't mind and still use WPA3, but 
> > more and more devices require WPA3 to be chosen specifically.
> > Would it make sense to set WPA3 as the default in the installer, given 
> > that it is backwards compatible?
> > 
> > Thank you for your help!
> 
> That sounds odd and something we've not encountered. Funny thing is that 
> we do this for compatibility with both encryption standards, both in 
> geteduroam and CAT.
> 
> If you're setting it WPA2-Enterprise it's my belief this works with both 
> WPA2 and WPA3. If you configure WPA3-Enterprise, it will no longer 
> accept WPA2 networks (not even with PMF optional/enabled).
> 
> Other vendors behave similar; WPA2 would work for both but WPA3 would 
> not "downgrade".
> 
> So that backwards compatiblity thing from WPA3 is not true as far as I'm 
> aware.
> 
> Your issue could be driver specific?
> 
> We have a large userbase, and tested this way of configuring ourselves, 
> but did so far not have issues, but let's keep our eyes open. If you can 
> be more specific about the drivers/platform/Windows update version, we 
> can try to reproduce perhaps. It's also helpful if you find that other 
> clients with the same Windows version but different hardware do work, 
> for instance.
> 
> Paul
> 

-- 
Yannis Naumann
Abteilung Kommunikation
Hochschulrechenzentrum (HRZ)

Philipps-Universität Marburg
Hans-Meerwein-Str. 6
35032 Marburg
Büro: Gebäude H|04, Raum 06A11

T +49 6421 28-23598
E naumann AT hrz.uni-marburg.de

https://www.uni-marburg.de/de/hrz