FIX: Win32: The service cannot be started, either because it is disabled…

A ‘disabled’ Service cannot be started?

Subtle hint… A colleague came to me and said he could not start a Service with the error message: ‘Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.‘.

FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

A ‘disabled’ Service cannot be started!!!

We will need to change the Startup Type from Disabled to either manual or automatic, but a disabled Service cannot be started.

Open Run and type in Services.msc.
Right click on the Service and choose Properties

FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Open the Startup Type field and change the setting to the desired option (Automatic or manual).

FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
FIX: Win32: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For the PowerShell savvies among us

Change SERVICENAME to the correct service name and run the below to Set the StartupType to Automatic and to start the service.

$Service = SERVICENAME
Set-Service $Service -StartupType Automatic
Start-Service $Service

Published by

Bas Wijdenes

My name is Bas Wijdenes and I work as a PowerShell Automation Engineer. My main focus is PowerShell, Azure AD, Azure Infrastructure, Server Management, and Exchange (Online).

Leave a Reply

Your email address will not be published. Required fields are marked *