Windows Deployment Services (WDS) enables you to deploy Windows operating systems over the network, so you do not have to install the operating system directly from a CD or DVD. This article will discuss how to fix “Wizard.hta Screen stuck during WDS Deployment”. please see MDT deployment failed and Stuck at Command Prompt: Windows installation does not proceed via PXE boot, and How to Fix Windows Stuck on System Restore.
Table of contents
Note: At the time of writing this piece, ADK for Windows 11, version 22H2. The VBScript is not currently working in WinPE, and as such. You cannot perform deployment with it. You have to downgrade if you already installed it.
It is expected to be fixed in an upcoming servicing update. Also, MDT is no longer supported for Windows 11 and Windows Server 2022, but it still works! Please see this link for MDT known issues.
What Triggers the Windows Error 0x800f0823?
The error code 0x800f0823 is one of the most common Windows update errors. It can be caused by various reasons as shown below:
- Missing or corrupt files
- Conflicts with existing software
- Corrupt update components
- Outdated service stack
- Damaged disks
- Corrupt Windows Services
More specifically as it regards my issue, the Windows update error 0x800f0823 means that the Windows Modules Installer in your system is outdated and you need to install/update the Windows Image before installing the PC via WDS.
The Windows Modules Installer Worker which is also referred to as the WMIW, or TiWorker.exe) is a core system process in Windows that checks for the latest Microsoft updates and installs them automatically.
Note: When using Windows Update, it automatically updates Windows Modules Installer or the servicing stack update first, before applying new updates/patches.
Also, see Fix Hyper-V VM Stuck in Stopping State, Windows Deployment Services: How to setup and install WDS role, and how to Fix “Getting Windows Ready” Don’t turn off your computer stuck on Windows.
MDT Log: Further look at Error 0x800f0823
This below was prompted due to the imaging of Windows LTSC from WDS. This might not be for you as it could be a different scenario. Let’s unravel the BDD.log file.
The BDD.log is an aggregated MDT log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file
The following output below can be found in the BDD.log file for the specific deployment.
Deployment Image Servicing and Management tool]LOG]!>Version: 10.0.1xxx1.1]LOG]!>Image Version: 10.0.xxxxx.3xxx]LOG]!>Error: 0x800f0823]LOG]!>The specified package cannot be added to this Windows Image due to a version mismatch. ]LOG]!>Update the Windows image and try the operation again.]LOG]!>
Before running to the resolution, it is worth noting that MDT outputs numerous log types. A clear understanding of these .log files used during an operating system deployment is paramount for resolving MDT/WDS deployment issues.
The MDT log file format is designed to be read by CMTrace. Please see Configuration Manager Tools: How to install and debug logs with the CMTrace Tool. Use this tool whenever possible to read the log files, because it makes finding errors much easier.
Explanation about Wizard.hta Screen stuck
The log is self-explanatory as it reveals that “The specified package cannot be added to this Windows Image due to a version mismatch. Update the Windows image and try the operation again”. This shows that there is a mismatch between the version of the package you are trying to add and the version of the Windows image.
Note: Not all errors in the BDD.log file are relevant as some Task Sequence actions are either skipped via the setting (“Continue on error”) or are just checking errors because optional components are not there/are not being used. An understanding of what is being skipped on error in your environment will be vital in resolving this issue.
Please, see Migrate Microsoft Enterprise Root Certification Authority and Forest Domain Domain to Azure, and Unveiling OOTBI Mini and New Features for v1.7 from Object First.
Resolution
The error message signifies that there is a version mismatch when attempting to add a package that is not compatible with the version of the Windows Image you are working with. Learn more about the LTSC servicing model. Here is a similar fix for error 0x800f0805, run DISM executable (Failure 5627)
Note: Windows LTSC Feature updates are offered in new LTSC releases every 2–3 years instead of every 6 months. Since the LTSC is not updated every month like Windows 10 and Windows 11, you must have thrown in packages or some packages are no longer compatible with the Windows LTSC image.
Here are a few steps you can take to address this issue:
- Check and update the Windows Image Version
- Ensure that the package you are trying to add is compatible with the version of Windows you are using. Otherwise, remove them from the list of packages.
Note: Also download the latest driver from the vendor’s website that might be missing and import them accordingly.
When the above is done, right-click MDT Deployment and choose Update Deployment Share.
Next, select Completely regenerate the boot images. Click Next, and follow through the prompts. Here is an excellent article that discusses WDS, MDT, WinPE and ADk extensively.
When this is done, start your deployment. The the deployment will run smoothly without errors.
I hope you found this article useful on how to fix “Wizard.hta Screen stuck during WDS Deployment” helpful. Please feel free to leave a comment below.
