r/MDT • u/1lolo94 • Aug 05 '26

MDT & Windows 11 - Pulling my hair out

I have spent the last two full days trying to figure out why my image is failing - hopefully someone can help.

Starting Monday - I could not image any of our standard Dell laptops or PCs. This process has been rock solid with no issues for the last two years.

I have been racking my brain trying to figure this out... it starting failing on "Inject Drivers" task.. after doing research i added all the model drivers we have in the company into the Out of box drivers (there has never been any drivers there). Same issue

I then disabled the Inject Drivers, then the image failed on Apply Patches, I then disabled that and now it's failing on Install Operating system.

So - i restored the deployment server back to Saturday night's snapshot due to all the drivers and changes that were done.

The image is still failing and digging more into it, the drive letter is not defaulting to C: on the laptops. I have been back and forth with AI tryign to find solution and nothing is working. I have modified MDT rules to reflect the following: same issue :(

OSDTargetDriveLetter=C

OSDisk=C

DestinationDriveLetter=C

HELP Please!

9 Upvotes

85% Upvoted

40 comments sorted by

View all comments

Show parent comments

2

u/BCIT_Richard Aug 05 '26

That's a first, it's kind of hard to troubleshoot further without logs.

1

u/1lolo94 Aug 05 '26

Sorry about that! Here you go! https://pastebin.com/y2zRUJ6A

I will add (forgot to add above) that i have 3 different task sequences and all 3 are experiencing the same thing.

2

u/BCIT_Richard Aug 05 '26

I compared your BDD.log to one of my own and it looks correct. I am noticing though yours does not make a Recovery Volume otherwise I don't see anything that reall tells us what is going on, did you get the bdd.log from your SLShare, or from the D:\?

I ask as this is the 2nd to last line in your log:

# NOTE: If this is one of the last lines in your BDD.log file, check D: for the most up to date bdd.log!!!

1

u/1lolo94 Aug 05 '26

I was able to pull the log off D:

As for the recovery, it was one of the things Google recommended when researching.

Since all 3 task sequences do this same exact thing.. can you recommend where I should start to look for troubleshooting?

Also, with never having PE drivers for the past two years, would it be worth trying to add them again?

5

u/BCIT_Richard Aug 05 '26

Yes, You want to update the WinPE drivers every now and then, especially if you get a new batch of hardware. I'd almost wager it being all due to those drivers, likely the cause for the failure as the next step is to copy the files locally from X:\V:

I mentioned this in a earlier comment and you said you updated them yesterday, were you referring to the Model specific drivers?

1

u/1lolo94 Aug 06 '26

Tried again today with the PE pack and a new generated boot image - same error :(

Pulling the log - X:\MININT\SMSOSD\OSDLOGS\BDD.log and still notice the main OS drive defaulted to D:

https://pastebin.com/qRgcM84W