Windows

TCP/IP Reset in Windows: Complete Network Recovery Guide

This guide details how to perform a TCP/IP reset in Windows using Command Prompt and PowerShell. You'll learn to restore network connections when errors occur.

Updated at February 16, 2026
5-10 min
Easy
FixPedia Team
Применимо к:Windows 10Windows 11Windows Server 2016Windows Server 2019Windows Server 2022

Introduction / Why This Is Needed

The TCP/IP stack is a set of protocols responsible for network connections in Windows. Over time, its configuration can become corrupted due to viruses, faulty software, or manual changes. The result: no internet, "Failed to obtain IP address" errors, slow or unstable connections.

Resetting TCP/IP restores the stack's default settings without affecting your personal data. This is an effective and safe alternative to reinstalling the system or resetting all network settings. After completing this guide, your network connection should start working again.

Requirements / Preparation

Before you begin, ensure that:

  • You have Windows 10, Windows 11, or Windows Server 2016/2019/2022.
  • You have administrator privileges (mandatory).
  • It is recommended to create a system restore point in case of unforeseen issues.
  • An internet connection is not required for the reset, but driver updates may be needed after the reboot.

Step-by-Step Instructions

Step 1: Opening Command Prompt or PowerShell as Administrator

Press the Win + X key combination and in the menu that appears, select one of the options:

  • Windows PowerShell (Admin) (recommended for Windows 10/11)
  • Command Prompt (Admin) (if PowerShell is unavailable)

If a User Account Control (UAC) prompt appears, click Yes.

⚠️ Important: Do not run the regular (non-administrator) version. Without administrator rights, the command will not work.

Step 2: Executing the TCP/IP Reset Command

In the opened window, type the following command and press Enter:

netsh int ip reset resetlog.txt

What this command does:

  • netsh — network management utility.
  • int ip reset — resets TCP/IP parameters.
  • resetlog.txt — the name of the file where the change log will be written (created in the folder from which the command is run, usually C:\Windows\System32).

If you want to save the log elsewhere, specify the full path, for example:

netsh int ip reset C:\Users\YourName\Desktop\tcp_reset_log.txt

After successful execution, you will see the message: "TCP/IP reset completed."

Step 3: (Optional) Resetting Winsock

If network problems persist after the TCP/IP reset (e.g., programs cannot connect to the internet), perform an additional Winsock reset—the component that manages network connections for applications.

In the same Command Prompt or PowerShell window, type:

netsh winsock reset

You will see confirmation: "Winsock reset completed."

💡 Tip: Perform this step if the network works partially (e.g., ping works but the browser doesn't load pages) or after removing malware.

Step 4: Restarting the Computer

This is a mandatory step. Changes will only take effect after a system restart.

Click Start → Power button → Restart or type in the command line:

shutdown /r /t 0

Step 5: Verifying the Network Connection

After restarting, ensure the network is working:

  1. Open Command Prompt (without administrator rights) and run:
    ipconfig /all
    

    Your network adapter (Wi-Fi or Ethernet) should have an IPv4 Address (e.g., 192.168.1.10) and a Default Gateway.
  2. Check connectivity to the gateway (replace 192.168.1.1 with your gateway from the previous command):
    ping 192.168.1.1
    

    Replies should be received (0% packet loss).
  3. Check internet access:
    ping 8.8.8.8
    

    If ping succeeds, open your browser and visit any website.

Verifying the Result

A successful reset means:

  • ipconfig /all displays a correct IP address, subnet mask, and gateway.
  • Ping to the gateway and external addresses (8.8.8.8) works.
  • Websites load in the browser.
  • Network applications (messengers, games) connect without errors.

If something is not working, proceed to the next section.

Potential Issues

Error "The system cannot find the file specified" or "Administrator privileges required"

  • Cause: Command Prompt/Shell was launched without administrator rights.
  • Solution: Close the window, reopen it via Win + X and select "Admin".

No IP address after reset (169.254.x.x)

  • Cause: The adapter is not receiving an address from the DHCP server.
  • Solution:
    1. Run ipconfig /release and ipconfig /renew.
    2. Restart your router/modem.
    3. Update the network adapter driver in Device Manager.

Error "The parameter is incorrect" when running netsh

  • Cause: Corruption of system files.
  • Solution: Run a system file check:
    sfc /scannow
    
    After completion, repeat the reset.

Programs missing from "Allow apps to use your network" list after Winsock reset

  • Cause: Winsock reset cleared all permissions.
  • Solution: Open Control Panel → Windows Defender Firewall → Advanced Settings → Inbound Rules and re-allow the necessary programs.

Network still not working after all steps

  • Cause: Hardware issue, drivers, or router settings.
  • Solution:
    1. Update the network adapter driver from the manufacturer's website.
    2. Perform a full network reset in Windows: Settings → Network & Internet → Network reset (this will remove and reconfigure all adapters).
    3. Check the cable or router.

⚠️ Important: Resetting TCP/IP does not delete your personal files, Wi-Fi passwords, or browser settings. It only affects low-level network protocols.

F.A.Q.

How does TCP/IP reset differ from network reset in Windows settings?
Is it necessary to restart the computer after TCP/IP reset?
Can TCP/IP be reset without administrator privileges?
What to do if the network doesn't work after reset?

Hints

Opening Command Prompt or PowerShell as Administrator
Executing the TCP/IP Reset Command
(Optional) Winsock Reset
Computer Restart
Checking Network Connection
FixPedia

Free encyclopedia for fixing errors. Step-by-step guides for Windows, Linux, macOS and more.

© 2026 FixPedia. All materials are available for free.

Made with for the community