Microsoft has released a KIR to mitigate the issue:
https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#2955msgdesc
DirectAccess keeps reconnecting after installing Windows 11 updates
After installing the following updates on Windows 11 22H2 DirectAccess state remaining Connecting after disconnect/connect a network:
- KB5018427
- KB5019509 (adds tabs to Explorer, taskbar overflow menu)
- KB5019980
These updates are tested stand-alone and after each other and/or different sequence, all resulting in a DirectAccess state remaining Connecting.
Anybody any idea what is causing this? A reboot of the laptop resolves the issue momentarerly but if the network disconnects/connects (drop on Wifi e.g.) the DirectAccess never connects again and another reboot is necessary. The issue is also on Windows 10, caused by at least these updates; KB5020953 and KB5019959.
-
coldKingdom 101 Reputation points
2022-11-14T07:28:51.6+00:00
1 additional answer
Sort by: Most helpful
-
Gary Baer - US 1 Reputation point
2022-11-12T00:02:47.583+00:00 We are having the same symptoms across our enterprise, though not every system. It is still in the hundreds, but not all; As it mostly goes unreported by a remote community used to "rebooting" when they have network issues, we don't have an exact ratio or device count. But it is very widespread based on the sampling we have done thus far.
I can confirm that after applying KB5019959 and rebooting, Direct Access does connect initially. Then at some point after logging in, perhaps there is a network latency, the DA connections drops and goes into an infinite "connecting" status. We can connect at that point to Anyconnect VPN with no issue. Drop VPN connection and DA remains in "Connecting" status.
After a reboot DA reconnects and we are fine until it "hiccups" again. Then it requires a reboot to get DA to reconnect. It seems that any network blip disconnects and leaves the DA connection unable to reconnect.
So far, the only thing we can do to resolve the issue is to uninstall KB5019959 and disable redeployment of that November update until MS comes out with a patch. Sad, though, since that KB resolved so many vulnerabilities and I believe it worked out 6 Zero Day's!!!
Anyone come up with a better solution?