Thank you very much! This was it for me. My organization had this value set to 4 (disabled) through Group Policy to prevent man in the middle attacks on all workstations so enabling it again worked (rollbacks to 23H2 also worked).
I'll give a summary of my experience in case it helps anyone. A number of my machines had no working wifi after updating to 24H2, however Bluetooth would work fine (and it's the same card running wifi and bluetooth). In Device manager it showed that it was working fine. In Control Panel it showed Disabled. If you enabled it, it would just go back to disabled with nothing much showing up in event viewer. In event log for the wifi adapter (Device Manager -> Network Adapter Properties -> Events) it showed that on the 24h2 update the device settings we're migrated from previous OS installation. After trying to uninstall and reinstall the device it would say the device settings we're not migrated from previous OS installation due to partial or ambiguous device match. Then i found that a USB wifi adapter also wouldn't work, and direct ethernet would connect for a second and then not work either (however it would get a dhcp address, but couldn't even ping the gateway). A USB C to ethernet connection (ie, through a dock) was the only thing that would work, so then I knew it was a Windows issue, not wifi or hardware. Then i found this post and it was the fix for me.
My best guess is that Windows 24H2 is now using auto proxy service to make a test connection somewhere to see it's connectivity (similar to how wifi tries to connect to that msftredirect site before completing the connection). When it can't use that auto proxy service, it just disables. Would love to know the real answer, but that's my guess. Our org has had this setting disabled for a couple of years and working fine through previous updates until 24H2.