This usually isn’t Meraki suddenly enabling splash. It’s Windows 11 behaving differently during network checks. When Windows thinks a network has limited or uncertain connectivity, it tries to validate internet access with a browser test. If that check doesn’t pass cleanly, it assumes a captive portal exists and throws the action required prompt. With 802.1X, this can happen if authentication is slow, delayed, or briefly fails. Some Windows 11 builds are more aggressive about this than Windows 10. Timing, drivers, or NAC posture checks can trigger it. Meraki logs it as splash because Windows is probing. It’s more of a client-side detection issue than an SSID misconfiguration.
... View more