Fix 0X000008E9: Messenger Service Paused Error

Yeah, I know — you're trying to send a message across the network and Windows throws that 0X000008E9 error. It's annoying, but it's also a dead simple fix. The culprit here is almost always the Messenger service on the receiving machine being in a paused state. Let's get it running again.

Fix It: Restart the Messenger Service

Do this on the machine that's supposed to receive the message — the one showing the error. Open an admin Command Prompt or PowerShell:

net stop messenger
net start messenger

That's it. Test your net send or whatever tool you're using. If the error goes away, you're done.

If you'd rather use the GUI, hit Win + R, type services.msc, find Messenger in the list, right-click it, and click Resume (if paused) or Restart. Don't bother changing the startup type — Messenger's default is Manual, which is fine. You only need it running while you send messages.

Why This Works

The Messenger service handles net send and older messaging protocols. When it's paused, it's still installed and technically loaded, but it won't process incoming messages. The error message literally says NERR_PausedRemote — it's telling you the remote side is paused. Restarting it forces the service to resume normal operation.

A paused service is different from a stopped one. If it were stopped, you'd get a different error (like 0X000006D9 or 1722). Paused means Windows intentionally suspended it — usually because someone right-clicked and clicked Pause, or a script ran net pause messenger. Either way, a net start command after a net stop clears the pause flag.

Less Common Variations

Sometimes the issue isn't on the recipient, but on a server between them. If you're using a dedicated messaging server or a terminal server, check its Messenger service too. I've also seen this happen when a domain controller's Messenger service gets paused by a group policy object that accidentally sets the service pause state.

Another variation: the error appears on a Windows Server 2003 or Windows XP machine, but the target is a newer OS like Windows 10 or Server 2019. The Messenger service was removed starting in Windows Vista and Server 2008. Those newer systems don't have the service at all. In that case, the error isn't really paused — it's because the service doesn't exist. The fix is to upgrade your messaging approach: use PowerShell remoting, msg command (available on newer Windows versions), or a third-party tool.

I've also run into this on clustered servers. If the Messenger service is running on the active node but paused on the passive node, failover can cause the pause state to persist. Check both nodes.

Prevention

The Messenger service is a legacy service. Microsoft deprecated it years ago. If you're relying on it for admin alerts or inter-machine communication, it's time to move on. But if you're stuck with it for now:

Don't pause the service manually. Train your team not to right-click and hit Pause. It's a rarely used action that causes this exact headache.
Use a startup script. If you need Messenger running on certain machines, set the startup type to Automatic in services.msc, and add a net start messenger line to a logon script or scheduled task.
Check GPOs. Look for Group Policy settings that might pause services. The policy is at Computer Configuration > Windows Settings > Security Settings > System Services. If Messenger is set to Pause, that's your problem.
Monitor service state. Use a simple script to check the Messenger service state across your environment. PowerShell's Get-Service -Name Messenger returns the status. If it's Paused, restart it automatically.

Bottom line: the fix is trivial, but tracking down why it got paused in the first place is where you'll save future headaches. And seriously — consider migrating away from net send. It's been deprecated for over a decade.