Fix 0X00000908 Session Not Found Windows Network

That Error Is Annoying — Let's Kill It Fast

I know that 0X00000908 error is infuriating. You're trying to clean up a network session, and Windows just says "nope, doesn't exist." But it usually does exist — Windows just lost track of it. Here's the fix.

The Real Fix: Delete the Session Manually

Skip the GUI for this one. Open Command Prompt as Administrator — right-click Start, choose Terminal (Admin) or Command Prompt (Admin). Then type:

net session \\computername /delete

Replace computername with the exact name you're trying to disconnect. For example, if the computer is named DESKTOP-ABC123:

net session \\DESKTOP-ABC123 /delete

Hit Enter. If the session exists, it'll disconnect. If it doesn't, you'll get the same 0X00000908 error — but that's OK, we're covering that case next.

When net session Fails, Force It

If net session still gives you the error, the session is already gone from the Server service's list but still shows in some tools (like Computer Management). Force it by using sc to query the Server service directly:

sc queryex lanmanserver

Look for the process ID (PID). Then kill any stale connections with net use — but this time, target the local drive mapping:

net use * /delete /y

This nukes all mapped drives. It's a sledgehammer, but it works.

Why This Error Happens

The error 0X00000908 maps to NERR_ClientNameNotFound. It fires when the Server service (lanmanserver) can't find the session you're referencing in its internal table. This usually happens because:

Another admin already disconnected the session, but your management tool didn't refresh.
The remote computer rebooted or went offline, so the session vanished.
A timing issue — you clicked too fast, and Windows was still enumerating sessions.

It's not a corruption or a real bug — it's just Windows being literal about what it sees right now.

Less Common Variations

Sometimes the error shows with a different computer name — like a typo or a fully qualified domain name (FQDN). If you used \\server01 and it fails, try \\server01.domain.local. Or check the session list first:

net session

If nothing shows, there's nothing to delete — the error is harmless.

I've also seen this on Windows Server 2016 and 2019 when the Server service is in a weird state. Restarting the service can clear it:

net stop lanmanserver && net start lanmanserver

That'll drop all active sessions, so do it during maintenance.

How to Prevent It

You can't fully prevent this error — it's a timing thing. But you can reduce how often you see it:

Wait a few seconds between listing sessions and deleting one.
Use net session in scripts with a short timeout /t 1 between commands.
If you use Computer Management's "Sessions" tool, refresh it before clicking Delete.

That's it. The error is more of a nuisance than a real problem. Now you know how to handle it.