Skip to content

TechDirectArchive

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

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

An error occurred while trying to start the Windows deployment services error 0x906

Posted on 28/01/202130/08/2026 Christian By Christian No Comments on An error occurred while trying to start the Windows deployment services error 0x906
  1. Home
  2. Windows Server
  3. An error occurred while trying to start the Windows deployment services error 0x906
Graphic depicting multiple devices including computers and mobile phones connected with gears, representing Windows Deployment Services.

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). In this article, we shall discuss the steps to fix “An error occurred while trying to start the Windows deployment services error 0x906”. Please see the differences between MDT and WDS, and how to deploy images to computers or virtual machines using WDS.

The purpose of WDS is to remotely deploy the Windows operating system. WDS uses a PXE method for booting clients. 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 compliant.

See this guide on how to set up and install the WDS role, how to configure Windows Deployment Services on Windows Server 2019, and how to configure DHCP Server option 60, 66, and 67 for Windows Deployment Services.

Why was Windows deployment services error 0x906 prompted?

You have recently set up the WDS server role as described only.

When you try to start the WDS service, you will be prompted with the following error “An error occurred while trying to start the Windows deployment services error information 0x906” as shown below.

Screenshot of the Event Viewer showing a Windows Deployment Services error. An error occurred while trying to start the WDS server, with Error Information: 0x906.

Even when you try to restart the WDS from the services.msc console, you will NEVER be able to start the service.

This is because the Windows deployment server has not been configured.

Screenshot of the 'Services' window in Windows, focusing on the 'Windows Deployment Services Server' entry, showing options to start and access properties.

Solution

To fix this, we will have to configure Windows Deployment Services. Kindly follow the steps discussed below.

There are various ways to get to the WDS snap-in console. Open the WDS snap-in console by launching the Server Manager. Click on Tools and then select Windows Deployment Services.

Alternatively, click on WDS as shown below, on the available server, right click and select Windows Deployment Services Management Console
Screenshot of Windows Server Manager 2019 showing the WDS (Windows Deployment Services) section with options for server management and features.

This will launch the Windows Deployment Services console as shown below. As you can see the server is currently not configured.

Configure WDS Server

To have the server configured, right-click on the server name (in my case, TechDarchive.techdirect.local). Click on configure the server.

Screenshot of Windows Deployment Services interface showing 'TechDArchiveDC.Techdirectarchive.local' selected with an arrow pointing to 'Configure Server' option.

This will open up the Windows Deployment Services Configuration Wizard as shown below. Read and ensure you are complying with the requirements to setup WDS. Click on Next

Screenshot of the Windows Deployment Services Configuration Wizard displaying prerequisites for setup, including the need for an Active Directory domain, a DHCP server, a DNS server, and an NTFS file system partition. An arrow points to the 'Next' button.

Integrate with Active Directory

Click on next to continue. On the Install Options page, verify that you choose  Integrated with Active Directory and then click Next.

Screenshot of the Windows Deployment Services Configuration Wizard, displaying the Install Options section with radio buttons for 'Integrated with Active Directory' and 'Standalone server'. An arrow points to the 'Integrated with Active Directory' option, and a button labeled 'Next' is highlighted.

Click on Next. On the Remote Installation Folder Location page, you can accept the default location which is C:\RemoteInstall and then click Next

Windows Deployment Services Configuration Wizard showing the Remote Installation Folder Location setup with an input field for the path 'C:\RemoteInstall', along with 'Browse' and navigation buttons for proceeding to the next step.

Note: If you do not want to have your boot images, install and PXE boot files etc saved to this location, click on browse and select your desired location. 

Since this is in a test environment, I will leave it this way. Ensure you select a different partition for a production environment.

Click on Next. This will prompt the “System Volume Warning dialog window”, and click Yes.

Screenshot of the Windows Deployment Services Configuration Wizard showing the remote installation folder location. A warning message indicates that the selected volume is the Windows system volume, advising to use a separate volume for best performance.
Usually, if you have a DHCP server server, you will be prompted to configure the Proxy DHCP Server. But we currently do not have a DHCP server set up in this LAB.

Next, you will be prompted to configure the PXE Server Initial Settings. On the PXE Server Initial Settings window.

Click Respond to all client computers (known and unknown), and click on Next, please wait for a few seconds for the process to complete.

Screenshot of the Windows Deployment Services Configuration Wizard showing PXE Server Initial Settings. Options to respond to client computers are displayed, with the 'Respond to all client computers (known and unknown)' option selected and an arrow pointing to it. A 'Next' button is also visible.

This will start the WDS configuration as shown below.

Windows Deployment Services Configuration Wizard displaying task progress with a green progress bar indicating the configuration of Windows Deployment Services is starting.

“Remember to uncheck the “Add Image” to the server now if this is currently not what you want to do. When complete, click on Finish.

Windows Deployment Services Configuration Wizard completion screen, displaying options to add images to the server and a 'Finish' button.

From the first image below, the start button is grayed out because the service is currently running. Also

Screenshot of Windows Deployment Services console showing a menu with the option to 'Start' a server under 'All Tasks'.

That is all that is needed to configure WDS and have the service running as shown below.

Screenshot of Windows PowerShell ISE displaying a command and its output showing the status of the WDSServer service as 'Running'.

I hope you found this blog post on how to fix “An error occurred while trying to start the Windows deployment services error 0x906” helpful. If you have any questions, please let me know in the comment session.

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
Windows Server Tags:Microsoft Windows, WDS, WDSUTIL, Windows 10, Windows 11, Windows Deployment Services, Windows Server 2016

Post navigation

Previous Post: Cannot open Bluetooth preference pane because it is not available
Next Post: How to Install and configure Active Directory Certificate Services

Related Posts

  • DC 3
    How to demote and remove a Domain Controller on Windows Servers Windows Server
  • create a two way Active Directory Trust
    How to create a two-way Active Directory Trust Windows Server
  • maxresdefault
    The following errors occurred attempting to join the domain: The specified domain either does not exist or could not be contacted Windows Server
  • unnamed 1
    NSlookup Displays Error: UnKnown Default Server Windows Server
  • How to upgrade domain controllers e1775563888303
    Build a New DC vs Swing Migration: Upgrade Server OS Correctly Windows Server
  • Object Firt OOTBI offline and online cluster update
    Offline and Online Update for Object First Out-of-the-Box Cluster Windows Server

More Related Articles

DC 3 How to demote and remove a Domain Controller on Windows Servers Windows Server
create a two way Active Directory Trust How to create a two-way Active Directory Trust Windows Server
maxresdefault The following errors occurred attempting to join the domain: The specified domain either does not exist or could not be contacted Windows Server
unnamed 1 NSlookup Displays Error: UnKnown Default Server Windows Server
How to upgrade domain controllers e1775563888303 Build a New DC vs Swing Migration: Upgrade Server OS Correctly Windows Server
Object Firt OOTBI offline and online cluster update Offline and Online Update for Object First Out-of-the-Box Cluster Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

veeaam100

Veeam Vanguard

  • VMware and HyperV are not compatible
    How to fix VMware and HyperV are not compatible Virtualization
  • ubuntu 1479782 1280
    Ubuntu Linux post installation of Network Properties, Guest Integration and Web Administration using Cockpit Linux
  • Fix failed to connect to the backup serve
    Fix failed to connect to the backup server: Make sure it is online Backup
  • Different Class IP Address
    Classes of IP Address: Understanding IP Address Classification Network | Monitoring
  • Convert PEM to PPK 1
    Convert a PEM Key to a PPK Key on a Linux and Windows AWS/Azure/OpenShift
  • MDt
    Failure 5456: Unable to determine destination disk, partition, and/or drive, see BDD Log Windows
  • SSU
    What to know about the servicing stack update and latest cumulative update in Windows Network | Monitoring
  • Azure logo 1
    Azure Active Directory: Why do I need to deploy Azure AD? AWS/Azure/OpenShift

Subscribe to Blog via Email

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

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

Tags

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

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.