Fix NERR_DeleteLater (0X000008FA) — Message Alias Deleted Later

Cause #1: The NetBIOS alias is still registered and waiting for cleanup

The most common trigger for 0X000008FA is when you try to remove a computer name or message alias from a Windows machine that's still actively sharing resources. I've seen this on file servers where someone removes a DNS alias or NetBIOS name but the Server service (lanmanserver) still holds a reference to it. Windows schedules the deletion for later—hence the error text "This message alias will be deleted later"—but sometimes it never gets cleaned up.

Here's the fix that works 9 out of 10 times:

1. Open an administrative Command Prompt (Win+X → Terminal (Admin)).
2. Type net stop server and press Enter. This stops the Server service and releases all aliases.
3. Wait five seconds, then type net start server to restart it.
4. Now try the operation that gave you the error again—adding or removing a message alias via net name or NetMessageNameAdd.

If you're on Windows Server 2016 or later, you might need to run sc stop lanmanserver followed by sc start lanmanserver instead—same effect, slightly different command. The real fix here is forcing Windows to release the stale alias immediately. I once had a customer's print server that threw this error every time they renamed the server. A quick restart of the Server service cleared it instantly.

Cause #2: Pending deletion queue is stuck due to open SMB sessions

Sometimes the Server service itself isn't the problem—it's an active SMB session keeping the alias alive. Windows won't delete a message alias while a client is connected to it. This happens more than you'd think in environments with persistent drive mappings or printer connections.

To check for open sessions:

1. Run net session at an admin prompt. You'll see a list of connected clients.
2. Note the client IP or computer name and ask users to disconnect mapped drives or printers temporarily.
3. Force-close all sessions with net session /delete (be careful—this kicks everyone off).
4. Now run net name to see pending deletions: look for any alias with a status of "Deleting" or "Pending".
5. Use net name aliasname /delete to remove it permanently.

If the alias still refuses to die, open Computer Management → Shared Folders → Sessions and disconnect each session manually. I've also seen cases where a single hung client with an open file handle prevents the alias from being released. Check Open Files in the same console.

Windows 10 and 11 users: if you don't have the Server service running (typical on desktop OS), the error can still appear if you're using net name for messaging. The same session-check applies.

Cause #3: Corrupt registry entry for the alias

This one's rarer but gnarly when it hits. The alias entries live under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares and HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Aliases. A bad entry here can cause 0X000008FA even after restarting the service.

Before touching the registry—backup the key. I've seen too many techs delete the wrong value and take down the whole server.

1. Open Regedit as Administrator.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Aliases.
3. Look for a value with the alias name that's stuck. If you see one with a weird status flag (like a DWORD of 0x000002 or 0x000004 instead of 0), delete it.
4. Also check HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares for any share names that reference the alias—remove those references too.
5. Restart the Server service (or reboot the machine).

I did this for a client running Windows Server 2019 after they'd renamed a file server three times. The registry had orphaned entries from each previous name. Cleaning them out finally killed the 0X000008FA error for good.

Quick-reference summary table

Cause	Likelihood	Fix
Server service still holds the alias	Very common	Restart Server service (net stop server && net start server)
Open SMB sessions blocking deletion	Common	Disconnect sessions (net session /delete) then remove alias
Corrupt registry entries	Rare	Edit HKLM\...\Aliases and Shares registry keys, then reboot

That's it—three real-world causes, no fluff. Start with the first fix, move to the second if it doesn't work, and save the registry hack for last. You'll be past the 0X000008FA error in minutes.