This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EER%3C/text%3E%3C/svg%3E)
Getting an error during MDT deployment. The error occurs right after the OS installs and the deployed machine boots for the first time. A dialog box appears that says,
"Unable to find definition file:BDD_Welcome_ENU.xml
Commandline : "C:\MININT\Scripts\Wizard.hta" /definition:BDD_Welcome_ENU.xml.
The definition file mentioned is located on the deployment share of the server. At this point in the deployment, the machine is supposed to map a Z: drive to the server's deployment share to read the file from but the Z: drive doesn't get mapped. For this reason, it was initially suspected that this was a driver problem but the correct NIC driver is installed in the OS at the time of the error.
The system has been working well for months and now it's failing 50% of the time. Originally the errors were only affecting new Dell Optiplex and Latitude machines and now older model HP and Lenovo machines are seeing the issue.
Hi, @Ed Reed
Thank you for posting in Microsoft Q&A forum.
It looks like a random issue, have we checked BDD.log to see if there any useful error message?
We may try to restart the MDT server to see if it helps?
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
It doesn't feel random to us, considering it happens so often. We generally perform ~50 deployments a week and this is happening about 50% of the time. We have 5 WDS servers throughout the organization with DFS-R and DNS failover. The problem isn't specific to one server, it has happened on all of them at different amounts. It doesn't seem to be specific to any model of machine either. We only perform new OS deployments and we don't capture machine images. I've restarted all the servers and am waiting for a technician to forward me a log the next time they have a failure.
As I said before, the system was working fine for many, many months. This is something new.
Here's some interesting lines from the BDD.log
FindFile: The file x86\Microsoft.BDD.Utility.dll could not be found in any standard locations. ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 1 ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
RUN: regsvr32.exe /s "" ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
FindFile: The file x64\Microsoft.BDD.Utility.dll could not be found in any standard locations. ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 1 ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
RUN: regsvr32.exe /s "" ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object ZTIGather 9/26/2022 10:30:50 AM 0 (0x0000)
i did apply the KB4564442 update to all the servers recently. Originally I only applied it to one of the servers, the one that I always built the boot image from. As a clean up task I went ahead and applied it to all of them. I don't see how this could have an effect though since the reason this file can't be found is because the Z: drive isn't being mapped as it's supposed to.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 49%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKN%3C/text%3E%3C/svg%3E)
This is a very absurd issue. My organization also begin to see it as we are imaging new out-of-the-box laptops. It does not happen to the computers that we are already imaged before and need to be re-imaged again for redeployment. We find that for the Out-of-the-box computers, if you do a Secure Wipe on the drive in BIOS, it will mitigate the issue. We have tried adding step in the Task Sequence to do a diskpart clean on the drive but doesn't fix it.
So far, our solution is to do a BIOS Secure Wipe on the drive for Out-of-the-box computers, before we image them.
Hope this help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 38%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
I'm experiencing a similar issue except only toward the end of the deployment process with Summary_Definition_ENU.xml. This has only occurred since I changed our OS from Win10 > Win11.. Did you use a method to programmatically secure erase? I believe the process is typically manufacturer specific and often an option in BIOS/UEFI, but I'm wondering if it can be accomplished in a task sequence step.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 17%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBL%3C/text%3E%3C/svg%3E)
Hi.. we have the same issue.. what I found is there a new BIOS firmware been sent out to all manufacturers (HP, Lenovo, Dell etc) and this cause the MDT to fail.. If you update this file and added the missing file that the MDT needs to transfer to the C: drive after it format the HDD (as it's not related to map the network drive).. LTICopySCripts.wsf.. it should help the issue. At this moment im testing it.. maybe it will help someone to figure why it doesn't grab the Skip Welcome attribute.
I added -> "BDD_Welcome_ENU.xml","WelcomeWiz_Initialize.xml","WelcomeWiz_DeployRoot.xml"
Private Sub Class_Initialize
' Create a list of scripts to copy.
ScriptsToCopy = Array("LiteTouch.wsf", "ZTIUtility.vbs", "ZTIGather.wsf", "ZTIGather.xml", _
"Wizard.hta", "Credentials_ENU.xml", "Credentials_scripts.vbs", "WizUtility.vbs", "Wizard.css", _
"Wizard.ico", "BackButton.jpg", "plusicon.gif", "minusico.gif", "DeployWiz_Definition_ENU.xml", _
"DeployWiz_Initialization.vbs", "DeployWiz_Validation.vbs", "Summary_Definition_ENU.xml","WelcomeWiz_DeployRoot.xml", _
"Summary_scripts.vbs", "LTICleanup.wsf", "LTIGetFolder.wsf", "ZTINICConfig.wsf","WelcomeWiz_Choice.xml",_
"ZTINICUtility.vbs","ZTIBCDUTILITY.VBS", "ZTIDataAccess.vbs", "BDD_Welcome_ENU.xml","WelcomeWiz_Initialize.xml", "LTISuspend.wsf", _
"ZTIDiskUtility.vbs", "ZTIRunCommandHidden.wsf", "header-image.png", "NavBar.png", "Computer.png", _
"SetupComplete.cmd", "SetupRollback.cmd", "ZTISetupRollback.wsf", "LTITriggerUpgradeFailure.wsf", "LTIBootstrap.vbs")
SourcePath = oUtility.ScriptDir & "\"
TargetPath = oUtility.LocalRootPath & "\Scripts\"