MDT Failure 5456 - Problem inject drivers

Question

Hello,
I am currently in the process of creating a master for HP x2 210 G2 PC tablets, with Windows 10 21H1 in 64bits.
I installed the latest versions of MDT and ADK.
Management Console 3.0 version 21H1
Microsoft Deployment Toolkit 6.3.8456.1000
MDT (8456) Update KB4564442
ADK 2004

I followed tutorials in French / English to complete this master.
And I end up with 8 errors and 5 warnings.
This crashes after injecting the drivers (see photo).

I don't know where to get the bdd.log and other log files, could you give me the path?

Could you help me unblock these errors?

I had drivers from our previous amster that I got and had the current problem.
I changed and took the drivers directly from the tablet, and I still have this same problem.
And I will try without injecting drivers, do you ever know if that changes anything ...

I despair, help me!

I thank you in advance.
Sincerely, Luciani.

Answer 1

Hi, @Andre Luciani
Thank you for posting in Microsoft Q&A forum.

We can specify the SLShare property in the Customsettings.ini file.
SLSHARE instructs MDT to copy the log files to a server share if something goes wrong during deployment, or when a deployment is successfully completed.
You may refer to the documentation:
https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image#the-customsettingsini-file

Then you may check your BDD.log for more information and do the further troubleshooting.

---

If the response is helpful, please click "Accept Answer" and upvote it.
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.

Answer 2

Hi @AllenLiu-MSFT
Thank you for you response, i have activated the log !

So i post the BDD.log here. 127114-bdd.log .

I specify that I try to format the tablet by usb key. Aaaand the new W10 is too big. So the wim is important. I have retired the version non used. But is still at 4.10GB...
So I had to partition my key with one part in ntfs for data and another in fat32 for uefi boot. The secure boot being disabled on the tablet models that I want to master.

The masterization crashes when injecting the drivers, just after the task to install the OS!

I hope you can helping me.
Sincerely, Luciani.

Answer 3

Bonjour @Andre Luciani ,

I will not trouble you with my terrible French, but I think the first place you should show us is your inject drivers are in the preinstall section. That are will give us more detail about your selection profile and it's used to denote what drivers get installed post-install. Have you specified that ONLY the drivers specific to the device are selected and not the "all drivers" option? In that same area, did you hit the check box to only install matching drivers from the selection profile? That's something I have found will save you some headache as a lot of driver config files for devices not on your system.

Also, in reading your bdd.log, I see it's not finding a drive to install the OS to. It does show that you're setting up drive 0, partition 1 but the drivers can't find where to install the OS and you're still in the install phase according to the log. How do you have the "select the location where you want to apply this OS" configured? That may be where the issue is if you're specifying a specific drive/partition. Try using Logical drive letter stored in a variable (viable is OSDisk) and see if that fixes it.

Let us know if this helps.

Answer 4

Hello @Alex Warren ,
Thanks for the response !

Regarding the injection of drivers in the preinstallation section, everything is done as you indicated. So there shouldn't be a problem.

For the install side of the operating system, I format the single hard drive, first in MBR (if the UEFI variable is FALSE) by assigning it the OSDisk variable, then I format it if the UEFI variable is TRUE by assigning it also the OSDisk variable. Does the fact of having affected twice the reasonable OSDisk generate errors?
Then with what I have read / seen on the internet, I make 4 different partitions boot, MSR, Windows and Recovery, all with variables of different letters of course.

And I have a problem on this tablet model, some times it does not recognize disk0 and does nothing. I have to add a task sequence to say to do the same on disk1.
Would there be a way with conditions to tell mdt to format disk0 if it exists and ignore it if it does not exist and go to the next task which will format disk1 if it exists and s 'there is no ignore the order to format it ...
Hope I managed to explain it clearly ^^

I completely dry up on these errors, and I can't read the bdd.log file well ...

Thank you for your help !

Answer 5

Hi @Alex Warren ,
I have already this option. So i don't know ...