Windows command guide

Reset Windows Update Services with net stop and net start

Windows Update depends on background services to download, verify, and install updates correctly. When those services get stuck, updates may stop progressing, fail repeatedly, or loop with the same download problem.

This guide is written around the specific symptom-command match for reset windows update services, 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

net stop wuauserv && net stop bits && net start bits && net start wuauserv

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: Updates stay stuck on checking, downloading, or installing
Run the primary repair line exactly as shown: net stop wuauserv && net stop bits && net start bits && net start wuauserv.
This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.

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...
net stop wuauserv && net stop bits && net start bits && net start wuauserv
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.

DISM /Online /Cleanup-Image /CheckHealth
sfc /verifyonly

What problem this command is trying to solve

This command targets hung or unstable Windows Update services, especially the Windows Update service and Background Intelligent Transfer Service.

Updates stay stuck on checking, downloading, or installing.
The same update fails repeatedly without a clear reason.
Download behavior looks frozen or inconsistent.

How the command works

The command stops the main update services and then starts them again. That can clear a stuck service state and give Windows Update a clean chance to resume normal activity.

When it makes sense to run it

Use it early in Windows Update troubleshooting when the problem looks service-related rather than caused by disk space, internet loss, or unsupported hardware.

Before you run this command

Open an elevated Command Prompt or PowerShell window before running net stop wuauserv && net stop bits && net start bits && net start wuauserv.
Confirm that the symptom really matches this guide, especially if you are seeing signs such as: updates stay stuck on checking, downloading, or installing.
Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.

What result to expect

After running net stop wuauserv && net stop bits && net start bits && net start wuauserv, compare the result against the symptom that brought you here. The most useful checkpoint is whether updates stay stuck on checking, downloading, or installing 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 net stop wuauserv && net stop bits && net start bits && net start wuauserv is to repeat the action that previously triggered the problem. If the same update fails repeatedly without a clear reason 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 system integrity and component corruption. 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

Run the command in an elevated console. If updates are already making progress, do not interrupt them just to experiment.

When this is probably the wrong fix

This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.

What to do if it does not help

If net stop wuauserv && net stop bits && net start bits && net start wuauserv does not improve updates stay stuck on checking, downloading, or installing, 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 system integrity and component corruption.

Frequently asked questions

Should I use net stop wuauserv && net stop bits && net start bits && net start wuauserv 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 hung or unstable Windows Update services, especially the Windows Update service and Background Intelligent Transfer Service.

What should I check right after net stop wuauserv && net stop bits && net start bits && net start wuauserv?

Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether updates stay stuck on checking, downloading, or installing becomes less frequent, changes form, or points you toward a more specific next step.