logo logo

The next-generation blog, news, and magazine theme for you to start sharing your stories today!

The Blogzine

Save on Premium Membership

Get the insights report trusted by experts around the globe. Become a Member Today!

View pricing plans

New York, USA (HQ)

750 Sing Sing Rd, Horseheads, NY, 14845

Call: 469-537-2410 (Toll-free)

hello@blogzine.com

Troubleshooting Windows Deployment Services Error 0xc0000023

avatar
Louis Ferguson

An editor at Blogzine


  • 🕑 3 minutes read
  • 27 Views
Troubleshooting Windows Deployment Services Error 0xc0000023

If you encounter the message Windows Deployment Services encountered an error 0xc0000023 while deploying an ISO image, this article will guide you in resolving the problem. First, let’s explore the underlying causes of this error.

Windows deployment services encountered an error 0xc0000023

Causes of Windows Deployment Services Error 0xc0000023

The error can be triggered by various issues, both on the server and client sides, as outlined below:

  • Corrupted Boot File: The Windows Image File (WIM) contains the OS image along with other critical components for booting and OS installation, typically stored in the boot.wim file. A corrupted boot.wim can lead to this error during remote installation when the WDS Server transfers this file to the target system.
  • Improper OS Image Capture: Failure to capture the OS image correctly can result in a corrupted or incomplete WIM file, causing deployment issues during the boot process.
  • Hardware Compatibility Issues: Incompatible hardware or outdated/corrupted device drivers on the target system can create conflicts, resulting in a boot failure that triggers the error.
  • Problems with WDS Configuration: Sometimes the WDS server may fail to locate or transfer the WMI file to the target system due to incorrect network settings, firewall restrictions, or other configuration issues.

How to Fix Windows Deployment Services Error 0xc0000023

Windows deployment services encountered an error 0xc0000023

You can follow the solutions outlined below to fix this issue:

  1. Verify the WDS boot file for errors
  2. Recapture the OS Image
  3. Check Hardware Compatibility
  4. Update and Reconfigure the WDS Server

1] Verify the WDS Boot File for Errors

Since the error suggests a potential corruption in the boot image file, the troubleshooting process should start with checking the boot.wim file. You can use the System File Checker and DISM tool to identify and rectify any errors in the following manner:

  • Open the Windows Terminal on the WDS server by typing cmd in the Desktop Search Bar.
  • Run the Terminal as an administrator, and execute the following command to initiate the System File Checker:

sfc /scannow

  • After completion, run the DISM tool with the command:

dism /checkHealth /image:C:\wim\boot.wim

  • If errors are detected, you can fix them by entering:

dism /repairImage /image:C:\wim\boot.wim

2] Recapture OS Image

  • Launch the WDS Server Manager and expand it by double-clicking on the server name.
  • Click on Boot Images in the left pane to view boot image file details on the right.
  • Right-click on the image and select Create Capture Image to start the image capture process.
Boot Image Option Wds Console
  • On the following screen, provide an Image Name, Description, and the path for saving the image file.
Wds Os Image Capture Details Enter
  • Click Next and wait until the image creation process is finished.
  • Upon completion, check the box next to Add Image to the Windows Deployment Server Now, and click Finish to finalize the recapture.
Win Image Creation Finishing Step

3] Check Hardware Compatibility

It’s essential to verify that the target system meets the minimum hardware requirements to avoid errors during deployment.

4] Reconfigure and Update the WDS Server

Reconfiguring the WDS Server as described below can prevent configuration-related errors:

  • Open the WDS Server Manager and right-click on the Server Name.
  • Select the Configure Server option and click Next.
Wds Console Configure Server Option
  • Select Integrated with Active Directory Domain if applicable, or choose Standalone Server, then click Next.
Wds Server Install Options
  • Specify the path for storing all Windows images and click Next.
Wds Remote Installation Location Path Selection
  • Choose the option Respond to all client computers (Known and Unknown) to proceed.
Wds Config Client Response Option
  • Select Add Images to the server now to include the newly captured image, and click Finish to complete the configuration. To add the image, refer back to the Recapture OS Image section.
Wds Server Config Final Step

Additionally, check for any pending updates to ensure compatibility with the latest Windows versions.

What is Windows Deployment Service?

Windows Deployment Service, or WDS, is a server-based tool provided by Windows that facilitates the installation and configuration of the OS on systems over a network. It allows simultaneous installations on multiple systems without the need for physical media. WDS operates in conjunction with the Pre-boot Execution Environment (PXE) to load a lightweight version of Windows, known as Windows Pre-execution Environment (Windows PE), on the target machine to perform the installation. WDS manages both network boot images and the actual OS images intended for remote installations.

Where Are Windows Deployment Services Boot Images Stored?

For 64-bit boot images in Windows Deployment Services (WDS), the boot images are located at <RemoteInstall>\Boot\x64\Images. If needed, the storage location can be modified using Microsoft Configuration Manager.

Source



Leave a Reply

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