I mean, that’s the kind of thing you’d have to try. Of the devices listed I would say as long as they’re running the latest software they should have no issue, with the Windows PC being an exception (driver/card related). Profile reuse bugs are still a thing in 2025 unfortunately. Forgetting and re-joining the network once it’s configured as desired would be an important step on problematic devices.
The SSID for my personal devices is set to required for both and has been running without issue within a day or two of this topic being created. Also, the topic is a bit derailed from the original context, imho, and hard to know where things were left off..
I’ve been using iPhone 16 Pro Max, Galaxy S24 Ultra, 5th gen iPad Pro 12.9 (M1), MacBook Pro (M2), and a Windows 11 PC (RTL8822BE NIC) on that SSID. I do not use Fast Roaming, if that matters. All of my other devices are on a WPA2 only SSID to leverage AltaPass, so it’s literally just those 5 devices on this SSID.
Let’s take a step back for a minute though.. The biggest issue is when we made the change to fix PMF options so they were technically correct we stopped force enabling PMF when WPA3 was set to on (or required). This matters because prior to that we forced set PMF to optional or required, depending on WPA3 mode. When we removed that forcing, people didn’t realize that they had wrongly configured their SSID (because we force enabeld a feature behind the scenes) and then ended up in a broken state. You cannot have WPA3 without PMF, it’s literally part of the spec, so when you have an SSID like that (WPA3 on, PMF off), at least Android and iOS devices will outright mark it as invalid and hide the SSID from the list.
EDIT2: That last bit is definitely different than your original report, but likely explains the not quite related me too reports scattered throughout this topic. I still think profile re-use is the most likely culprit for issues encountered with an otherwise valid config, or at least that’s the definite starting point.
Please try reverting the SSID to the desired config, and then if the Windows PC or S23 are still problematic I would suggest forgetting and re-joining the network. Then observe and debug from there, depending on outcome.
Last thing I remember was I did all those things, like rebooting, forgetting and rejoining networks, making sure On * 2 or Required * 2. But, I’ll give it a shot again and report back 
