I experiencing the same issue on. On multiple machines.
We also have this problem on multiple machines.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
I experiencing the same issue on. On multiple machines.
We also have this problem on multiple machines.
I experiencing the same issue on. On multiple machines.
O meu deu o mesmo problema na atualização, 23H2 para 24H2, a store diz que não tenho conexão, na primeira não consegui fazer a reversão, mas quando conectei o Android via usb e liguei o Tethering foi concluída reversão do sistema.
I may have this figured out - for my case anyway. The new ADMX templates include 2 new settings related to DNS. I tried the one and that didnt' work, so I tried the other and now I'm always getting DNS. The setting in group policy editor;
| Turn off default IPv6 DNS Servers | HKLM\Software\Policies\Microsoft\Windows NT\DNSClient!DisableIPv6DefaultDnsServers | At least Windows Server 2012 Windows 8 or Windows RT | If you enable this policy the DNS client will not use the default IPv6 DNS server addresses provided by Windows. |
|---|
I enabled this setting to effectively turn off the default IPV6 DNS addresses. WHY??? WHY???? WHY? is this even a thing? And why does it need to be turned off? This should be one of those settings that the unconfigured option should have the default provided dns addresses disabled. OY, Microsoft!
I tested several computers yesterday and restored them to full functionality by simply removing the winhttpautoproxysvc service from dependency.
That service should be disabled because it is insecure.
The exact fix I found to work 100% of the time is:
HKLM\System\CurrentControlSet\Services\WcmSvc
In the root of the key, look for value DependOnService.
Edit it.
Remove WinHTTPAutoProxySvc
Save.
Start Windows Connection Manager service. Start WLAN AutoConfig service.
Then location services complains about being off. Go into Settings, Location. Turn OFF the notifications about location services being off.
Interestingly, after a reboot, the issue returned. I also found that running netsh int ipv4 reset will allow dns to propagate until I move to another usb port.
I also had a person that doesn't disconnect her docking station report that after I changed the service dependency, the problem came back. Ultimately I disconnected the wired network connection from the dock and she's on wireless now which has not been an issue.