Fix ERROR_RESOURCE_DISABLED (0x000010D5) on Windows

1. A critical Windows service got disabled

This is the #1 reason I see 0x000010D5. Some service the app needs — like the Print Spooler, Server Service, or Windows Update — got shut off. Maybe a cleanup tool did it, maybe an update flipped a switch. Either way, fixing it takes two minutes.

Had a client last month whose entire print queue died because the Print Spooler service was disabled. Every time someone tried to print, boom — ERROR_RESOURCE_DISABLED. They'd been fighting it for three days before calling me.

Check and re-enable the service

1. Press Win + R, type services.msc, hit Enter.
2. Look for the service related to your problem. Common suspects:
• Print Spooler — if the error appears when printing
• Server — if it's a file share or network path
• Windows Update — if an updater or tool reports this
• Windows Audio — for sound-related issues
3. Double-click the service. If Startup type is Disabled, change it to Manual or Automatic.
4. Click Start to run it now, then Apply and OK.

That fixed it for the printer client. If you don't know which service, check the Event Viewer — look under Windows Logs > System for error events around the same time. The source will point you at the disabled service.

2. A device in Device Manager is disabled

Sometimes it's hardware. A network adapter, a USB controller, a display adapter — if it's disabled in Device Manager, any app that needs it gets this error. I saw this with a guy who couldn't connect to a network drive. His Realtek PCIe GbE controller was disabled after a driver update gone wrong.

Find and enable the device

1. Right-click the Start button, select Device Manager.
2. Expand categories. Look for any device with a down arrow icon (that means disabled).
3. Right-click the disabled device, select Enable device.
4. If the device is hidden, go to View > Show hidden devices first.

If you can't find the disabled device, check the system event logs again — the error might mention a hardware ID or device name. Search for that in Device Manager by right-clicking the top node and selecting Scan for hardware changes.

3. A Windows optional feature is turned off

Threw me for a loop the first time. A client's old inventory app wouldn't start — kept hitting 0x000010D5. Turned out they needed SMB 1.0/CIFS File Sharing Support, which Windows 10 and 11 disable by default for security. The app relied on it.

Other disabled features that trigger this: .NET Framework 3.5 (for legacy apps), Windows Subsystem for Linux, Hyper-V.

Enable the feature via Windows Features

1. Press Win + R, type optionalfeatures, hit Enter.
2. Look for the feature you need. For SMB 1.0, expand SMB 1.0/CIFS File Sharing Support, check the box.
3. Click OK, let Windows install it, then restart when prompted.

That app started right up after the restart. Just be careful — SMB 1.0 is old and insecure. Only turn it on if you absolutely need it for legacy gear, then disable it after.

Quick-reference summary table