Problem in network Windows 11 24h2

Solution for No Internet/Network Connection After Upgrading to Windows 11 24H2

Hi everyone,

I recently encountered an issue after updating to Windows 11 24H2. My system was assigned a 169.x.x.x IP address, resulting in no internet or network connection. After troubleshooting, I found a solution that worked for me, and I wanted to share it in case it helps someone else.

Here are the steps I followed:

1. Remove the WinHTTPAutoProxySvc Dependency

Open regedit (Registry Editor).

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WcmSvc.

Locate the DependOnService entry.

Remove WinHTTPAutoProxySvc from the list, leaving only RpcSs and NSI.

2. Enable the WinHTTP AutoProxy Service

In regedit, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc.

Locate the Start entry.

Change its value from 4 (disabled) to 3 (manual).

3. Modify Windows Connection Manager

Open Command Prompt (Admin).

Run the following command:

sc config WcmSvc depend= RpcSs/NSI

4. Reboot Your System

Restart your computer to apply the changes.

5. Set Up a Static IP Address

Assign a static IP address manually.

Note: I had issues pinging the gateway address even with a correct static IP during this step, but I continued with the next steps.

6. Reset the Network Stack

Open Command Prompt (Admin).

Run the following commands:

netsh int ip reset

netsh winsock reset

ipconfig /flushdns

7. Reboot Again

After the final reboot, I was able to ping my local gateway (set during Step 5). I then switched back to obtaining an IP address via DHCP, and everything finally worked again.

Additional Note: I also disabled my antivirus during the troubleshooting process, but I don't believe it made any difference in resolving the issue.

I hope this helps anyone else and maybe saves someone like a full day of debugging and trying... next time i think i will just install unix ;)

I have a few thousand endpoints under management currently, but come from large enterprise with 13,000 endpoints under management. NTLM was terminated as well as LLMNR in any environment we manage .... long, long ago. My observation with 24H2 is that it is a modernization, codification of the rewriting of the TCP stack and dependent components and services. The codification is where things that should have been disabled and removed in environments as far back as 2014 are finally being killed at the OS level. So the only items affected, are deprecated and ancient legacy technologies that should have been upgraded long ago or outright replaced to have no client-side component. Most of those apps should have been converted to SaaS applications accessible only via website or a Microsoft Store app.

I had to go to war with the check scanning upstream party to 6 different banks about a decade ago. Even then, the check scanning application had horrendous deprecated software dependencies.

If you have not looked into the new UAC model, you need to. Legacy apps are going to soon not work. They will be dead because of all their insecurities.

The software companies cannot maintain the legacy apps anymore. The software developers that once knew how to maintain them have all since retired or died. And the software companies cannot convince new software devs to work on that tech. A great example is .NET Framework. Just try to find a developer that has a clue about .NET Framework. So if you have software that is dependent on it, game over. Probably cannot find one and/or cannot afford to hire them.

You can review my prior posts. I posted the service dependency correction which was the only real problem/fix I found. I've been eradicating legacy apps from the environments for the last 10 years.

I think the next big bomb will be all the Windows 10 machines that will be replaced in the next 9 months with Windows 11 machines. The clock is ticking on all these apps.

The fix for no Wifi:

Open Regedit as admin

Look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wcmsvc

Open DependOnService and remove WinHTTP Web Proxy Auto-Discovery Services.

Click OK and reboot.

This simple fix works perfectly for me:

FIX FOR NETWORKING ISSUES AFTER Windows11 24h2 major update

Search for and open "Local Group Policy Editor" in settings:

Navigate to:

Local Computer Policy: Computer configuration: Administrative Templates: Network: Lanman workstation: Enable insecure guest logons - Enable

Reboot and problem is solved

To be clear, this is not a fix or a solution. This lowers the security of the OS and may be a suitable workaround for now for some of the issues with networking after the update, but it's not a fix.

Additionally, this does not solve the problem with using a USB network adapter and not getting DNS.

After updating to the new Windows 11h2, some machines experienced network issues with both cable and Wi-Fi. They connect but don’t get network access and receive an IP address starting with 169…, resulting in no internet or network connection. I updated drivers, firmware, and reset the network settings. The machines’ MAC addresses haven’t changed. Does anyone know what could be causing this?

Roberson,

Veja se você tem a opção 43 habilitada no seu DHCP Server.

Resolvi o problema aqui desativando essa opção.