Fix 0X000008FB: Message alias delete failure across networks

When this error hits you

You're managing a Windows 10 Pro 22H2 workstation, or maybe a Server 2022 box, and you just removed a user from Active Directory. Or you're cleaning up old computer accounts after a domain migration. You run a NetMessageBufferDelete command or a script that tries to remove a messaging alias, and bam — you get 0X000008FB. The full message says "The message alias was not successfully deleted from all networks", and the system logs show NERR_IncompleteDel. It's frustrating because the user or computer account is already gone in AD, but Windows insists the alias didn't fully delete across every network path it knows about.

What's really going on

This error isn't about your email. It's about the Windows messaging alias system — a leftover from LAN Manager days that still lives in modern Windows for legacy network messaging (like the old net send command). When Windows tries to remove an alias, it checks every network node (workstations, servers, domain controllers) that might have that alias cached. If even one node can't confirm the deletion — because it's offline, unreachable, or the alias is locked — Windows throws this incomplete error. The real trigger is a mismatch between what Active Directory says and what the local messaging subsystem expects. Most common after a user is force-deleted from AD without properly removing their messaging alias first, or after a computer account is removed from a domain while still hosting an alias.

The fix: clean the alias from all angles

You need to hit this from three sides: the registry, the Net command line, and sometimes the network cache itself. Here's the exact order that works for me every time.

Step 1: Kill the alias in the registry

Press Win + R, type regedit, hit Enter. If User Account Control pops up, click Yes.

Go to this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Look for a value named Aliases or MessageAliases — often a REG_MULTI_SZ (multi-string) entry.
Double-click it. You'll see a list of aliases, one per line. Find the one that's stuck — it might be a username or computer name that you've already deleted from AD.
Delete that line entirely. Don't leave a blank line. Then click OK.
After clicking OK, close Registry Editor. You won't see any immediate change — that's normal.

Step 2: Force the deletion using the Net command

Open Command Prompt as administrator. Right-click Start, choose Command Prompt (Admin) or Windows Terminal (Admin).
Run this command, replacing aliasname with the actual alias you're trying to remove:
```
net alias aliasname /delete
```
After you press Enter, you should see one of two things: "The alias was successfully deleted" (great, you're done) or the same 0X000008FB error again (means Step 1 didn't fully clear it, or there's a network holdout).
If you get the error again, wait 30 seconds, then retry the net alias delete. Sometimes the registry change needs a moment to propagate to the service.

Step 3: Flush the network cache and restart the service

Still in the admin command prompt, run:
```
net stop lanmanserver /y
```
After you press Enter, you'll see "The Server service is stopping." Wait for it to finish.
Then run:
```
net start lanmanserver
```
After this, you should see "The Server service was started successfully."
Now try the delete again:
```
net alias aliasname /delete
```
This time it should succeed. You'll see the confirmation message.

Step 4: Verify no lingering references in AD or local SAM

If the alias was for a user account that no longer exists in Active Directory, run this on a domain controller (or from a machine with RSAT tools):
```
Get-ADUser -Filter {SamAccountName -eq "aliasname"}
```
Replace aliasname with the alias. If it returns nothing, the AD side is clean.
On the local machine, open an admin PowerShell and run:
```
Get-LocalUser | Where-Object {$_.Name -eq "aliasname"}
```
If nothing comes back, there's no local account with that alias.

If the error still won't clear

Sometimes the alias is stuck on a remote server that's offline or has a stale cache. In that case, you need to clean it from the source. Check these:

Check the Primary Domain Controller (PDC) emulator. Log into the PDC emulator (it's usually the first DC in the domain). Open Command Prompt as admin there and run net alias aliasname /delete. This clears the authoritative copy.
Look for hung sessions. On any machine that shows the alias, run net session to see open connections. End any sessions tied to that alias with net session \\computername /delete.
Restart the entire machine. I know it's brute force, but if you've done Steps 1-4 and it's still there, a full restart flushes everything. After the restart, run net alias (no arguments) to list all remaining aliases — the problem one should be gone.

If none of that works, you're dealing with a replication delay across multiple sites. Wait an hour (or run repadmin /syncall on the DCs), then retry Step 2. That usually sorts it.