Fix ERROR_SERVER_DISABLED 0X0000053D on Windows Server

Quick answer: The server got disabled because its service start type was changed to Disabled or the registry entry Start under SYSTEM\CurrentControlSet\Services\LanmanServer is set to 4. Run sc config LanmanServer start= auto and net start LanmanServer as admin to fix it.

I know this error is infuriating—you're staring at a server that suddenly won't talk to anyone. I've seen this on Windows Server 2012 R2 through 2022, usually after a security tool or a failed update disabled the Server service. The real culprit is almost always the LanmanServer service (SMB server) being set to Disabled. When that happens, the server can't respond to any SMB requests, and you get the 0X0000053D error. Let's get it back online.

Why This Happens

This error pops up when the Server service (LanmanServer) is disabled. Common triggers:

Someone accidentally changed the service startup type via services.msc or Group Policy.
A security hardening script (like from CIS benchmarks) set it to disabled, thinking you didn't need SMB.
A failed Windows update corrupted the service registry entry.
An antivirus or endpoint detection tool quarantined the service.

The server can still boot, but any SMB connections—file sharing, printer sharing, remote admin—fail immediately.

Fix Step-by-Step

Open Command Prompt as Administrator. Press Win+R, type cmd, then press Ctrl+Shift+Enter.
Check the current service state. Run:
```
sc query LanmanServer
```
Look for STATE and START_TYPE. If START_TYPE shows 4 (disabled), you've found the issue.
Re-enable the service. Run:
```
sc config LanmanServer start= auto
```
Note the space after start=—yes, it's required.
Start the service. Run:
```
net start LanmanServer
```
You should see "The Server service is starting..." and then "The Server service was started successfully."
Verify the error is gone. Try connecting from another machine via net use or File Explorer. If you get 0X0000053D again, reboot the server.

Alternative Fix: Registry Edit

If sc config doesn't work—maybe the service is protected or the registry is corrupted—edit it directly.

Open Regedit as Administrator.

Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer

Find the Start DWORD. Set it to 2 (automatic start) or 3 (manual). Do not set it to 4 (disabled).
Close Regedit, reboot the server.

I've also seen cases where a Group Policy Object forced the service to be disabled. Check gpedit.msc under Computer Configuration > Windows Settings > Security Settings > System Services. Find Server, set it to Automatic, and apply.

What Not to Do

Don't reinstall the SMB feature unless you're absolutely sure the service binary is missing. That's almost never the case.
Don't delete the registry key—that will break things worse.
Don't ignore the error. A disabled server service can also affect Kerberos authentication and Netlogon.

Prevention Tip

Before you run any security script, check if it disables the Server service. If you're hardening a server that needs file sharing, set the service to Automatic but restrict SMB versions or enable SMB encryption instead of killing the service. Also, snapshot your server before applying Group Policy changes—it'll save you time if something like this happens again.

One real-world scenario: I had a client whose IT admin ran a CIS hardening script that disabled all unnecessary services. They didn't realize the Server service was needed for the file server. After the script ran, the entire office couldn't access shared drives. This exact error appeared in the event log. The fix was the sc config command above. Took 30 seconds.