Skip to content

TechDirectArchive

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

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

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

Posted on 28/01/202108/09/2024 IT Expert By IT Expert 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

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.

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.

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

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.

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

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.

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

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.

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.

This will start the WDS configuration as shown below.

“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.

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

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

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.

5/5 - (1 vote)

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: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

  • Slide1 1
    How to manage Microsoft Defender Antivirus using Group Policy and Command Line Utility Anti-Virus Solution
  • fgh
    Configure log on as a batch job permissions on any server Windows Server
  • BitLocker
    Hide Default BitLocker Drive Encryption item in Windows Windows Server
  • trrdf
    Remote Desktop cannot find the computer this in the specified network: Verify the computer name and domain that you are trying to connect Windows Server
  • How to Check what files are taking up space
    WinDirStat: Check what files are taking up space on Windows Windows
  • original 1
    Install Wim: How to Add Packages to Windows image Using the DISM Tool Windows Server

More Related Articles

Slide1 1 How to manage Microsoft Defender Antivirus using Group Policy and Command Line Utility Anti-Virus Solution
fgh Configure log on as a batch job permissions on any server Windows Server
BitLocker Hide Default BitLocker Drive Encryption item in Windows Windows Server
trrdf Remote Desktop cannot find the computer this in the specified network: Verify the computer name and domain that you are trying to connect Windows Server
How to Check what files are taking up space WinDirStat: Check what files are taking up space on Windows Windows
original 1 Install Wim: How to Add Packages to Windows image Using the DISM Tool 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

  • VMware Tools
    How to upgrade VMware Tools in vSphere Virtualization
  • UpdateOfficeOnlineServer 1
    Perform Office Online Server Update via Windows Updates Windows Server
  • How to Enable and use Sudo in Windows 11
    How to Enable and use Sudo in Windows 11 Windows
  • Veeam Virtual Appliance for Backup and Restore
    How to setup Veeam Software Appliance v13 Backup
  • Veeam Enterprise Manager setup
    Veeam Enterprise Manager setup and User Role management Backup
  • How to enable or disable Microsoft Defender Antivirus Active or Mode Mode
    Set Microsoft Defender Antivirus to Passive or Active Mode Anti-Virus Solution
  • images
    AWS Network Adapter: Redhat to Citrix PV and AWS PV Driver AWS/Azure/OpenShift
  • SQL Error
    Fix “the server was not found or was not accessible: Verify that the instance name is correct and that SQL Server is configured to allow remote connections” Oracle/MSSQL/MySQL

Subscribe to Blog via Email

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

Join 1,780 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

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.