802.1x Wifi unable to connect after 2024-04 cumulative update

[Swennienl]

I cannot connect to 802.1x certificate based wifi's after installing the windows cumulative update of 2024-04. 

This only happens on Windows 11 systems. 

On Windows updates 2024-03 there are no issues. 

Wifi SSIS's wth a password are not an issue. 

I pulled the latest windows 11 ISO from Microsoft. These contain the updates for 2024-02. I did a fresh installation. I Used the HP assistant to install all the latest drivers. So far so good. I installed 2024-03 update without any issue. 
I downloaded the 2024-04 update (and only this one), and I cannot connect anymore. 

This happens on a HP Elitebook 860 G9 and G10.  Now somebody can say its related to the Windows update, so bug Microsoft. But when i tried this on a older EliteBook x360 G2 its not an issue. So its only for certain models.....

The only error I see when i try to connect is an security event: 
Error Code 0x80070285
EAP Reason code 0x285 
EAP Cause String: Internal Authentication Error. 
EAP Error Code 0x285

I can see there there have been some 802.1x issues in december 2023. But those should all be fixed in the 2024.02 updates. And that is what i can confirm...

So hopefully somebody recognizes this and can point me in the right direction. 
 

[LarsJuhlAdvania]

I might have exact same issue did you find a solution ? thanks

[CorbinNexus]

I have the same issue with the HP Elitebook 640 G10. After deploying it with Windows 11 23H2, it can't connect to our wifi 802.1x. It does not help to update drivers. The network card is Intel Wi-Fi 6E AX211 and if I try with an HP Pro x360 computer running with the same deployment of OS, it works fine. That second computer uses the same network card. 

I tried a third computer, HP Elitebook 640 G10, but I just booted up this one with the preloaded software without deploying it with our Windows 11 Enterprise, and it works. Now I will try to create a USB with Microsoft media creation tool and install an Elitebook 640 G10 to see how that works.

[Dudu40_volt]

Hi,

This workaround works for me. 

This was actually due to credential guard. . Fix: GP->Administrative Templates->System->Device Guard->Turn on Virtualization Based Security (set to DISABLED)

or run regedit - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard, create DWORD EnableVirtualizationBasedSecurity and set it to 0 (diasble).