Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Contact
  • Reviews
  • Toggle search form

The service could not be started either because it is disabled or because it has no enabled devices associated with it

Posted on 28/08/202004/10/2023 IT Expert By IT Expert No Comments on The service could not be started either because it is disabled or because it has no enabled devices associated with it
  1. Home
  2. Windows Server
  3. The service could not be started either because it is disabled or because it has no enabled devices associated with it
Service startup issues

Windows Deployment Services (WDS) is a Microsoft tool for deploying Windows Operating System (OS) over the network. In Windows Server 2003, it was referred to as Remote Installation Services (RIS). The purpose of WDS is to remotely deploy the Windows operating system. WDS uses a PXE method for booting clients. In this article, we shall discuss “The service could not be started either because it is disabled or because it has no enabled devices associated with it”. Please see Program startup: How to launch an application automatically during startup on Windows, and how to fix “The virtual machine ran into a non-fatal problem as described below, we suggest that you take appropriate action to prevent the problem from recurring“.

PXE enables clients to boot off the network. To find WDS services and to load boot images, the client should be able to contact the WDS server, and the client network card must be PXE compliant and most devices are NICs complaint. See this guide on how to set up and install the WDS role, and how to configure Windows Deployment Services on Windows Server 2019. Also, see how to configure DHCP Server option 60, 66, and 67 for Windows Deployment Services.

Service Startup Issue Disabled or No Enabled Devices

The Windows Deployment Services are used for the central distribution of operating systems. Please visit the following link for more information on WDS not referenced here.

Disabled service error

When faced with this error “The Service Startup Issue Disabled or No Enabled Devices because it is disabled“. However, when starting a WDS server, as shown below, please follow the suggested steps. See the following similar error “No valid offer received: WDS PXE-E16 error when booting UEFI and BIOS clients“.

Furthermore, To fix this issue, you must ensure the Windows Deployment Services (services.msc)is started (running).

Note: This is applicable to all windows services regardless of the application.

You may want to see: How to start an application automatically on Mac. Also, see Uninstall WDS: How to remove Windows Deployment Services role via the GUI and PowerShell“.

I hope you found this blog post about addressing the Service Startup Issue Disabled or No Enabled Devices helpful. Please let me know in the comment session if you have any questions.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:WDS, Windows 10

Post navigation

Previous Post: No valid offer received: WDS PXE-E16 error when booting clients
Next Post: How to setup SELinux on a Linux server

Related Posts

  • RDS Error
    RDP Users are unable to change Passwords Windows Server
  • Hyper V VM creation
    How to Create a Windows Server VM on HyperV Windows Server
  • original 1
    DISM “Failed to open image” CWimImageInfo Mount(hr:0x8007000d): Fix Error DISM WIM Provider Windows
  • 1 WeXxkEX0JG3oB781HD8Hrg
    Error 0x204: Unable to Connect to Remote PC [Part 1] Windows Server
  • login keyboard feature
    Sign-In Method Not Allowed: Contact Network Administrator Windows Server
  • nonRDP admin
    Allow RDP access for non administrators: Add User to Remote Desktop Users Group in Active Directory Windows Server

More Related Articles

RDS Error RDP Users are unable to change Passwords Windows Server
Hyper V VM creation How to Create a Windows Server VM on HyperV Windows Server
original 1 DISM “Failed to open image” CWimImageInfo Mount(hr:0x8007000d): Fix Error DISM WIM Provider Windows
1 WeXxkEX0JG3oB781HD8Hrg Error 0x204: Unable to Connect to Remote PC [Part 1] Windows Server
login keyboard feature Sign-In Method Not Allowed: Contact Network Administrator Windows Server
nonRDP admin Allow RDP access for non administrators: Add User to Remote Desktop Users Group in Active Directory Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Basic Cisco Switch Configuration
    Configure a username and secret on a Cisco Switch and Router Network | Monitoring
  • Word Backup Day Veeam Backup Configuration File Saved The Backup Sever
    [World Backup Day] V13 Upgrade Failure: Veeam Configuration Backup Saved the Day Backup
  • BitLocker MBAM Frequently Asked Questions
    Disable the Sleep Mode: UEFI and TPM and BitLocker FAQs Windows
  • image 9
    Fix Error 853: The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid Network | Monitoring
  • veeam
    Install Veeam Backup And Replication With Dedicated SQL Server Backup
  • Screenshot 2022 03 20 at 21.08.50
    How to integrate AWS CodeBuild and AWS CodeCommit to SonarCloud AWS/Azure/OpenShift
  • term “git” was not used as the name of a cmdlet, function, script file, or executable Program recognised
    The term “git” was not used as the name of a cmdlet, function, script file, or executable Program recognized Version Control System
  • scroll
    How to Take a Scrolling Screenshot on Windows 11 Windows

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,801 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.