Microsoft recently released Windows 11 24H2. Not long after the release there have been numerous reports of DirectAccess failing after performing an in-place upgrade from previous versions of Windows 11. New installations of Windows 11 24H2 experience the same problem.
Update 10/28/2024: This issue is resolved with KB5044384.
Testing
After downloading and configuring a Windows 11 24H2 test client I was able to quickly reproduce the issue. While previous versions of Windows 11 can connect to my test DirectAccess server without issue, the Windows 11 24H2 client fails.
Troubleshooting
Looking at the DirectAccess status indicator in the UI the DirectAccess connection remains ‘Connecting’ perpetually. Further investigation indicates an IP-HTTPS interface error. Running the command netsh.exe interface httpstunnel show interface reveals an error code 0x57 (invalid parameter) with the following error message.
Failed to connect to the IPHTTPS server. Waiting to reconnect.
Workaround
Currently there is no known root cause for this issue and there is no available workaround. Administrators should delay upgrading to Windows 11 24H2 if DirectAccess is deployed in the organization. I will continue to investigate and post additional information as I learn more. Stay tuned!
Additional Information
Troubleshooting DirectAccess IP-HTTPS Error Code 0x800b0109
Troubleshooting DirectAccess IP-HTTPS Error Code 0x90320
Troubleshooting DirectAccess IP-HTTPS Error 0x80090326
Zach
/ October 7, 2024Technically, the workaround is to use Always On VPN. 😉
Richard M. Hicks
/ October 7, 2024That’s for sure! 🙂
Phil Ready
/ October 7, 2024Hi Richard, do you know if AOVPN is affected?
Cheers
Richard M. Hicks
/ October 7, 2024Not to my knowledge. I certainly haven’t heard any reports as such. I haven’t done any testing myself, though. I’ll post something if I hear anything or run into any issues myself.
Richard M. Hicks
/ October 7, 2024I’ve just finished testing Windows 11 24H4 with Always On VPN and have no issues to report. Works perfectly. 🙂
Tony Gaston
/ October 28, 2024Microsoft support engineer here, this issue is fixed in the October preview release of the November cumulative update.
https://support.microsoft.com/en-us/topic/october-24-2024-kb5044384-os-build-26100-2161-preview-5a4ac390-7c7b-4f7f-81c2-c2b329ac86ab
Richard M. Hicks
/ October 28, 2024Thanks for checking in, Tony! I’ve updated the post to include this information. Also, my testing and that of several of my customers has confirmed this issue is resolved.