After installing Windows 11 version 24H2, some PCs start showing frustrating network problems: Wi-Fi says it is connected, but websites do not open, the connection drops after reboot, or a VPN connects without passing traffic. As of March 9, 2026, the newest 24H2 security update listed by Microsoft is KB5077181 (OS Build 26100.7840), and the newest 24H2 optional preview is KB5077241 (OS Build 26100.7922). Microsoft also says Windows 11 version 25H2 is available for eligible 24H2 devices and is delivered through the same servicing branch.
The important thing to know is this: there is no single official Microsoft bug entry that explains every “Wi-Fi connected, no Internet” case on 24H2. Microsoft’s current 24H2 known-issues page highlights a WUSA shared-folder issue in enterprise-style update installs, not a universal home-user Wi-Fi outage. Microsoft also had a separate NDI/streaming performance issue after the August 2025 update, and that issue was marked resolved on September 9, 2025. In other words, 24H2 networking trouble is usually a mix of driver issues, DNS problems, corrupted network settings, or VPN/filter conflicts rather than one single global defect.
Before you start changing settings, check which build you are actually running. Open Settings > System > About and look at OS Build. If you are behind on updates, install the latest 24H2 update first. If your device is eligible and you prefer to move forward instead of troubleshooting 24H2 further, Microsoft recommends moving to 25H2 when it is offered.
- 1 Step 1: Install the latest Windows updates first
- 2 Step 2: Run Network Reset
- 3 Step 3: Set a manual DNS server
- 4 Step 4: Reset Winsock, TCP/IP, and DNS cache
- 5 Step 5: Update the adapter driver — or roll it back
- 6 Step 6: If the problem appears only with your VPN, test without it
- 7 Step 7: Generate a Wireless Network Report
- 8 Step 8: Repair Windows without wiping your apps and files
- 9 When should you move to 25H2?
- 10 Final advice
Step 1: Install the latest Windows updates first
This should always be your first move. If your PC is still on an older 24H2 build, you may be troubleshooting a problem that has already been improved in later cumulative updates. Open Settings > Windows Update > Check for updates, install everything available, and restart. If you see an optional preview update and you are comfortable testing a newer build, that can also be worth trying after making a backup or restore point.
Step 2: Run Network Reset
Microsoft’s own Windows 11 Wi-Fi troubleshooting guidance still recommends Network reset as one of the main recovery steps. Go to Settings > Network & internet > Advanced network settings > Network reset, choose Reset now, and restart the PC. Microsoft notes that after a network reset, you may need to reinstall or reconfigure networking software such as VPN clients or virtual switches, and Windows may switch your saved network profile back to Public.
If your internet comes back after this step, the problem was probably in the Windows networking stack, adapter bindings, or old network configuration left behind after the 24H2 upgrade. This is one of the safest first fixes because it does not require editing the registry or uninstalling Windows updates.
Step 3: Set a manual DNS server
If Wi-Fi shows as connected but browsers still say there is no internet, DNS may be the real problem. Windows allows you to manually specify DNS in the adapter settings. Go to the properties page for your active Wi-Fi or Ethernet connection, open the IP settings editor, switch to Manual, turn on IPv4, and enter a Preferred DNS and Alternate DNS value. Windows also supports DNS over HTTPS options in the same area.
A practical test is to use a known public resolver for a few minutes and see whether browsing becomes stable. If web pages start loading immediately after changing DNS, the connection itself may be fine and only name resolution was failing. That is especially common when an update, VPN client, or router change leaves the adapter using an unstable DNS path.
Step 4: Reset Winsock, TCP/IP, and DNS cache
Microsoft’s Windows network troubleshooting guidance also includes the classic admin-command sequence for rebuilding the network stack. Open Command Prompt as Administrator and run these commands one by one:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Then restart the PC. Microsoft lists these commands as standard troubleshooting steps for Windows networking problems, including Wi-Fi and Ethernet failures.
This step is especially useful when the problem returns after reboot, when DHCP seems broken, or when browsers and apps disagree about whether the internet is available. It is also a good next step if Network Reset helped only temporarily.
Step 5: Update the adapter driver — or roll it back
Driver problems are still one of the biggest reasons a PC loses stable networking after a feature update. Open Device Manager, expand Network adapters, right-click your Wi-Fi adapter, and try Update driver. If the trouble began right after a Windows or driver update, Microsoft’s Device Manager guidance specifically says that reinstalling the previous driver often resolves it, and it provides the Roll Back Driver option under the adapter’s Driver tab.
In real-world troubleshooting, the best result is often not “the newest driver,” but the most stable driver for your exact laptop model. That means if Windows Update installed a newer wireless driver and the problem started immediately afterward, the better fix may be to roll back or install the latest OEM package from your PC maker instead of staying on the Windows Update driver branch. Microsoft’s support guidance does not name specific adapter models here, but it clearly supports the update-or-rollback workflow when a recent driver change is suspected.
Step 6: If the problem appears only with your VPN, test without it
If normal browsing works but everything fails only when your VPN is connected, treat the VPN as part of the problem until proven otherwise. Microsoft notes that network reset may require VPN software to be reinstalled or set up again, which is a strong clue that VPN clients can be part of the failure path when networking breaks after a major Windows change. Temporarily disconnect the VPN, test plain internet access, then update or reinstall the VPN client if needed.
This is especially important on work laptops, because many VPN tools install network filters, virtual adapters, or custom DNS behavior. If your company manages the PC, do not remove enterprise security software on your own—report the exact behavior to IT instead. A quick test with the VPN off is usually enough to tell whether the problem is in Windows networking generally or in the VPN layer specifically.
Step 7: Generate a Wireless Network Report
Windows includes a built-in diagnostic report that many people forget exists. Open Command Prompt as Administrator and run:
netsh wlan show wlanreport
Windows will create an HTML report showing the last three days of Wi-Fi events, including disconnect reasons, adapter details, driver version, driver date, and session failures. Microsoft says this report is one of the most useful built-in tools for diagnosing Wi-Fi problems.
This report is especially helpful when the issue is intermittent. If your connection randomly drops every few minutes, or only fails after sleep or reboot, the report can show the exact time and type of disconnect. That makes it much easier to tell whether the real cause is the access point, the adapter driver, DHCP, profile corruption, or repeated authentication failures.
Step 8: Repair Windows without wiping your apps and files
If the problem survives resets, DNS changes, and driver work, you may be dealing with damaged Windows components from the upgrade itself. Microsoft now provides a built-in repair path under Settings > System > Recovery > Fix problems using Windows Update > Reinstall now. Microsoft says this option reinstalls the same version of Windows already on your PC, repairs system files and components, and preserves your apps, files, and settings.
If that option is missing on your PC, Microsoft also documents the classic in-place repair install using installation media: mount the Windows installation media, run setup.exe from within Windows, and choose to keep your files and apps. That method can refresh networking components as part of the repair process without forcing a clean install.
When should you move to 25H2?
Microsoft’s current release-health guidance says 25H2 is available and recommends moving to it to stay up to date. Microsoft also explains that 25H2 is delivered as an enablement package for eligible 24H2 devices and shares the same code base and servicing branch. That means moving from 24H2 to 25H2 is lighter than a full major-version replacement on those eligible systems.
That said, upgrading is not the first fix for every broken connection. If your PC lost internet right after 24H2 and you need it working today, repair the current install first. Once networking is stable and your device is fully backed up, then decide whether moving to 25H2 makes sense for your hardware and workflow.
Quick symptom guide
If your symptom is “Wi-Fi connected, no Internet,” start with Windows Update, then Network Reset, then a manual DNS test, and finally the Winsock/TCP-IP command sequence.
If your symptom is “it breaks after reboot” or “it worked until a recent update,” go straight to the adapter’s Driver tab and try Roll Back Driver if that option is available.
If your symptom is “only my VPN is broken,” test the connection without the VPN first, then reinstall or reconfigure the VPN client if ordinary internet access returns. Network Reset may require VPN software to be set up again.
If your symptom is “random drops every few minutes,” create a wireless network report and check the disconnect reasons, driver version, and session failures before changing more settings.
FAQ
Is this an official Microsoft 24H2 internet bug?
Not as one single universal bug. Microsoft’s current 24H2 known-issues page does not list a blanket “Wi-Fi connected, no internet” issue for all users. The documented items are more specific, such as the mitigated WUSA shared-folder problem, while the August 2025 NDI streaming issue was already resolved.
Should I uninstall the latest update?
That is usually not the first thing to try. Start with the lower-risk fixes first: install the newest cumulative update, run Network Reset, test DNS, reset Winsock/TCP-IP, and roll back the adapter driver if the issue clearly started with a driver change. If those fail, use the Windows repair reinstall path before considering bigger rollback decisions.
Can reinstalling the current version of Windows really fix network issues?
Yes. Microsoft says the Fix problems using Windows Update recovery option reinstalls the same version already on the PC, repairs system files and components, and keeps apps, files, and settings. That makes it one of the best “last safe steps” before a clean install.
Final advice
If Windows 11 24H2 broke your connection, do not assume the whole update is permanently bad. In many cases, the fix is more targeted: bring the PC fully up to date, reset the network stack, test DNS, roll back the adapter driver if needed, and generate a wireless report if the problem is intermittent. If the system itself seems damaged, use Microsoft’s built-in repair reinstall option. And if your device is eligible and stable enough afterward, moving to 25H2 may be the cleanest long-term path because Microsoft now recommends it for staying current.
✔️You might also find these helpful:
▶︎[Important] How to Extend Windows 10 Security Updates for Free Until October 2026
▶︎How to Fix “No Internet Access” on Windows: Causes and Solutions (Wi-Fi & Ethernet)
