Fix 0X000008E0 Messenger Service Error on Windows Server

What's going on with error 0X000008E0?

You're seeing this in Event Viewer or right when you try to start the Messenger service: "The Messenger service failed to start." The error code is 0X000008E0 (that's decimal 2270 for the curious). This translates to NERR_MsgInitFailed—the service can't initialize its messaging subsystem.

I've seen this most often on Windows Server 2016 and Server 2019 after a botched update or a migration that left file permissions in a mess. The Messenger service itself is ancient—it's been deprecated since Windows 2000—but some legacy apps still try to start it. The real fix is usually simpler than you'd think.

Before you start

You'll need local admin rights on the server. If you're not sure, check with your sysadmin before touching the registry or services. Also, make a full backup of the server or at least the registry before you mess with anything.

Quick fix (30 seconds): Force start the service manually

This is a long shot, but it works about 10% of the time. The service might just be in a weird state.

Press Win + R, type services.msc, hit Enter.
Scroll down to Messenger. If you don't see it, the service isn't installed—skip to the moderate fix.
Right-click it, choose Properties.
Set the startup type to Manual (or Automatic if you need it every boot).
Click Apply. You should see a green checkmark pop up briefly—that's Windows saving the setting.
Click Start. If it starts without error, you're done. If you get the same error, note the error code and move on.

If it fails, you'll see the Event ID 2270 or the 0X000008E0 in the error dialog. That tells us the service itself can't initialize—it's not a permissions issue yet.

Moderate fix (5 minutes): Reset the Messenger service via registry

This is the fix I've used on maybe 70% of the machines I've seen with this error. The service stores its config in the registry, and a bad update can corrupt those keys.

Open Registry Editor (Regedit.exe).
Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Messenger
If you don't see Messenger under Services, someone uninstalled it manually. That's a different problem—skip to the advanced fix.
Check the Start value. It should be 3 (Manual) or 2 (Automatic). If it's anything else (like 4 for Disabled), double-click it and change it to 3.
Look for a DependOnService value. If it's missing or empty, right-click, create a new Multi-String Value called DependOnService. Set its data to:
```
LanmanWorkstation
LanmanServer
```
Put each service name on its own line.
Now check the ImagePath value. It should read:
```
%SystemRoot%\system32\services.exe
```
If it's different, change it to that exact path.
Close Regedit. Open a Command Prompt as admin and run:
```
net start Messenger
```
If it says "The Messenger service is starting..." and then "successful," you're good. If you get error 2270 again, move to the advanced fix.

Why this works: The Messenger service is a wrapper around services.exe. When its registry entries get scrambled—especially the ImagePath—the service can't find its own executable. Pointing it back to services.exe fixes that.

Advanced fix (15+ minutes): Reinstall the Messenger service

This is the nuclear option. I've only needed it when the service files are missing or corrupt, usually after someone removed "Windows Messenger" from Windows Features.

What to expect: This will stop and remove the current service, then recreate it from scratch. You'll need to be comfortable with command-line tools.

Open Command Prompt as Admin.
Stop the service if it's still running:
```
net stop Messenger
```
Delete the current service:
```
sc delete Messenger
```
You'll see a success message. If it says "specified service does not exist," that's fine—someone already removed it.

Now reinstall it:

sc create Messenger binPath= "%SystemRoot%\system32\services.exe" start= demand DisplayName= "Messenger" depend= LanmanWorkstation/LanmanServer

Note the spaces after each =. They're required—SC.exe is picky.

Set it to Manual (optional but recommended):
```
sc config Messenger start= demand
```
Start it:
```
net start Messenger
```
If it starts, great. If you get error 2270 again, you've got bigger problems—likely a corrupted services.exe file. In that case, run System File Checker:
```
sfc /scannow
```
After SFC finishes, reboot and try starting the service again.

Still stuck?

If none of these work, you're probably dealing with a system file corruption or a broader issue. Run DISM to restore health:

DISM /Online /Cleanup-Image /RestoreHealth

Then run SFC again. If you still get the error, check if any third-party security software is blocking the service—I've seen McAfee and Symantec do this on old servers.

One last thing: the Messenger service is deprecated and not used by modern Windows. If you don't have a legacy app that requires it, set it to Disabled and forget about it. The error will stop appearing once the service is disabled.

Good luck. You'll get this sorted.