Categories About Us Contact Us Become a Member

How to fix Windows error 1058 (ERROR_SERVICE_DISABLED)

This means a service could not start because it is disabled or has no enabled devices. Enabling and starting it fixes it. Jump to your situation below or work through the methods in order.

By Neeraj Singh ~6 min Updated Jun 2026 89% found this helpful
Error message
Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Summary

Error 1058 (ERROR_SERVICE_DISABLED) means a service could not start because its Startup type is set to Disabled, or it has no enabled devices associated with it. Something, a misconfiguration, an optimisation tool, malware cleanup, or a policy, set the service to Disabled, so Windows refuses to start it. The fix is to open services.msc, set the service's Startup type to Automatic or Manual, and start it. You can do the same from the command line with sc config. If the service depends on others that are also disabled, those need enabling too, and on a managed PC a Group Policy may be forcing the disabled state. Once the service is enabled and its dependencies are running, it starts and the error clears.

What this error means

Every Windows service has a Startup type. If it is Disabled, Windows will not start the service at all, by request or automatically. Error 1058 is Windows reporting exactly that: you asked it to start, but it is disabled.

So the cure is to enable it. Setting the Startup type to Automatic or Manual lets it start. The complications are dependencies, a service whose prerequisites are also disabled cannot run, and policy, where a managed machine may keep forcing the service back to Disabled.

Common causes

The service's Startup type is set to Disabled.
A dependency service is also disabled.
An optimisation tool or malware cleanup disabled it.
A Group Policy forces the service to Disabled.
The associated device is disabled.
Expert insight

“1058 is blunt: the service is switched off, so Windows will not start it. The fix is just as blunt, open services.msc, set it to Automatic or Manual, and hit Start. The two things that trip people up are dependencies, where the service you want needs another one that is also disabled, so you enable that too, and policy, where a work machine keeps flipping it back to Disabled. On a personal PC it is almost always a quick toggle.”

How to fix it

Method 1

Enable and start the service

1Open services.msc, double-click the service, and set Startup type to Automatic or Manual.
2Click Apply, then Start.
3The service should start without error 1058.
Method 2

Enable it from the command line

1From an elevated prompt, set the start type and start it:
sc config ServiceName start= auto
sc start ServiceName
2Note the space after start= is required.
3Use the service's short name from its Properties.
Method 3

Enable required dependencies

1On the service's Properties, Dependencies tab, check the services it relies on.
2Make sure those are also enabled and running.
3A disabled dependency blocks the service.
Method 4

Check policy on a managed PC

1If the service keeps reverting to Disabled, a Group Policy may be forcing it.
2Ask your administrator, who can adjust the policy.
3Then re-enable the service.
Method 5

Check the associated device

1If the message mentions no enabled devices, the related hardware may be disabled.
2Enable it in Device Manager, then start the service.

Error 1058 means the service is disabled, so open services.msc, set its Startup type to Automatic or Manual, and start it (or use sc config and sc start). Enable any disabled dependencies too, and on a managed PC check whether a Group Policy keeps forcing the service back to Disabled.

Frequently asked questions

What does Windows error 1058 mean?
The service cannot be started because it is disabled, or because it has no enabled devices associated with it. Its Startup type is set to Disabled.
How do I fix error 1058?
Open services.msc, set the service's Startup type to Automatic or Manual, and start it. From the command line, use sc config ServiceName start= auto then sc start ServiceName.
What sets a service to disabled?
A misconfiguration, an optimisation or tune-up tool, malware cleanup, or a Group Policy. On a managed PC a policy can keep forcing the service back to Disabled.
Why does it still fail after I enable it?
A dependency service may also be disabled. Check the Dependencies tab in the service's Properties and enable and start those services too.
How do I enable a service from the command line?
From an elevated prompt run sc config ServiceName start= auto (note the space after start=) then sc start ServiceName, using the service's short name.
It keeps reverting to disabled, why?
A Group Policy on a managed machine is likely forcing the disabled state. Ask your administrator to adjust the policy, then re-enable the service.

Still not working?

If a service cannot be enabled because its Startup type controls are greyed out, the restriction is usually a Group Policy or a permissions issue on the service registry key. An administrator can adjust the policy or the key's permissions. You can also submit your error to us for a tailored fix.

Was this fix helpful? Thanks for your feedback!