Fix ALPC Error 0XC0000701: STATUS_MESSAGE_LOST on Windows

1. Corrupted System Files

This is the number one reason I see 0XC0000701. The ALPC (Advanced Local Procedure Call) component needs clean system files to pass messages between processes. When a key .dll or driver gets corrupted—often after a botched Windows update or a drive failure—the message simply never arrives. Last month, a client's machine threw this error every time they opened Outlook; turns out a Windows 11 preview update had busted the ntdll.dll file. The fix is straightforward, but skip the fluff:

1. Open Command Prompt as Administrator (right-click Start, choose that).
2. Run sfc /scannow. Let it finish—takes 10-15 minutes.
3. If SFC finds issues but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth. This pulls fresh files from Windows Update.
4. Reboot. Check if the error's gone.

If SFC reports corruption but DISM fails (happens if your Windows Update is broken), use a Windows installation USB. Run DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess (replace D: with your USB drive letter). I've had to do this on three machines this year—it works when online repair doesn't.

2. Hung or Corrupted Windows Services

ALPC relies on services like the Print Spooler, Windows Update, and Background Intelligent Transfer Service. If one of these gets stuck or its state file gets corrupted, messages pile up and eventually fail. The classic trigger: a print job that hangs, then you reboot, and boom—0XC0000701 during login. Here's what to do:

1. Press Win + R, type services.msc, hit Enter.
2. Look for these services:
   - Print Spooler
   - Windows Update
   - Background Intelligent Transfer Service (BITS)
3. Right-click each one, select 'Stop'. If any are already stopped or won't stop, note them.
4. For the Print Spooler: open an admin Command Prompt and type del /Q /F %systemroot%\System32\spool\PRINTERS\*. This wipes stuck print jobs.
5. For Windows Update: run net stop wuauserv then net stop bits. Then delete the SoftwareDistribution folder: rmdir /S /Q C:\Windows\SoftwareDistribution.
6. Restart all services: net start spooler, net start wuauserv, net start bits.
7. Reboot.

On a client's Windows 10 box, the error only showed when they tried to print from Chrome. Clearing the spooler folder alone fixed it—no SFC needed. But if you see the error at random times, go with the service reset.

3. Third-Party Software Conflicts

Sometimes a program hooks into ALPC and screws things up. Antivirus suites (especially Norton and McAfee) are notorious for this. I've also seen VPN clients and printer management tools cause it. The error usually appears after installing something new. To test:

1. Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart > press 4).
2. If the error doesn't show in Safe Mode, it's a third-party driver or service. Boot normally, then use Autoruns (free from Microsoft) to disable non-Microsoft services one by one.
3. Start with the newest installs. Reboot after each disable until the error stops.

One client had a cheap USB printer driver that was intercepting ALPC messages. Uninstalling the driver and using the Windows built-in driver for that old HP LaserJet solved it instantly. Another case: McAfee's firewall component was blocking internal IPC calls. Removing the suite fixed it, then a fresh install of a different antivirus worked fine.

Quick-Reference Summary

Start with #1—it covers the most cases. If you hit a dead end, a repair install of Windows (using the Media Creation Tool, keep files) almost always kills this error. It's the nuclear option, but I've used it on three machines this year alone.