Windows 11 win 11 upgrade no network

• DNS Client (Dnscache) and WinHTTP AutoProxy are disabled/blocked by a local policy or a leftover/third‑party network agent after the 24H2 upgrade. “Some settings are managed by your organization” + the DNS service showing as disabled strongly points to a policy/registry setting or a service Start value set to Disabled rather than a simple UI glitch. We’ll check service configs, reset the network stack, and look for policy keys or software that can force those settings.

• You’ll need an Administrator Command Prompt (right‑click Start → Terminal (Admin) or search cmd, Run as administrator).
• Back up the registry before making changes (if we get to editing it I’ll remind you).

• sc config dnscache start= auto
• sc config WinHttpAutoProxySvc start= auto
• sc config wlansvc start= auto
  Then try:
• net start dnscache
• net start WinHttpAutoProxySvc
• net start wlansvc

• reg query "HKLM\SYSTEM\CurrentControlSet\Services\Dnscache" /v Start
• reg add "HKLM\SYSTEM\CurrentControlSet\Services\Dnscache" /v Start /t REG_DWORD /d 2 /f
• reg add "HKLM\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc" /v Start /t REG_DWORD /d 2 /f
• reg add "HKLM\SYSTEM\CurrentControlSet\Services\wlansvc" /v Start /t REG_DWORD /d 2 /f
  Then reboot and check Services.msc and Event Viewer again.

• netsh winsock reset
• netsh int ip reset
• ipconfig /flushdns
  Reboot and test.

• gpresult /h "%USERPROFILE%\Desktop\gpresult.html"
  Open the gpresult.html from your desktop and check for any applied Computer Configuration policies. If gpresult says no policies, also run:
• reg query "HKLM\SOFTWARE\Policies\Microsoft" /s
• reg query "HKCU\SOFTWARE\Policies\Microsoft" /s
  Copy any keys that look like Network, Internet Settings, WinHTTP, or DNS entries. Don’t delete anything until I review it.

• VPN clients (Cisco AnyConnect, GlobalProtect, OpenVPN, NordVPN, etc.
• Security/antimalware with network filtering (ESET, Sophos, McAfee, SonicWall, Malwarebytes with web protection)
• Local management agents (SentinelOne, CrowdStrike, corporate MDM)
  If yes, uninstall or disable them temporarily and try the upgrade or start services again.

• Try the sc config / net start sequence above first — that fixes this in many cases.
• If that doesn’t work and you find policy keys under HKLM\SOFTWARE\Policies\Microsoft that reference network/dns, paste them and I’ll give exact safe delete commands.
• If you have VPN/AV installed, uninstall them, reboot, then retry the upgrade (do a clean boot: msconfig → Selective startup → disable non‑Microsoft services).

• I’ll walk you through an in‑place repair (Windows 11 ISO > Setup > Upgrade to repair) which preserves files/apps and fixes corrupted system service registrations. That is usually a last step but is reliable.

• Run Step 1 and Step 2 and paste the outputs + the exact Event Viewer text for the 7001 / WinHttpAutoProxy errors. Also tell me if you have any VPN/AV or network management agents installed. I’ll interpret the outputs and give the precise registry/repair commands.

cwdavi1 said:

I've searched the forum and couldn't find this.

I upgraded a win 10 pro with local account to win 11 24H2. Installation succeeded but no wifi shows under networking. I plugged in ethernet, the taskbar icon shows connected with internet access but apps report no connection. Latest event viewer shows DNS client service failed to start, event 7001. First event error shows winhttpautoproxy service failed to start because the dependency service group failed to start. Services.msc shows DNS client disabled, can't enable. I ran sfc and dism, no problems found. Followed one suggeston I found and attempted to set manual DNS server. Got message some of these settings are managed by your oganization, could not save changes.

This is my desktop,bought it new, no group polices have ever been set, never joined any domaine. I rolled back to win 10, everything ok. Ran the upgrade again, same problem. This is my 4th win 11 upgrade in 3 days, first 3 no problems.

I will greatly appreciate any help.

Click to expand...

• Step 0 — be safe: run these in an elevated (Admin) PowerShell or Command Prompt. If you want, paste outputs here before changing anything.
  • sc qc dnscache
  • sc query dnscache
  • sc qc WinHttpAutoProxySvc
  • sc query WinHttpAutoProxySvc
  • sc qc WcmSvc
  • sc query WcmSvc
• Step 1 — try to set and start services (quick, non‑destructive)
  • sc config dnscache start= auto
  • sc config WinHttpAutoProxySvc start= demand
  • sc config WcmSvc start= auto
  • net start dnscache
  • net start WcmSvc
  • net start WinHttpAutoProxySvc
    If those start/stop commands succeed, reboot and test.
• Step 2 — if WcmSvc or DNS client still will not start or the Start value is repeatedly disabled, apply the commonly used workaround: remove WinHttpAutoProxySvc from WcmSvc’s DependOnService so Connection Manager no longer requires WPAD. This is the registry edit the community has used successfully for the exact 24H2 regression you’re seeing.
  Safe edit steps (Admin PowerShell)
  1) BACKUP the key first:
  reg export "HKLM\SYSTEM\CurrentControlSet\Services\WcmSvc" "%USERPROFILE%\Desktop\WcmSvc-backup.reg"
  2) Run these PowerShell commands to remove the dependency (copy‑paste as a single block in Admin PowerShell):
  $k='HKLM:\SYSTEM\CurrentControlSet\Services\WcmSvc'
  $deps = (Get-ItemProperty -Path $k -Name DependOnService -ErrorAction SilentlyContinue).DependOnService
  if ($deps) {
  $new = $deps | Where-Object {$_ -ne 'WinHttpAutoProxySvc'}
  Set-ItemProperty -Path $k -Name DependOnService -Value $new
  "Removed WinHttpAutoProxySvc from DependOnService"
  } else { "No DependOnService found; nothing changed." }
  3) Then set starts and restart services:
  sc config WcmSvc start= auto
  sc config dnscache start= auto
  net start dnscache
  net start WcmSvc
  4) Reset network stack and reboot:
  netsh winsock reset
  netsh int ip reset
  ipconfig /flushdns
  Restart‑Computer
• Step 3 — check for managed/policy keys and 3rd‑party network agents
  • Run gpresult /h "%USERPROFILE%\Desktop\gpresult.html" and open it (check Computer Configuration) — if it shows policies, paste the parts here.
  • Also check these registry paths for policies:
  • reg query "HKLM\SOFTWARE\Policies\Microsoft" /s
  • reg query "HKCU\SOFTWARE\Policies\Microsoft" /s
  • Temporarily uninstall/disable VPN clients, enterprise AV or network filtering drivers (they commonly cause “managed” settings or interfere with WinHTTP/WPAD).
• If you’re uncomfortable editing the registry
  • The alternative is to roll back to 23H2 (you already confirmed rollback works) or wait for Microsoft patching; many users simply rolled back until an official fix was available. Community/analysis posts show Microsoft acknowledged multiple connectivity regressions in 24H2 related to DHCP/WPAD and offered mitigations while working fixes; rollback is the safest short‑term option if you don’t want registry edits.

• Tell me the output of the sc / query commands above, or whether you want me to walk you through the registry workaround step‑by‑step. If you choose the registry route, I’ll stay with you through each command and how to restore the backup if anything looks wrong.

• From an elevated (Admin) Command Prompt run and paste outputs:
  • sc qc dnscache && sc query dnscache
  • sc qc WinHttpAutoProxySvc && sc query WinHttpAutoProxySvc
  • sc qc WcmSvc && sc query WcmSvc
  • sc qc wlansvc && sc query wlansvc
• Try (one at a time) and report any error text:
  • sc config dnscache start= auto
  • sc config WinHttpAutoProxySvc start= demand
  • sc config WcmSvc start= auto
  • net start dnscache
  • net start WcmSvc
  • net start WinHttpAutoProxySvc
• If you prefer to grab files instead: run gpresult /h "%USERPROFILE%\Desktop\gpresult.html" and attach that gpresult.html, and also export this registry key for review:
  • reg export "HKLM\SYSTEM\CurrentControlSet\Services\WcmSvc" "%USERPROFILE%\Desktop\WcmSvc.reg"

• The behavior you described matches a known 24H2 regression (WPAD / WinHttpAutoProxySvc dependency causing WcmSvc/DNS/WLAN problems). The detailed steps I posted earlier will help diagnose and, if necessary, remove WinHttpAutoProxySvc from WcmSvc’s dependency list as a safe workaround.
• Back up the registry before any edits. If you’d rather not edit the registry, rolling back to 23H2 is a safe short‑term option (you already saw rollback works).

• Paste the command outputs here or attach gpresult.html and the WcmSvc export. Say whether you want the step‑by‑step registry walkthrough or prefer I guide you through a rollback/repair install. I’ll respond with exact commands and what to expect.

• Note Windows build (Settings → System → About) and the exact network adapter model (Device Manager → Network adapters → right‑click → Properties → Details → Hardware Ids). If you want, paste those here and I’ll point to the correct OEM driver.

• Settings → Network & internet → Advanced network settings → Network reset → Reset now.
• Reboot and test.

• netsh int ip reset
• netsh winsock reset
• ipconfig /release
• ipconfig /renew
• ipconfig /flushdns
  Reboot and test.

• sc query Dnscache
• sc query Dhcp
• sc query Wlansvc
  If any are stopped, start them:
• sc config Dnscache start=auto & sc start Dnscache
• sc config Dhcp start=auto & sc start Dhcp
• sc config Wlansvc start=auto & sc start Wlansvc

• Device Manager → Network adapters → right‑click adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.”
• Also check USB Root Hubs / Bluetooth if using a BT dongle.

• Download the latest LAN/Wi‑Fi driver package from your PC/motherboard maker (don’t rely only on Device Manager).
• Device Manager → Network adapters → right‑click → Uninstall device. If prompted and you have OEM driver ready, you may choose “Delete the driver software” and then Reboot.
• After reboot install the OEM driver package and retest.

• Temporarily disable/uninstall VPN clients, third‑party firewalls, antivirus network shields, and any “network optimizer” utilities. Reboot and test.
• If removing those fixes it, re-install the vendor’s Windows 11 compatible version.

• DISM /Online /Cleanup-Image /RestoreHealth
• sfc /scannow
  Reboot and test.

• Event Viewer → Windows Logs → System: look for Dhcp, DNS Client, Netwtw (Intel), or NDIS warnings/errors around the failure times.
• Generate a powercfg/energy or netsh trace if needed:
  • powercfg /energy /duration 60 (creates a report in C:\Windows\system32\energy-report.html)
  • netsh trace start capture=yes tracefile=c:\temp\nettrace.etl (reproduce issue, then netsh trace stop)

• Try an in‑place repair (keeps apps & files): download and run the Media Creation Tool (Windows 11) and choose “Upgrade this PC now” → choose Keep personal files and apps. This refreshes system files and services that might be corrupted by an upgrade.
• Only if repair fails: consider clean install (after backing up).

• If everything works fine in Windows 10 on same hardware, focus on Windows 11 driver packages and any vendor tools that hook the network stack (VPN/cloaking).
• For Intel/Qualcomm/Atheros adapters, firmware/driver bundles from the OEM laptop page (Surface/HP/Dell/Lenovo) are often more stable than generic drivers on intel.com.
• If your PC uses Modern Standby, some adapter drivers need special WDF versions; OEM driver is especially important.

• Check for the latest OEM driver for you if you paste the PC/motherboard model and the adapter hardware id.
• Walk you through the command steps live and interpret any Event Viewer lines you find. Which would you like?

• Your symptoms match a known Windows 11 24H2 regression where WinHTTP Auto‑Proxy / WPAD and related service dependencies can stop WcmSvc/DNS/WLAN from starting, produce Event ID 7001, and show “some settings are managed by your organization.” Many users fixed it with a registry/workaround or (safer) rolled back until a patch.

• Keep what you have; Microsoft/partners often release fixes in a later feature update or cumulative patch. This is the least risky option.

• Create a fresh Windows 11 ISO from Microsoft (don’t reuse the old Rufus stick).
• On your working Win10 system: uninstall VPN/third‑party network filtering, temporarily disable AV, perform a clean boot, run chkdsk + sfc, and download the chipset + NIC/Wi‑Fi drivers for your board (from OEM or component vendor) onto a USB before attempting upgrade.
• Run the in‑place upgrade (Setup.exe from mounted ISO) with “keep apps and files” and monitor setuperr/logs if it fails. If it fails again, gather the setuperr/setupact logs and I’ll parse them with you.

• The community workaround that directly addresses the service dependency is to remove WinHttpAutoProxySvc from WcmSvc’s DependOnService and then restore service start types and restart the network stack. That has resolved the exact Event 7001 / DNS disabled case for many users, but I only recommend it if you’re comfortable with a registry backup and a restore plan.

• Tell me which option you prefer. If you want to retry the upgrade now (option 2) I’ll give an exact, ordered checklist and the commands to run (including safe registry backup and the DependOnService edit) and I’ll stay with you through the outputs. If you prefer to wait for 25H2, I can note what to collect later so a retry is painless (driver list, gpresult, setuperr logs).

• If Windows Update doesn’t offer 25H2 yet, Microsoft may be blocking your device or waiting for OEM driver fixes — that’s good. Wait until Windows Update shows the optional Feature update or Release Health shows no block for your model.

• Full image/backups (system image + file backup + note BitLocker keys).
• Download the latest OEM chipset + NIC/Wi‑Fi drivers for your exact motherboard/PC model (install them on Win10 before the upgrade). OEM driver updates are frequently the difference between success and failure.
• Uninstall/disable VPN, network‑filtering AV, and other network hooks before upgrade.
• Make a restore point and ensure you can roll back (or have the Win10 recovery media ready).
• Do the upgrade from a fresh Microsoft ISO (mounted Setup.exe) rather than an old Rufus stick if you had trouble before.

• The community workaround that fixed many 24H2 cases is to remove WinHttpAutoProxySvc from WcmSvc’s DependOnService and restore service start types; that works for affected machines but is an advanced registry fix and should be used only after backing up the registry. If you want, I can give the exact safe steps and a rollback command set. (I can also help check your device for a safeguard hold or driver availability first.

• If you rely on legacy EVR/DirectShow players, scripted WUSA installs from network shares, or SMBv1 workflows — Microsoft explicitly listed those classes of scenarios as still having known issues around the 25H2 rollout. If any of those describe you, I’d delay until your hardware/drivers and app workflows are confirmed compatible.

• Tell me your PC/motherboard model or paste the Network Adapter hardware ID from Device Manager (right‑click → Details → Hardware Ids). I’ll:
  • Check whether OEM Windows 11 drivers exist for your NIC.
  • Check whether Microsoft has a safeguard hold or known issue that would affect your model.
  • If you want to proceed, I’ll give a short, ordered checklist you can run just before upgrading and the exact commands for the registry/workaround in case the DNS/WcmSvc problem appears.