Fix: Service Cannot Accept Control Messages at This Time

You right-click a service in the Services console, choose Restart, watch the spinner for a few seconds, and then the dialog appears: “The service cannot accept control messages at this time.” I understand the sinking feeling — your first instinct is to reboot the server. I've watched IT pros do exactly that, only to see the same dialog 15 minutes later because the underlying issue was never resolved. Before you go down that road, know this: the message, officially Windows Error 1061, means the Windows Service Control Manager asked a service to do something while that service was still in START_PENDING or STOP_PENDING, so the service refused the request. Waiting about 60 seconds and retrying resolves many cases.

In this guide, I'll walk you through every reliable fix I've used over years of Windows administration — graphical, command-line, and PowerShell. I tested every method here on Windows 10 and Windows 11, and the same steps work on Windows Server. I'll also cover the scenarios where this error bites hardest: IIS App Pools, Windows Update, and third-party sync services. Most fixes don't require a reboot, but I'll show you a safe escalation path for services that simply refuse to recover.

---

What Does "The Service Cannot Accept Control Messages at This Time" Mean? (Error 1061)

Let's decode the actual error before we start clicking things.

The Service State Machine Explained in Plain English

Every Windows service has a lifecycle: a starting phase (START_PENDING), a running phase (RUNNING), a stopping phase (STOP_PENDING), and a fully stopped state (STOPPED). The Windows Service Control Manager acts like a dispatcher, sending start, stop, pause, and continue commands through a Service Control Dispatcher. Each service can only process these commands when it's in the right state.

If a control request arrives while the service is still transitioning between states, Windows returns Win32 error 1061 (ERROR_SERVICE_CANNOT_ACCEPT_CTRL), which your screen displays as "The service cannot accept control messages at this time."

Here's the analogy I use with clients when they're troubleshooting an IIS App Pool: a driver changing lanes cannot safely process a new turn signal mid-maneuver. The request isn't wrong — the timing is. Wait for the lane change to complete, and the same request goes through without issue.

Why Do Services Get Stuck in Start Pending or Stop Pending?

In my experience, a service rarely gets stuck for no reason. The usual culprits are:

• Hung dependencies — a service waits on another service that's itself stuck mid-transition.
• Disabled helper services — third-party cleanup tools, or even aggressive "optimizers," disable things like Credential Manager, breaking dependent applications.
• Windows Update components mid-operation — update services often lock themselves while installing or finalizing patches, especially right after a reboot.
• Slow application startup logic — a service whose executable performs lengthy initialization in its main thread keeps the state at START_PENDING far longer than Windows's internal timeout.

The important takeaway: the service itself usually isn't corrupt. The Service Control Manager simply refuses new commands until the pending operation completes or times out. Identifying why the service entered that pending state is what determines which fix below you need — and honestly, the quick-fix roadmap in the next section resolves a surprising percentage of cases.

---

Try This First: A 30-Second Quick Fix for a Start-Pending Service

I never start a troubleshooting session with nuclear options. Here's the sequence I walk every support call through, and it's resolved more "critical" incidents than I can count.

The Quick-Fix Roadmap

1. Wait a full 60 seconds — not 10, not 15. Set a mental timer, sip your coffee, then retry. Many pending transitions simply need time to complete.
2. Press Win + R, type services.msc, and press Enter. Locate the service that generated the error, right-click it, and choose Restart.
3. If Restart fails, check the service's state. If it still shows Start Pending or Stop Pending, note the service name and skip directly to Fix 2, where I'll show you how to identify the stuck process ID and terminate it cleanly.
4. Only if both of those fail, reboot the machine — then retry the service operation once Windows has fully settled (give it two to three minutes after sign-in; services need time to finish their boot sequence, and I'll explain why in the Windows Update section).

This 60-second rule is a decision point: wait once, retry once, then escalate. Spending 45 minutes clicking a stubborn Start button won't accomplish anything.

---

Fix 1: Restart the Stalled Service from services.msc

Step-by-Step: Restart a Service and Verify Its Startup Settings

When the quick-fix roadmap doesn't do the job, open the Services console and check the service's configuration. I recommend doing this even if you plan to use command-line tools later, because you'll see the service's real name and dependencies at a glance.

1. Press Win + R, type services.msc, and press Enter.
2. Find the service that displayed the error. Double-click it to open its Properties window.
3. On the General tab, confirm the Startup type is set correctly. Many third-party apps expect Automatic; if it's set to Manual or Disabled, change it and click Apply.
4. Click Start (or Restart if the service is already running). If the service is stuck, try clicking Stop first. If the Stop button is grayed out, don't close this window — switch to the Log On tab, verify the service account is correct, and then use the command-line method in Fix 2. That grayed-out button tells you the SCM believes the service is transitioning, and the GUI won't force its hand.
5. On the Log On tab, confirm the service account's password hasn't expired — this is a surprisingly common cause of services that fail to fully restart after a password rotation.

One Windows quirk worth knowing: close every Properties window before closing the Services console, or the console itself may refuse to close. It's a silly cosmetic bug that's been around for over a decade, and it catches everyone at least once.

Once the service shows Running, test your original operation again. If it still throws Error 1061, you're dealing with a stuck process, and that's what Fix 2 handles.

---

Fix 2: Stop an Unresponsive Service with sc stop, net stop, or taskkill

GUI tools have limits. When a service is truly stuck in a pending state, the command line gives you far more control — and also reveals exactly what's happening.

Find the Stuck Service's Exact State with sc query

Open Command Prompt or PowerShell as Administrator (right-click and choose "Run as administrator"). First, check the service state:

sc query <service-name>

The STATE line tells you everything. If it reads 2 START_PENDING or 3 STOP_PENDING, you've confirmed the problem. If it reads 4 RUNNING, you're working with a different issue entirely — the service accepts commands but may be crashing repeatedly.

To get the process ID (PID) of a hung service, use:

sc queryex <service-name>

Look for the PID line. That number is your key to ending the process manually.

Stop, Kill, and Restart the Hung Service

Work through these steps in order, and don't skip ahead — force-killing should always be the last resort.

1. Try a graceful stop with either sc stop <service-name> or net stop <service-name>.

2. Wait 30–60 seconds. If the service is still in STOP_PENDING, run sc queryex <service-name>, note the PID, and force-kill the process:

   taskkill /F /PID <PID>
   

3. Restart the service once the process has ended:

   sc start <service-name>
   

   or

   net start <service-name>
   

A warning I give to every junior admin I've mentored: do not force-kill critical system services like RPC (RpcSs), Plug and Play (PlugPlay), or Security Accounts Manager (SamSs) unless you are fully prepared for system instability. Killing those can leave Windows in a state where only a reboot saves you. For ordinary application services, though, taskkill is safe.

PowerShell Alternative: Restart-Service -Force

If you're a PowerShell person, the one-liner you want is:

Restart-Service -Name <ServiceName> -Force

The -Force switch tells PowerShell to restart the service even if it has dependent services or appears unresponsive.

But here's a caveat from experience: Restart-Service -Force can still produce Error 1061 when the service is mid-transition. When that happens, fall back to the workflow above — grab the PID with sc queryex, kill it with taskkill, then start the service with sc start. PowerShell is excellent, but it's not magic; it talks to the same Service Control Manager that's refusing the command.

---

Fix 3: Restart Windows Update and Related Services That Trigger Error 1061

Which Windows Services Need a Restart and in What Order

Windows Update is the most common source of Error 1061 I encounter in the field — particularly after an update fails mid-installation or a laptop sleeps during a patch download. The update stack runs several interdependent services, and stopping them in the wrong order creates exactly this error.

The usual suspects are:

• BITS (Background Intelligent Transfer Service) — service name: bits
• Windows Update — service name: wuauserv
• Cryptographic Services — service name: CryptSvc
• Windows Installer — service name: msiserver
• Windows Modules Installer — service name: TrustedInstaller

Stop dependent services first, then the main Windows Update service, and reverse the order when starting them. Here's the copy-paste command sequence I use:

net stop bits
net stop wuauserv
net stop CryptSvc
net stop msiserver
net stop TrustedInstaller

Then, after a few seconds, start them in reverse:

net start TrustedInstaller
net start msiserver
net start CryptSvc
net start wuauserv
net start bits

Run sc query after each stop command so you can identify exactly which service refuses to transition. That's your stuck service, and it needs the taskkill approach from Fix 2.

If Windows Update Services Still Won't Stop: Next Steps

If wuauserv or bits returns Error 1061 and refuses to stop gracefully, escalate to the PID hunt: run sc queryex wuauserv, then taskkill /F /PID <PID>. These services run inside shared svchost.exe processes, so you must target the exact PID — killing all svchost processes is a recipe for a blue screen.

Once you've forced the stop, run the official Microsoft Windows Update Troubleshooter to repair any corrupted update components, then try your update again.

One specific pattern I've seen repeatedly in forum reports is the "service cannot accept control messages after reboot" complaint. If you attempt to stop update services in the first few minutes after sign-in, you'll often trigger this error because the update stack is still finalizing state from the previous boot. Let the machine settle — go grab a coffee — then try again.

If the error keeps returning, deeper system corruption may be involved. Run SFC /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth — I've fixed several stubborn cases this way, although it requires patience and a stable internet connection.

---

Fix 4: IIS App Pools, Credential Manager, and Other Common Error 1061 Scenarios

IIS: Fix the Error When Starting or Stopping an App Pool

IIS App Pool errors were a rite of passage for me early in my career, and developers still hit them constantly. The root cause is usually that the App Pool is stuck and its worker process needs to be cycled.

First, confirm that both the World Wide Web Publishing Service (W3SVC) and the Windows Process Activation Service (WAS) are running — App Pools depend on them. Then:

1. Open IIS Manager, select the App Pool stuck in Starting or Stopping, and try Recycle or Start.

2. If the App Pool remains stuck, kill its worker process from Task Manager:

   taskkill /F /IM w3wp.exe
   

   Note: this kills all IIS worker processes, so use it only if you have a single site server.

3. Start the App Pool again from IIS Manager.

If you prefer the command line, use the IIS appcmd tool:

C:\Windows\System32\inetsrv\appcmd recycle apppool "YourAppPoolName"

This targeted command recycles just the one pool, which is significantly less disruptive on shared hosting environments.

Credential Manager (VaultSvc) Service Error 1061

Credential Manager is one of those services people forget exists until it breaks. Third-party software — especially system "cleaners" — can disable it, and then anything requesting credential operations triggers Error 1061.

1. Open services.msc, locate Credential Manager, and double-click it.
2. Set Startup type to Automatic, click Apply, then click Start.

If the GUI refuses to start it, use the command line:

sc config VaultSvc start= auto
sc start VaultSvc

After the service shows Running, retry the application that triggered the error. This fix alone resolves a meaningful portion of Credential Manager-related Error 1061 reports I've seen on Microsoft's own support forums.

Third-Party Sync Apps, Sitecore Installs, and Other Reported Triggers

The pattern extends well beyond Microsoft software. A popular accounting sync application, AutoEntry, documents this exact error when its desktop sync service gets stuck — users end the two related client processes in Task Manager, then restart the sync service. It works because the service's process, not the service configuration, was hanging.

I've also seen Sitecore Commerce installations fail with Error 1061 when a dependent Windows service was still pending during setup. The generic fix path for any third-party service:

1. Identify the service name.
2. Run sc queryex <service-name> to find its PID.
3. Kill the hung process with taskkill /F /PID <PID>.
4. Start the service with sc start <service-name>.

If you're troubleshooting an application you rely on, resist the urge to uninstall it first — this is almost always a Windows service-state issue, not a broken installation.

---

Error Code 1061 vs. 1053 vs. 1079: How to Tell Them Apart

Three Windows Service Errors People Frequently Mix Up

Error 1061 is specific: the service is mid-transition and can't process your command. But two other Windows service errors look similar and cause endless confusion.

What About "The Device Cannot Accept Control Messages at This Time"?

You might encounter a forum thread where the exact wording is "The device cannot accept control messages at this time" instead of "service." The same principle is at work: a hardware device or its driver is in a transitional state and cannot accept a new command at that precise moment.

The fix sequence mirrors what I've already covered: wait a few seconds, disable and re-enable the device in Device Manager, and reboot if it remains unresponsive. Underlying registry and driver issues follow similar logic, even though the message text differs slightly.

---

Frequently Asked Questions

How do I fix "The service cannot accept control messages at this time" in Start App Pool?

Verify that the World Wide Web Publishing Service (W3SVC) and Windows Process Activation Service (WAS) are both running. Open IIS Manager, select the stuck App Pool, and try Recycle. If it remains stuck, kill the w3wp.exe worker process with taskkill /F /IM w3wp.exe, then start the App Pool again. The command-line alternative is appcmd recycle apppool "YourAppPoolName" from C:\Windows\System32\inetsrv.

What is Windows error code 1061?

Error 1061 means ERROR_SERVICE_CANNOT_ACCEPT_CTRL: the Windows Service Control Manager sent a control request while the service was in a START_PENDING or STOP_PENDING state, so the service couldn't accept the command at that moment.

How long should I wait before force-stopping a stuck Windows service?

Most service transitions complete in seconds. Wait a full 60 seconds and retry once. If the service still shows Start Pending or Stop Pending, use taskkill /F /PID <PID> with the PID from sc queryex. Never force-kill critical system services like RPC, Plug and Play, or Security Accounts Manager — those can destabilize Windows.

How do I fix error 1053 and error 1079?

Error 1053 is a startup timeout issue — the service didn't respond within the configured window. Fix it by checking dependencies and increasing the service timeout. Error 1079 is a service account mismatch within a shared process — open the service's Log On tab and set the account to match the other services in that process.

---

Final Thoughts: Don't Let Error 1061 Derail Your Day

Error 1061 is almost always a service-state conflict, not a sign of a corrupted operating system or a broken application. The fastest path is straightforward: wait 60 seconds, retry in services.msc, then escalate to sc stop, taskkill, or PowerShell if the service remains stuck.

The scenario-specific fixes matter too. IIS App Pools need the W3SVC worker process to be recycled; Windows Update services need to be stopped in dependency order; Credential Manager needs to be re-enabled; and third-party sync services usually just need their hung processes killed and restarted.

If forced termination becomes a recurring routine rather than a one-time fix, dig deeper: verify the service account and its password, check the dependency chain, review disk health, and run SFC /scannow plus DISM /Online /Cleanup-Image /RestoreHealth to repair any underlying system file corruption.

Which method fixed your Error 1061? Tell us in the comments and include the exact service name that triggered the error so we can help other readers with the same scenario. If you're still stuck after working through all six fixes, describe your workflow and we'll point you to the next step.