If that’s the case, it’s time to add the drivers of the new computer model to the MDT system. Ideally, you will need two sets of drivers for that new device, one for the WinPE bootable drive and one for regular deployment.

Download these drivers from the official website first and then import them to the MDT system under the Out-of-Box Drivers section. You can create separate folders to better manage different types of drivers.

To update the bootable LiteTouch ISO image, right-click the Deployment Share and choose Update Deployment Share.

And choose the Completely regenerate the boot image option. It may take a while to get all drivers updated in the boot image.

Lastly, make sure you have the Inject Drivers step in the Task Sequence when deploying a new computer.

Installation failed with error code 0xC190010E

This indicates that the setup.exe needs the /eula accept parameter to accept the license agreement.

The fix is quite simple, add a Set Task Sequence Variable task sequence with the following variable and value in the Preparetion stage.

Task Sequence Variable: WindowsUpgradeAdditionalOptions
Value: /eula accept

Installation failed with error code 0xC190010E

This indicates that the hardware doesn’t meet the minimum requirement of Windows 11, whether it’s an early version of TPM or an older generation of CPU processor.

The fix is also simple, to add a registry key named AllowUpgradesWithUnsupportedTPMOrCPU in HKLM\SYSTEM\Setup\MoSetup before the actual upgrade to tell the installation process to bypass the hardware requirement check.

To accomplish that, add a Run Command Line to add this registry key in the Preparation stage.

reg.exe add "HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup" /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1 /f

1. Download Windows 10/11 ISO image

Download and run the Windows 10 Media Creation Tool to create the installation media in ISO format.

2. Extract files

Right-click the ISO file we just downloaded, and choose Mount to mount the image into a local drive.

Now let’s make a copy of the mounted drive to a folder. For me, I copied the whole drive into a Software folder on my computer.

3. Create install.wim from install.esd

Open an elevated Command Prompt window and run the DISM command to locate the right image to convert first.

DISM /Get-WimInfo /WimFile:sources\install.esd

Since I am preparing for the Pro version, index 6 is what I needed. Now run the following to create the install.wim file.

DISM /Export-Image /SourceImageFile:sources\install.esd /SourceIndex:6 /DestinationImageFile:sources\install.wim /compress:max /CheckIntegrity

This created the install.wim file in the same folder as install.esd.

4. MDT Setup 1 – Add Image

Now let’s open Deployment Workbench (MDT Console), right-click Operating System and choose Import Operating System.

Select the entire image folder that contains the install.wim file we just managed to create. Check the Move the files option if needed.

Given a unique name for the image, and done for the import.

That’s it. Now you can either create a new task sequence that uses the newly created image or modify an existing one.

Turns out, just preparing the new image.wim file for Windows 10 21H2 wasn’t enough. You will have to upgrade the Windows ADK along with a new set of PE add-ons as well.

Here is how to proceed.

Go to the Windows ADK download page, and download both ADK for Windows 10, version 2004, and Windows PE add-on for the ADK. If you already have version 2004 of ADK installed, make sure you have the PE add-on updated.

Then, uninstall the old version of Windows ADK and Windows PE add-ons and then install the new version you just downloaded above.

Once installed, open Deployment Workbench, right-click DeploymentShare, and choose Update Deployment Share.

Select option “Complete regenerate the boot image”, and click Next.

Once it’s finished, you can go to the DeploymentShare\Boot folder and use tools like Rufus to create a new bootable USB drive using the LiteTouchPE_x64.iso image.

A quick note, you could use Windows 11 ADK as well since it’s now also available. But I was having difficulty using the bootable USB to boot and launch the deployment wizard using Windows 11 PE version for some reason. Windows 10 ADK 2004 works for me now so I will just leave it like that since I have no plan to deploy any Windows 11 installs.

A quick Google search tells me that this is something to do with UEFI boot. It makes sense since it’s an old box. So, I created another sequence that only formats and prepares the disk for BIOS legacy boot and also applied the hotfix that fixes the issues with BIOS type firmware. But no luck, the deployment still fails right after the OS installation phase.

Guess what, to be able to deploy a Windows 10 installation on an old computer that doesn’t have the UEFI boot option, I will have to prepare a USB bootable disk with the BIOS boot option and boot from it.

Once I boot from it, it went through without any further errors.

TPM Password missing. Please provide Password via TpmOwnerPassword or AdminPassword

Since none of the password is present in the sequence or the configuration file, the encryption wasn’t going through.

So where to put the these passwords so that the deploy sequence can go through without the problem?

In MDT’s DeploymentWorkbench, right-click the Deployment Share you have, and choose Properties.

Switch to Rules tab and add the following line under [Default] section.

TpmOwnerPassword=passphase

Click OK to save the setting, which saves the change to CustomSettings.ini file under Control folder in MDT deployment share folder.

Now try again and the encryption should go through.

Behind the scene, the TpmOwnerPassword is used during the TPM initialization process for encryption. However, since retaining ownership password is no longer a safe measure in BitLocker, it will be set to a random value in the latest Windows 10 builds. So, it seems that the TpmOwnerPassword is obsolete and no longer used. However, if it still prevents you from enabling BitLocker during the deployment, hope this one helps.

The preliminary thought is that it might be missing some drivers as out of the box, the MDT WinPE bootable drive doesn’t recognize the network adapter and I had to use a USB-network adapter to connect to the network.

Skipping the Inject-Driver step didn’t help, nor loading them all during the installation.

So, how can I prepare a WinPE bootable drive that recognize the on-board network adapter right away?

Here is a quick run-down of the steps that update the bootable WinPE disk that eventually solved my problem.

First, download the latest driver from the manufactory’s website.

Then, create a subfolder under Out-of-Box Drivers, let’s call it Lenovo M920.

Right-click the folder’s name and choose Import Drivers.

Specify the directory that contains all the drivers you want to import and click Next.

Once done, right-click MDT Deployment and choose Update Deployment Share.

Select Completely regenerate the boot images, and click Next.

It may take a while to regenerate all the boot images. Once done, you can re-make the bootable USB drive from DeploymentShare\Boot folder.

And now use the new generated bootable disk and it will pass through the Wizard.hta screen like wind.

Note that if you have a large amount of computers from various vendors with different models, you may consider using profiles and/or groups to separate the bootable drive and drivers.