Problem in network Windows 11 24h2

Anonymous

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?

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.

0 comments

269 answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2025-02-16T15:04:17+00:00

We have a SEVERAL PC ALL IN ONE of HP 440 G9 WITH Windows 11 PRO VER 24H2 I configure all IP address in ethernet network adapter including KM-TEST LOOPBACK NETWORK ADAPTER WITH FIREWALL IP ADDRESS LIKE 10.135.249.26 . BUT SYSTEM NOT REPOND FOR OUR DEPARTMENT SOFTWARE . AND SYSTEM NOT READ ABOVE IP ADDRESS . FOR RUNNING PROGRAMM . WHILE NETWORK CONNECTED WITH DEFAULT NETWORK ADAPTER

SO PL HELP ME WHAT CAN I DO

I am a zubair ahmad
Was this answer helpful?

0 comments No comments
Anonymous

2025-02-26T18:14:47+00:00

My workstation just flips back and forth between "media disconnected" and fine.

Had the problem in October and reverted and then blocked update.

Yesterday it did the update anyway and the same problem is back.

Wired LAN
Was this answer helpful?

0 comments No comments

Anonymous

The update was also installed a second time (this time, without asking prior)

I had 2 problems:

erratic display with the RDP connection to older machines (Win 7, Server 2008) -- this is fixed now

networking problems

The networking problems are still there.

Let me remind my setup.

I have a DNS server, which resolves the internal hosts (domain suffix .home.local) and forwards the other requests to a public resolver.

I have a DHCP server, which provides in the option fields: the domain suffix, the IP address of the DNS resolver, the IP address of the default gateway.

All of this uses only IPv4.

Since the update, 24H2 adds a rogue IPv6 DNS server on top of the DNS servers list - staying before my own DNS server. As a result, none of my internal hosts are resolved by their name.

See here the IPCONFIG /ALL output:

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : home.local
   Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
   Physical Address. . . . . . . . . : D4-54-8B-71-1B-9B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2a02:a03f:6b56:f000:1d93:354b:99df:fe43(Preferred)
   Temporary IPv6 Address. . . . . . : 2a02:a03f:6b56:f000:5529:2eed:c3d6:5176(Preferred)
   Link-local IPv6 Address . . . . . : fe80::f0ce:9414:ba29:f9b8%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.68.85(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, 21 February 2025 22:11:07
   Lease Expires . . . . . . . . . . : Saturday, 22 February 2025 22:21:07
   Default Gateway . . . . . . . . . : fe80::3a35:fbff:fe31:81ee%15
                                       192.168.68.1
   DHCP Server . . . . . . . . . . . : 192.168.68.5
   DHCPv6 IAID . . . . . . . . . . . : 164910219
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-50-9F-B5-7C-8A-E1-BE-3C-D8
   DNS Servers . . . . . . . . . . . : fe80::3a35:fbff:fe31:81ee%15
                                       192.168.68.5
                                       192.168.68.1
                                       fdaa:fbbc:bfdd:eef0:ff:f1d0::
   NetBIOS over Tcpip. . . . . . . . : Enabled
   Connection-specific DNS Suffix Search List :
                                       home
								   
C:\Users\f>ping fe80::3a35:fbff:fe31:81ee

Pinging fe80::3a35:fbff:fe31:81ee with 32 bytes of data:
Reply from fe80::3a35:fbff:fe31:81ee: time=7ms
Reply from fe80::3a35:fbff:fe31:81ee: time=3ms

The workaround has been to deactivate IPv6 in the network card properties.

0 comments

Anonymous

2025-02-27T17:08:54+00:00

While After months of being hopeful that Microsoft would resolve an issue they clearly created, we have moved on. We paused updates for the devices experiencing this issue and revisited the update every 5 weeks. Everytime the 24h2 update was installed the network connectivity would fail for both ethernet and wifi. Each time we rolled back to Windows 23H2 resolving all of the issues until the next attempt. We have tried every fix posted in this community during our testing none of which resolved the issue.

Ultimately we have re imaged the devices that were experiencing this problem about 2.5% of our devices and this has resolved the issue. Each device is now running 24h2 without issue.

Thank you to everyone who has taken the time to try and help out here.
Was this answer helpful?

0 comments No comments