How to Restart Windows Update Service: Quick Fix for Stuck Updates

Stuck updates are the worst. I’ve seen systems hang for days waiting on Windows Update to finish what it started.

Restarting the service usually kicks it back into gear. The fix takes under 2 minutes and doesn’t require any special tools—just admin access and a command prompt. No registry edits, no third-party software.

You’ll clear the queue, reset the state, and force Windows to check for updates again. Works on Windows 10 and 11, and I’ve used it on dozens of machines without a single failure.

Handles most stuck update scenarios, including the infamous spinning wheel of doom. Let’s get it running again.

What Youll Need

Instructions

These are the exact steps I use to get this service back on track in under two minutes.

Press Windows + X and select Terminal (Admin) or Command Prompt (Admin) from the menu. If you see a UAC prompt, click Yes to grant administrative privileges. Without admin rights, the commands won’t execute properly.

Verify you’re in the right place by checking the title bar—it should read Administrator: Command Prompt. If it doesn’t, close the window and try again. This step is non-negotiable for the next commands to work.

Type the following command and press Enter:

net stop wuauserv

Wait for the confirmation message: “The Windows Update service was stopped successfully.” If you get an error, double-check the command for typos. This ensures the service is fully halted before restarting it.

Now, type the following command and press Enter:

net start wuauserv

You should see “The Windows Update service was started successfully.” If the service fails to start, proceed to the next step—sometimes a quick reset of its dependencies fixes the issue.

If the service still won’t restart, run these commands one at a time, pressing Enter after each:

net stop bits

net stop cryptsvc

Then, run:

net start bits

net start cryptsvc

These commands reset the Background Intelligent Transfer Service and Cryptographic Services, which Windows Update relies on. After running them, try restarting the update service again with net start wuauserv.

This almost always resolves stuck or frozen update processes.

Open Services.msc by pressing Windows + R, typing services.msc, and hitting Enter. Scroll down to Windows Update in the list. The Status column should read Running, and the Startup Type should be Manual (Trigger Start) or Automatic.

If it’s not running, right-click it, select Start, and confirm it begins without errors. You’re done—the service is now active and updates should resume normally.

Tips and Common Mistakes

These quick adjustments will save you time and prevent common hiccups when restarting Windows Update.

Admin Rights Are Mandatory: In Step 1, don’t skip verifying the Command Prompt title reads “Administrator.” Without elevated privileges, the net stop/start commands will fail with access denied errors. I learned this the hard way when troubleshooting my first stuck update—always check the title bar.

Confirmation Messages Matter: In Step 2 and Step 3, wait for the exact success confirmation before proceeding. If you don’t see “The Windows Update service was stopped/started successfully,” you’re not ready for the next command. Rushing this leads to dependency errors.

Dependency Reset Order: For Step 4, the sequence of stopping/starting bits and cryptsvc is critical. Always run net stop commands first, then net start commands. Mixing the order can leave services in a broken state. This is the most common fix when wuauserv refuses to restart.

Verification Shortcut: Instead of scrolling through Services.msc in Step 5, you can run sc query wuauserv in Command Prompt to quickly check the service status. It’s faster and gives you the same information without navigating menus.

Frequently Asked Questions

Restarting the Windows Update service is a simple yet effective way to resolve stuck updates and keep your system running smoothly. With just a few steps in Command Prompt or Services, you can get back on track. 💡 Try checking for updates again after restarting the service to ensure everything is working properly!