Problem in network Windows 11 24h2

I didn't have issues with internet access, but I did run into a problem accessing my network drive. Drive showed up, but was blocked by a security issue of some kind. Drivers were fully updated and verified the settings in the router. Verified the sharing settings. Rolled back to 23H2 and got access to the drive back.

Bij mij ook alles weg ben twee uur bezig

Geweest met die zooi

We have found the source for our problems, it seems with the update, it came with dependecies on some really oooooold service.

So here is what we did with the computers that the network doesnt work, I think there was also the solution with the regedit somewhere in this thread.

Procedure 1 (if device has no network at all - mostly PCs):

a. Obtaining LAPS or using a pcadmin account

b. Starting the CMD command line as pcadmin/Administrator

c. Entering the line: sc qc wcmsvc

d. Reviewing the lines entered

c. Enter a new line sc config wcmsvc depend= RpcSs/NSI

d. And check the success of the entry: sc qc wcmsvc

e. Reset the computer

OR

Procedure 2 (mostly for laptops if their LAN connection works):

a. Run Regedit as Administrator/pcadmin

b. Look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc

c. In the folder, find the DWORD "Start" the current value will be 4 (disable)

d. Enter a new value 3 (start)

e. Save

f. Reset the computer

This should fix the issues, it works at least in our company environment.

Hope it helps!

Regards,

Miloš

We have found the source for our problems, it seems with the update, it came with dependecies on some really oooooold service.

So here is what we did with the computers that the network doesnt work, I think there was also the solution with the regedit somewhere in this thread.

Procedure 1 (if device has no network at all - mostly PCs):

a. Obtaining LAPS or using a pcadmin account

b. Starting the CMD command line as pcadmin/Administrator

c. Entering the line: sc qc wcmsvc

d. Reviewing the lines entered

c. Enter a new line sc config wcmsvc depend= RpcSs/NSI

d. And check the success of the entry: sc qc wcmsvc

e. Reset the computer

OR

Procedure 2 (mostly for laptops if their LAN connection works):

a. Run Regedit as Administrator/pcadmin

b. Look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc

c. In the folder, find the DWORD "Start" the current value will be 4 (disable)

d. Enter a new value 3 (start)

e. Save

f. Reset the computer

This should fix the issues, it works at least in our company environment.

Hope it helps!

Regards,

Miloš

I appreciate the help. I would caution enabling WPAD from a security stand point. In-the-Wild WPAD Attack | How Threat Actors Abused Flawed Protocol For Years (sentinelone.com) We found in one of our cases that adding a static IP with a different DNS helped, but it is not a long-term solution with our infrastructure, and it is better for us to roll back when possible. I am hoping for a Microsoft fix :)

Thanks,

William

Hi all

we had the same issue. It is caused by Win11 Device Security settings, Win 11 23H2 suffers the same fate. These features I believe are now turned on by default with this release when using Enterprise and Education Versions on Win11. If using a GPO you can set this feature to Disabled here. Howver this substantially reduces your security posture so is not recommended.

The underlying issue is that MS-CHAPv2 is no longer a secure auth method so you will nead to switch to EAP-TLS Certificate Based Auth when using Wireless Authentication. I need to emphasise this was our experience so, use this at your own risk (TEST TEST TEST!!!) and please use this setting with caution as it is a bit of a mission once you Disable this setting to reinstate default Windows Security settings such as Core Isolation, Driver Guard etc... but it is a temporary work around for now.

We have now permanently overcome this issue by means of configuring our Enterprise CA, to issue Machine and User Certs throughout our Domain using Auto Enrollment GPO Policies and authenticating using EAP-TLS Thankfully the issue is no more....