Fix ERROR_SERVICE_DISABLED (0X00000422) – 3 Common Causes

Cause #1: The Service Is Manually Set to Disabled

This is the most common reason. A program or a user accidentally set the service to 'Disabled' in the Services console. It's an easy fix.

1. Press Windows + R on your keyboard. A run box pops up.
2. Type services.msc and hit Enter. This opens the Services window.
3. Find the service that's giving the error. Look at the Name column. If you're not sure which one, look at the error message in Event Viewer or the program that crashed. Common ones: Windows Update, Print Spooler, Windows Firewall.
4. Right-click that service and choose Properties.
5. In the 'Startup type' dropdown, change it from Disabled to Automatic (or Automatic (Delayed Start) for some services).
6. Click Apply. You should see the Apply button turn gray – that's your cue it saved.
7. Click Start to run the service right now. The Status column should change to 'Running'.
8. Click OK.

Once you do this, restart your computer. The error should be gone. If it comes back after a reboot, move to Cause #2.

Cause #2: Group Policy Blocked the Service

Sometimes a group policy setting overrides your manual changes. This is common on company computers or if you're running Windows Pro or Enterprise. The policy tells Windows to keep the service disabled no matter what you do in Services.

1. Press Windows + R, type gpedit.msc, and hit Enter. If it says 'Windows cannot find gpedit.msc', you have Windows Home edition – skip this cause and go to Cause #3.
2. Go to: Computer Configuration > Administrative Templates > System > Services.
3. Look for a setting named something like 'Turn off Windows Update device search' or the specific service name. For example, if the error is about the Print Spooler, look for 'Turn off Print Spooler'.
4. Double-click the policy. If it says Enabled, change it to Not Configured or Disabled. Most of the time, Not Configured lets the service run normally.
5. Click OK.
6. Close the Group Policy Editor.
7. Open a command prompt as admin (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)).
8. Type gpupdate /force and press Enter. It will update policies immediately.
9. Restart your computer.

After the restart, go back to Services (services.msc) and check if the startup type is still Automatic. If it changed back to Disabled, the policy is still active – double-check you set it to Not Configured, not Enabled.

Cause #3: Third-Party Software Disabled the Service

I've seen antivirus programs (like Malwarebytes, Norton, or McAfee) disable Windows services they think are risky. Also, some system cleanup tools like CCleaner or AVG TuneUp can accidentally turn off services to 'speed up' your PC. This is a sneaky cause because the change isn't in Windows itself.

1. Open your antivirus or system optimization software. Look for settings like 'System Protection', 'Startup Manager', or 'Service Manager'.
2. Find a list of disabled services. They might call it 'Disabled items' or 'Stopped services'.
3. Look for the service that matches your error. For example, if you got 0X00000422 trying to run Windows Update, find 'Windows Update' in the software's list.
4. Enable it. The button might be 'Enable', 'Allow', or 'Set to Automatic'.
5. Apply the change. Some software needs a restart – do it.
6. Now reboot your PC.

One real-world example: I had a user whose Malwarebytes Premium kept disabling the Windows Firewall service because it thought it conflicted with its own firewall. We had to add an exception in Malwarebytes for the Windows Firewall service. Check your software's help docs for 'exclusions' or 'allow list'.

If you don't know which software did it, think about what you installed recently. A quick trick: boot Windows in Safe Mode (press F8 during startup or hold Shift while clicking Restart). In Safe Mode, third-party software doesn't load. If the service works fine there, then yes – a third-party program is the culprit. Uninstall the program or contact their support.

Quick-Reference Summary Table

That's it. Try these in order – start with Cause #1, it's the quickest. If that doesn't stick, move to Causes #2 and #3. You'll have that service running in no time.