I experienced the same issue mentioned above. The only thing that 'fixed' the issue was to use a static IP address. When I used a static IP address the network worked just fine but when I remove it the computer can no longer receive a domain IP address. This seems to be only an issue with authenticating to a domain network. This also applies to our domain WiFi connection. I can connect to our guest Wi-Fi network and get internet access and if I use my mobile phone as a hotspot I can get Internet access.
Win11 24H2 - DHCP issue - no Gateway
Not 100% sure if our problem is only with Win 11 24H2, but with 23H2 the problem does not occur. It is occurring on several systems right now - both when upgrading on a notebook in a WSUS test group and when reinstalling via a USB stick. I do not have the problem on at least one notebook (also test group).
No network connection can be established on these now 5 different systems - neither via LAN nor WLAN. The error was quickly identified (the gateway is missing in the network configuration), but after rebooting the gateway is missing again. If it is added manually, everything works.
We use DHCP. Settings checked and ok. The configuration is complete, i.e. IP, mask, DNS servers are correct - only the gateway is missing. ipconfig /release or /renew do not help. Wireshark shows nothing conspicuous.
When reinstalling, the notebooks get stuck during installation at the point where a network connection is to be established (despite cable and/or correct WLAN settings). With an unattend.xml the installation goes through, but the gateway is missing.
Same problem in homelab after wiping the disk and reinstalling. I therefore rule out problems with the infrastructure.
***Moved from Windows / Windows 11 / Internet and connectivity***
Windows for business | Windows Client for IT Pros | Networking | Other
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. To protect privacy, user profiles for migrated questions are anonymized.
14 answers
Sort by: Most helpful
-
Anonymous
2024-10-23T12:05:11+00:00 -
Anonymous
2024-11-26T01:55:31+00:00 Did you figure out a solution to the issue, or just downgraded to 23H2 again? I'm getting tired of assigning static IP addresses to client PC's.
-
Anonymous
2024-11-26T03:37:14+00:00 Did you figure out a solution to the issue, or just downgraded to 23H2 again? I'm getting tired of assigning static IP addresses to client PC's.
Sadly no, I reverted the computers to 23H2 and delayed our update ring for feature updates in Intune to 365 days until a subsequent update fixes this issue.
-
Anonymous
2024-12-05T09:11:16+00:00 We found solution for this.
https://support.microsoft.com/en-us/topic/november-12-2024-kb5046617-os-build-26100-2314-701f76d0-1127-43f5-a554-f562a940bc17#ID0EJBD=Catalog the files you find here: https://www.catalog.update.microsoft.com/Search.aspx?q=KB5046617
Install this files with:
Add-WindowsPackage -Online -PackagePath "c:\packages\Windows11.0-KB5046617-x64.msu"
This fixed DHCP problems.
-
Anonymous
2024-12-06T14:41:11+00:00 I just received some desktops from HP and it seems the patch has already been applied since I could join them to the domain right out of the box :).