Windows command guide

How to Reset WinHTTP Proxy Settings in Windows

Windows uses different networking layers for different services. Even if your browser works, system services such as Windows Update or background Microsoft components can still fail because WinHTTP is using a bad proxy configuration. Resetting the WinHTTP proxy removes that stale or incorrect setting and returns the system service layer to a direct connection unless a new proxy is defined later.

This guide is written around the specific symptom-command match for reset winhttp proxy settings, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.

Reviewed guide Updated 2026-04-21

Elevated Command Prompt

netsh winhttp reset proxy

Best place to run it

Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.

Fast repair workflow

Start from the exact symptom on this page: Windows Update or Microsoft sign-in services fail even though web browsing still works
Run the network repair line exactly as shown: netsh winhttp reset proxy.
This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
Disconnect and reconnect the adapter or reboot the PC if the reset changed saved network state.
Verify raw connectivity, name resolution, and IP assignment before moving to router or driver troubleshooting.

Copyable wrapper script

Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.

@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
netsh winhttp reset proxy
echo.
echo Review the output before closing this window.
pause

Verification commands after the repair

These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.

ipconfig /all
ping 1.1.1.1
nslookup example.com

What problem this command is trying to solve

This command targets system-level proxy misconfiguration. That can happen after VPN tools, enterprise proxy policies, old scripts, removed security tools, or manual network testing.

Windows Update or Microsoft sign-in services fail even though web browsing still works.
A proxy server was used before, but it is no longer available.
Network tools mention proxy errors or connection failures on background services.

How the command works

netsh winhttp reset proxy clears the WinHTTP proxy configuration. That does not necessarily change your browser proxy settings, but it resets the network path used by many Windows components and background service calls.

When it makes sense to run it

Use it when Windows services cannot connect and you suspect an old proxy is still applied. It is common after leaving a managed network, uninstalling VPN or filtering software, or testing corporate proxy settings on a home machine.

Before you run this command

Open an elevated Command Prompt or PowerShell window before running netsh winhttp reset proxy.
Confirm that the symptom really matches this guide, especially if you are seeing signs such as: windows update or microsoft sign-in services fail even though web browsing still works.
Check whether the failure is really system-wide and not just one website, one browser, or one Wi-Fi network.

What result to expect

After running netsh winhttp reset proxy, compare the result against the symptom that brought you here. The most useful checkpoint is whether windows update or microsoft sign-in services fail even though web browsing still works becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.

How to verify that it worked

The best verification step after netsh winhttp reset proxy is to repeat the action that previously triggered the problem. If a proxy server was used before, but it is no longer available still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.

Why administrator rights matter here

This command changes connectivity, DNS, IP, proxy, or adapter state. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.

Before you run it

If your environment really requires a proxy, clearing it can break that setup until the correct proxy is configured again.

When this is probably the wrong fix

This is not the right first fix when one website is down, the ISP has an outage, or only one app is blocked by a firewall rule. Use it when the Windows networking stack or saved network state looks damaged.

What to do if it does not help

If netsh winhttp reset proxy does not improve windows update or microsoft sign-in services fail even though web browsing still works, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about connectivity, DNS, IP, proxy, or adapter state.

Frequently asked questions

Should I use netsh winhttp reset proxy for this exact Windows symptom?

Use it when the behavior on your PC lines up with the repair target on this page: This command targets system-level proxy misconfiguration. That can happen after VPN tools, enterprise proxy policies, old scripts, removed security tools, or manual network testing.

What should I check right after netsh winhttp reset proxy?

Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether windows update or microsoft sign-in services fail even though web browsing still works becomes less frequent, changes form, or points you toward a more specific next step.