Fix ERROR_SERVICE_NOT_ACTIVE (0X00000426) on Windows Server

You're staring at error 0X00000426 – ERROR_SERVICE_NOT_ACTIVE. This one's straightforward: the service you need hasn't been started. I've seen this mostly on Windows Server boxes running SQL Server, print spoolers, or file share services. One client last month hit it after a Windows Update reboot killed their print server. Another got it on a Domain Controller when the NetLogon service decided to play dead after a patch Tuesday.

Root Cause: Why It Happens

The service is either stopped, disabled, or stuck in a weird state. Common triggers: a failed service recovery, a dependency didn't start first, or someone accidentally set the startup type to Disabled during a troubleshooting session. Also happens after a system crash where the service didn't restart properly. Think of it like a car that won't start because the battery's dead – the service is there, but it's not running.

Fix Steps: Get That Service Running Again

1. Identify the failing service. Look at your application's logs or the Event Viewer under Windows Logs > System. Filter by the time the error appeared. The source will tell you exactly which service is the problem. Had a case where it was the Windows Time service – took me 30 seconds to find.
2. Open Services Manager. Press Win + R, type services.msc, hit Enter. Find the service from step 1. Check its Status column – it'll say Stopped. Right-click it and select Start. If it starts, you're golden for now. But it'll likely stop again after a reboot.
3. Check startup type. Double-click the service. Under Startup type, make sure it's set to Automatic (or Automatic (Delayed Start) for services that don't need to boot immediately). Manual is okay if you're starting it on demand, but Automatic keeps it running after reboots. I always set core services like DNS or DHCP to Automatic with a 2-minute delay to let the network stack fully initialize.
4. Fix dependencies. Still failing? Click the Dependencies tab inside the service properties. It'll show services that must be running before yours. Note them down. Go start each one in order – or set them all to Automatic. For example, the Print Spooler depends on RPC Endpoint Mapper and HTTP Service. If those aren't running, your print queue goes nowhere.
5. Use the command line. Don't want the GUI? Open PowerShell or Command Prompt as admin. Run sc query [service name] to see the current state. Then sc start [service name] to start it. If it fails, check the error – "1058" means disabled, "1068" means a dependency is missing. Fix those before retrying.
6. Check Service Recovery options. Back in services.msc, go to the Recovery tab. Set First failure to Restart the Service, Second failure to Restart the Service, and Subsequent failures to Take No Action. This auto-starts the service if it crashes. I also set Reset fail count after 1 day – stops the service from getting stuck in a restart loop.

What To Check If It Still Fails

If you've done all that and the error keeps popping up, dig deeper. Check if the service account has the right permissions. Open Local Security Policy or gpedit.msc, go to Security Settings > Local Policies > User Rights Assignment. Make sure the service account has "Log on as a service" rights. I've seen SQL Server fail because the service account's password expired – reset it in AD and then update it in the service properties.

Also run the sfc /scannow command to check for corruption in system files. If that finds nothing, check the System event log for errors from Service Control Manager (source: "Service Control Manager"). That'll tell you exactly why the service failed to start – like a missing DLL or a timeout. Last resort: re-register the service with sc create or reinstall the application. But honestly, nine times out of ten, it's a startup type mix-up or a dependency that someone accidentally disabled. Fix those two things and you're out the door.