23H2 to 24H2 Feature Update causes no internet

Topic

New Reply

I was offered the 24H2 update earlier this week. I don’t want it yet but wanted to try it. Made a backup image then let it go. Didn’t take too long, about 20 minutes then restarted and I had no internet! I have never had a problem like this before. The internet always just works. I’m back on 23H2, have internet again. Searched for answers online, a week of searching, reading and trying things:

https://www.windowslatest.com/2024/10/27/windows-11-24h2-issues-break-internet-wi-fi-network-sharing-cause-more-bsods/

https://answers.microsoft.com/en-us/windows/forum/all/problem-in-network-windows-11-24h2/ac1e20e5-091a-45ab-a3c7-94ca7b31577d?page=16

but nothing works. I used Gibson Research’s InControl app to stop 24H2.

I would like to know what is causing this, of course, because eventually I’ll have to update but will this problem be solved by then?

2 users thanked author for this post.

WSskd, ClearThunder

Reply | Quote

Replies

I bought a new Win11/24H2 rig a week or so ago, and didn’t have any issues with internet until the last windows update on Tuesday.   I didn’t check MS to see if it was a widespread issue (yet), so I tried restarting the computer.  No internet.  So I did a cold-boot on my modem, and that seemed to fix the issue.  I figured it was an ISP problem, and let it go at that until I came upon this thread.

For me, this issue with internet connectivity happens during a restart or boot-up.  Every time I do either, there is no internet until I do a cold-boot on the DSL modem (hey, it’s all I have access to here in BFE), and then the internet is restored.  My guess is that the modem resets some kind of Gateway or  …… something that only an MIT graduate would understand.  Judging from what people are saying in the Microsoft forums TJN linked to, all the fixes seems to be draconian in nature, and not for the faint of heart or someone who is not tech savvy.

So …. until Redmond issues a fix, I just avoid the problem by keeping my computer on and connected to my UPS in case of a power outage.  Since my PC was shipped with 24H2, I keep my automatic windows update on.  The O/S is already ‘buggy,’ so following Susan’s Defcom advice is unwise at this time because one of those unplanned or out of band updates just might be a fix for this issue, and I’d prefer not to miss it.

"War is the remedy our enemies have chosen. And I say let us give them all they want" ----- William T. Sherman

1 user thanked author for this post.

T-J-N

Reply | Quote

Thanks for the reply.

I didn’t list the things I’d tried because I did them all. Reset modem, restarted, checked registry settings, changed dns settings. I even checked the ASUS site for new drivers but I have all of the new “important” ones from December 2024 installed already. I also sent a post in Feedback Hub for the very first time. There is nothing wrong on my end, 23H2 works fine. I need Microsoft to fix this. I am genuinely worried about the future of Windows.

 

Reply | Quote

When you had no internet, was there anything in the event logs?  Did a wired connection work? Home or Pro?  Have you done any customization on the 23H2?

Remember how badly XP sp2’s roll out was?  Every new major release we have issues.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Windows 11 Home, wired ethernet. Custom built tower PC. No problems at all for 2 years until 24H2. I didn’t think of checking the Event Logs. I have installed StartAllBack, that’s it, no VPN or Bitlocker. I have never had a problem with the internet before, XP, Vista, 7, 10, it always just works. I’m back on 23H2 now so the internet problem is over, it is only there on 24H2. I think it has something to do with tightening security in Windows that 24H2 does. Thank you for trying to help.

I did it 3 times. Upgrade, roll back, upgrade again with new info, roll back, upgrade again with a week of gathered intel and roll back. Maybe the event logs are still there?

Update, this is the only relevant error I could find:
Event ID: 10142
Source: Windows Remote Management
The WinRM service cannot migrate the listener with Address * and Transport HTTP. A listener that has the same Address and Transport configuration already exists.

Reply | Quote

I have seen this reported to fix some machines.

I honestly don’t understand the root cause and personally my spidey sense feels like it’s a vendor OEM issue or hardware issue that they haven’t identified yet.

“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.

Thank you! This completely fixed my issue. It’s the only solution I’ve found. The give away for me was that the connection was showing two active networks, and was unable to properly setup the DHCP connection on IPv4 only.

After making this registry edit and restarting the service everything is working properly. Total lifesaver”

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

T-J-N

Reply | Quote

That is the problem, none of those issues existed on 24H2 in my case. I have a clean basic system so there is nothing for me to do, like try uninstalling whatever. On the third upgrade cycle I checked everything and they were all set right, the same as they were on 23H2, and that is why I am stumped and worried. My main desire was to make noise about this issue, because it is major and the fixes don’t work for me. I am not going to let it get me down, I am going to enjoy Christmas and wait for this issue to get resolved.

Reply | Quote

I’ve seen it where you have to make these registry changes.  I would open a feedback ticket in the Windows feedback section.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote