NERR_RunSrvPaused (0X00000951): Server Paused on Windows

Cause #1: The Server Service Is Manually Paused After a Windows Update

The most common trigger for error 0X00000951 is a recent Windows Update that pauses the LanmanServer service. What's actually happening here is that the update's post-install phase sometimes leaves the service in a paused state instead of running. You'll see this on Windows Server 2016 through 2022, and occasionally on Windows 10/11 Pro when file sharing stops working.

Don't overthink this. The fix is to resume the service directly.

1. Open Command Prompt as Administrator.
2. Run net continue server. This resumes the paused service immediately.
3. Verify with net start | findstr Server. You should see 'Server' listed as started.

The reason this works is that net continue sends a SERVICE_CONTROL_CONTINUE signal to the service control manager. It's the only command that correctly resumes a paused service — restarting or starting won't work because Windows sees the service as already 'started' but paused. The error code 0X00000951 maps to NERR_RunSrvPaused, which means the service isn't stopped — it's just frozen in place.

If you prefer PowerShell: Resume-Service -Name LanmanServer. Both do the same thing under the hood.

Cause #2: A Group Policy or Admin Script Paused the Service

Sometimes an overzealous IT policy or a legacy login script issues a net pause server command. This happens more often than you'd think — someone copies a script from 2005 without checking what it does. The pause command doesn't stop the service, it just suspends incoming connections. The service still shows as 'running' in Services.msc, which is why people miss it.

The symptom: clients can't connect to shared folders or printers, but the server looks healthy. You run sc query LanmanServer and see STATE: 4 PAUSED in the output.

Fix is the same as above: net continue server. But you also need to hunt down the offending script or policy. Check:

• Local Group Policy Editor (gpedit.msc) → Computer Configuration → Windows Settings → Scripts (Startup/Shutdown). Look for any .bat or .ps1 that contains net pause server.
• Active Directory Group Policy if this is a domain environment.
• Scheduled tasks that run net pause to 'maintain' the server — a common misguided practice for 'security'.

Once you remove the pause command, the service stays running after reboots. If you can't find the source, set a scheduled task at startup to run net continue server as a workaround. Not elegant, but it works.

Cause #3: Third-Party Backup or Security Software Interfering

Backup agents — especially legacy ones from Acronis, Symantec Backup Exec, or Veeam — sometimes pause the server service before a snapshot. The problem is they forget to resume it if the backup fails halfway through. The same goes for some antivirus suites that 'suspend' file sharing during scans.

You'll know this is the culprit because the error appears right after a scheduled backup window or a virus scan. Check the Application event log for entries from the backup software around the time the error started.

Fix: resume the service (net continue server) and then update or reconfigure the offending software. For backup software, find the setting that says 'pause server during backup' and disable it. Instead, use Volume Shadow Copy (VSS) for consistent backups without pausing the server. For antivirus, exclude the file server role from the scanning schedule.

One more thing: if the backup software uses its own service to pause LanmanServer, you might need to stop and restart that third-party service first, then resume LanmanServer. Check the software's documentation — but honestly, most of them just use net pause server under the hood, so the same command works.

Quick-Reference Summary Table

Don't waste time looking at SMB settings, firewall rules, or permissions when you see 0X00000951. The root cause is always a paused service. Resume it, then find out why it got paused in the first place. That second part is what stops it from happening again.