Fix Error 0X00000836: Workstation Driver Not Installed

I've seen this error pop up on a Tuesday morning more times than I'd like. You're trying to map a network drive or connect to a shared folder, and boom—0X00000836 with the message "The workstation driver is not installed." It's frustrating because everything else seems fine. Let's fix it.

What you'll see

On Windows 10 or Windows 11 (22H2 and later), you might get this when running net use in Command Prompt, or when you double-click a network share in File Explorer. The exact text is usually:

System error 0X00000836 has occurred.
The workstation driver is not installed.

The real fix: reinstall the workstation service

Skip the registry tweaks you'll find on random forums. The real fix is to remove and re-add the Workstation service (LanmanWorkstation). It takes about two minutes.

Open Command Prompt as Administrator. Type cmd in the Start menu, right-click it, pick "Run as administrator."
Type this command and hit Enter:
```
sc delete lanmanworkstation
```
After you press Enter, you should see [SC] DeleteService SUCCESS. If you get an error like "ACCESS_DENIED," you aren't running as admin—double-check that.

Now install it fresh:

sc create lanmanworkstation binpath="C:\Windows\System32\svchost.exe -k NetworkService" start= auto displayname="Workstation" depend= bowser/mrxsmb10/mrxsmb20/nsi

Hit Enter. You'll see [SC] CreateService SUCCESS.

Start the service:
```
sc start lanmanworkstation
```
You should see SERVICE_NAME: lanmanworkstation followed by STATE : 4 RUNNING.

That's it. Try your network connection again. In 9 out of 10 cases, the error vanishes immediately. If it still shows, reboot once—sometimes the service needs a clean start after being recreated.

Why this works

The Workstation service is the Windows component that handles outbound connections to SMB shares. When its driver (the underlying kernel-mode piece) gets corrupted or goes missing—often after a failed Windows update, a third-party antivirus uninstall, or a registry cleaner tool—you get 0X00000836. Deleting and recreating the service forces Windows to rebuild the driver binding from scratch. It's the same principle as reseating a loose cable. We're not guessing; we're restoring a known-good state.

Less common variations

Sometimes the error hides inside an application, not File Explorer. For example, I've seen it in backup software like Veeam Agent or in older versions of QuickBooks when they try to access a network database. The fix above works for those too—same service, same problem.

Another variation: you might see the error in the Event Viewer under System logs with source bowser or mrxsmb. That's just the same issue reported differently. Reinstall the Workstation service and it'll stop logging those errors.

One more: on Windows Server 2016/2019, I've seen 0X00000836 after a domain controller promotion fails. The fix is identical—sc delete lanmanworkstation then recreate it. No special server steps needed.

What if the sc commands fail?

If sc delete gives you service does not exist, that's weird but fixable. The service registry key might be missing. Run this instead:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation" /f

Then run the sc create command from above. That manually creates the missing registry key, letting the service install properly.

If you still get errors after the reg add, check that the LanmanWorkstation folder inside C:\Windows\System32\drivers exists. If not, copy it from a working machine with the same Windows build. Don't skip this—it's rare but it happens after a botched feature update.

Prevention for next time

Three things keep the Workstation service healthy:

Don't run registry cleaners. They strip out entries they shouldn't, including service driver paths. CCleaner's registry cleaner is a common culprit. Just don't.
Keep SMB 1.0 disabled. It's a security risk anyway. The Workstation service doesn't need it. Go to Control Panel > Programs > Turn Windows features on or off, and uncheck "SMB 1.0/CIFS File Sharing Support" if it's enabled.
After a Windows feature update, check the Workstation service is running. Open Services.msc, scroll to "Workstation," and make sure its status is "Running" and startup type is "Automatic." If it's stopped, start it—don't wait for an error.

That's the whole thing. No fluff, no magic. Took me about 90 seconds to type the commands, and it'll take you less than five minutes to run them. Good luck.