This just happened to me but with the 2025 update....Yea...Trying to rollback but it is taking forever.
Problem in network Windows 11 24h2
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?
Windows for home | Windows 11 | Install and upgrade
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
269 answers
Sort by: Newest
-
Anonymous
2025-01-15T01:51:05+00:00 -
Anonymous
2025-01-10T17:28:06+00:00 I had similar issues after we started using Windows 11 24H2. The problem was that we disabled the WPAD and IP Helper services.
Once those were re-enabled, the network started working again, specifically WiFi.
This is not ideal since we had them disabled for a reason, but Microsoft made some fundamental changes for IPv6
-
Anonymous
2025-01-09T01:16:02+00:00 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.
When you did the manual settings, you must set valid values for:
- IP-address
- Netmask
- Gateway
Did you do all three?
Probably, since you did not disable the DHCP service, you should have skipped this step.
-
Anonymous
2025-01-08T20:28:06+00:00 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:
- 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.
- 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).
- Modify Windows Connection Manager
Open Command Prompt (Admin).
Run the following command:
sc config WcmSvc depend= RpcSs/NSI
- Reboot Your System
Restart your computer to apply the changes.
- 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.
- Reset the Network Stack
Open Command Prompt (Admin).
Run the following commands:
netsh int ip reset
netsh winsock reset
ipconfig /flushdns
- 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 ;)
-
Anonymous
2025-01-08T19:37:22+00:00 Super glad it worked for you as well. Blessings.