Fix 0X00000859: Workstation Service Inconsistent State

The 30-Second Fix: Restart and Repair the Service

What's actually happening here is the Workstation service (the LanmanWorkstation service) got stuck in a transitional state. This usually happens after a network adapter change, a failed Windows Update, or when you join/leave a domain without a clean reboot. The service thinks it's in the middle of something, but that something never finished.

Open Command Prompt as Administrator. Don't bother with PowerShell unless you're already there — the commands are the same.

net stop LanmanWorkstation /y
net start LanmanWorkstation

The /y flag forces the stop even if dependent services complain. After starting, run net start alone to confirm the service is listed as running. If you still see error 0X00000859 when trying to access a network share, move to the next step.

The 5-Minute Fix: Clean Up the Service State in the Registry

The reason step 1 sometimes fails is the service state is cached in the registry. The Start value might be correct (usually 2 for auto-start), but the internal service controller memory is corrupted. This is especially common on Windows 10 22H2 and Server 2022 after a network profile migration.

1. Open regedit as Administrator.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation.
3. Check the Start value — it should be 2 (hex). If it's anything else, set it to 2.
4. Delete the FailureActions key entirely. Don't be scared — Windows will recreate it with defaults on next service start. This clears any corrupted failure state that's keeping the service in limbo.
5. Restart the machine. Not the service — a full restart. The service controller needs to reinitialize its internal state table.

If you're on a domain-joined system, also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Look for DomainCompatibilityMode — if it's set to 1 and you're not in a mixed-mode domain, that can cause the inconsistent state. Set it to 0.

The 15+ Minute Fix: Repair the SMB Stack and Network Stack

If neither of the above worked, the workstation service isn't the root cause — it's a symptom of a deeper SMB or network stack corruption. I've seen this most often after a VPN client install (looking at you, Cisco AnyConnect 4.x) that mangles the Winsock catalog, or after a failed in-place upgrade from Windows Server 2016 to 2019.

First, reset the network stack completely:

netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew

Second, re-register the SMB services. This forces the service controller to rebuild its dependency graph:

sc config LanmanWorkstation start= auto
sc config mrxsmb start= auto
sc config mrxsmb20 start= auto
sc config srv start= auto
sc config srv2 start= auto

Notice the space after start= — that's not a typo. The sc command requires that exact syntax.

Third, check the SMB version. If SMB 1.0 is enabled on a modern system (it shouldn't be), it can conflict with the SMB 2.0+ driver state. Run Get-SmbServerConfiguration | Select EnableSMB1Protocol in PowerShell. If it's True, disable it:

Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force

Fourth, if you're still hosed, rebuild the security descriptor for the service. Use Powershell:

sc sdset LanmanWorkstation D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

This sets the default security for the service. A corrupted SD can block the service from reading its own configuration, which looks exactly like the inconsistent state error.

After all that, reboot. If the error persists, you're looking at a system file corruption. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. The DISM step is critical — SFC alone won't fix component store corruption that often triggers this error on Server 2022.

One last thing: check the System event log for event ID 7023 or 7031 from the LanmanWorkstation source. Those events will tell you exactly which dependency failed. Common culprits: NSI service (Network Store Interface) or MRxSmb (SMB mini-redirector). If you see NSI failing, your network adapter drivers are likely the real problem — update them from the OEM site, not Windows Update.