Enter Search Query:

Netsh int ip reset says access denied

Resetting the TCP/IP stack can be a useful way to clear any issues that might be preventing your computer from accessing the Internet or network. In Windows, there are lots of things that could screw up a systems TCP/IP stack and lead to connectivity issues. This is because Microsoft Windows stores most network information including the TCP/IP stack details in the registry and there are lots of ways for third party applications to modify this information.

Luckily Microsoft also implemented a way to reset the TCP/IP stack back to defaults which can clear up a variety of issues. The command to clear and reset the TCP/IP stack (on Windows XP, 7, 8 and 10) is:

netsh int ip reset c:\resetlog.txt

The command must be run in an elevated command prompt windows (WIN+X) and it can be destructive in terms of IPv4 info set on an adapter, so…like don’t run it remotely on a server with a static IP.

But I digress. The issue I’m really getting to is related to Homegroup membership and the Windows 10 upgrade. I found that if you’re upgrading from Windows 7 to Windows 10 and the original system you’re upgrading was joined to a homegroup, then the upgraded system might have issues with the TCP/IP stack (I.e. obtaining an IP address via DHCP).

[the problem]

I spent hours troubleshooting this on several freshly upgraded systems running Windows 10 that couldn’t connect to the network because they couldn’t obtain an IP from the DHCP server. All machines exhibited the same issue and all machines were previously joined to a homegroup (not a domain). Here are the symptoms:

  1. The system is upgraded from Windows 7 to Windows 10 build 1511 and works as expected but cannot obtain an IP address via Ethernet or Wi-Fi.
  2. The system works normally if a static IP is assigned.
  3. Resetting the TCP/IP stack results in the following information:
    netsh int ipv4 reset
    Resetting interface, OK!
    Resetting Unicast Address, OK!
    Resetting Neighbor, OK!
    Resetting Path, OK!
    Resetting , failed.
    Access is denied.Resetting , OK!
    Restart the computer to complete this action

[the solution]

In essence having had the systems joined to a homegroup somehow messed up the TCP/IP stack in windows 10 after the upgrade to the point that the system cannot obtain an IP address from DHCP. Here’s how to fix the issue:

  1. Open Regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi and expand that folder.
  3. Expand the subfolder named {eb004a00-9b1a-11d4-9123-0050047759bc} and right-click the subfolder named 26. Select Permissions… and ensure that for Everyone the Full Control box is checked.
  4. change_network_key_permission_registry_editor
  5. Press WIN+X to open a command prompt with elevated permissions. Type netsh int ip reset and hit enter. Now you should see the following results:
    Resetting , OK!Restart the computer to complete this action
  6. Reboot the system.

That’s it.

November 28, 2016

Related Posts

10 comments found

Comments for: Netsh int ip reset says access denied

  1. CB

    Thanks for this post. Do you know where I need to change permissions to get this command to work?:

    netsh Int ipv6 reset reset.log

    I have made your change in the folder 26 but I still get the access denied error. I am trying to fix a problem of all browsers crashing in W10.

  2. Johnny Lai

    Hi David,
    I have tried to set permission on subfolder 26, but everytime i restart my pc it removes the tick in ‘full control’. Do you know why this happens?
    Btw. How do you know it is the subfolder named 26 that should have full control?
    Johnny Lai

    1. Wyatt

      Having the same problem. Very frustrating. The solution works, but I must go through the entire process each time.

      1. SW

        I have one user who has had the folder reset permissions again too. Very odd.

  3. Not require

    iT works. thanx

  4. RJB

    I have multiple instances of {eb004a00-9b1a-11d4-9123-0050047759bc}, none of which have the same entries, but several have a “26” in them.

    1. lar

      try removing the shades before editing your registry.
      ok, i also had to look twice…

  5. Thank yoj


Leave a Reply

Your email address will not be published. Required fields are marked *