In this article, we shall discuss the steps to fix “‘WDS server unable to start with Error Information 0xFFFFFDF0”. The error code 0xFFFFFDF0 serves as a key piece of information when troubleshooting. Identifying the specific error code is essential in understanding and resolving issues. Further investigation and analysis are recommended to unveil the underlying cause and implement the appropriate solutions. here is a similar error ‘An error occurred while trying to start the Windows deployment services error 0x906“
Also, see how to Uninstall WDS: How to remove Windows Deployment Services role via the GUI and PowerShell, What are the differences between MDT and WDS? and Windows Deployment Services: How to setup and install WDS role.
Review WDS-related Logs
With this in mind, let us dive into the Windows Event Viewer. Navigate to the “Windows Logs” and check both “Application” and “System” logs for any WDS-related errors or warnings
As you can see below, we have got some errors. The first error states “An error occurred while trying to initialize provider WDSMDMGR and the deployment services server will be shut down with the error code 0xFFFFFDF0
Exploring another event, we can see the details “An error occurred and the deployment services server will be shut down”
Please, see Integrate Ac, tive Directory with IPMI for Out-of-Band Management, and Migrate Microsoft Enterprise Root Certification Authority and Forest Domain to Azure.
Why was the error prompted?
The error code 0xFFFFFDF0 when associated with Windows Deployment Services (WDS) indicates an issue with the Windows Deployment Services server database. We already know that the WDS service is installed but not running.
I already know why this error was prompted. Therefore, I will go straight to the solution and suggest what you could do if the issue is prompted in your environment and you are having a different issue scenario (use-case).
Here is how to fix “MDT Warning: Unable to set working directory, the application returned an unexpected code 2, and how to fix “Failure 5456: Unable to determine destination disk, partition, and/or drive, see BDD Log“.
Fix WDS server unable to start with Error Information 0xFFFFFDF0
As mentioned above, I recently migrated WDS and MDT to a new Windows Server. As you can see, the WDS service did not respond to the start or control request in a timely fashion.
This is because the RemoteInstall folder files were not correctly copied to the new server. Due to the missing files, WDS could not start. I do not need to repair the WDS database.
Note: to fix this, stop the wds service on the parent WDS server which you wish to decommision WDS and recopy the RemoteInstall folder to the new WDS server
I will just recopy the RemoteInstall files from the old server to the new location. As you can see from the image below, I will replace the files in the new destination server.
When the copy job is complete, you can easily compare the emoteInstall File size on both servers. When this is done, you should be able to start your WDS server.
Let”s review the WDS log once again, we can see that the WDS server has started successfully.
Please, see “Install Windows Deployment Services on Windows Server 2022, and How to create a backup job for Proxmox VMs using VBR.
Alternative solution: Verify WDS Database Integrity
To check and repair the WDS database, follow the steps below. Open a Command Prompt with administrative privileges. At the command prompt, type and then press ENTER.
wdsutil /uninitialize-server To reinitialize the WDS service, type the below at a command prompt, and then press ENTER.
wdsutil /initialize-server /reminst:{RemoteInstallFolder} wdsutil /initialize-server /REMINST:<path_to_remote_install_folder>Conclusion
As a last resort, you may consider uninstalling and then reinstalling the WDS server role. This should be done carefully to avoid data loss or unintended consequences.
Remember to back up any critical data and configurations before making significant changes to your WDS server. If the issue persists, review specific error messages in the logs from the Windows Event Viewer.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.
