Share via

BDD_Welcome_ENU.xml error message after initial OS boot.

Ed Reed 6 Reputation points
2022-09-23T15:52:05.25+00:00

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.

244328-mdt-error.png

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.

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
862 questions
Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,923 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 43,071 Reputation points Microsoft Vendor
    2022-09-26T02:43:56.86+00:00

    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.

    1 person found this answer helpful.
  2. Kevin Nguyen 0 Reputation points
    2024-07-18T15:36:41.9866667+00:00

    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.