Experiencing driver installation failures in SCCM new Dell laptops, such as Pro Max 14/16 (MC14250/MC16250) models, when imaging Windows 11 24H2, despite WinPE boot and task sequence running fine.

Question

Experiencing driver installation failures in SCCM new Dell laptops, such as Pro Max 14/16 (MC14250/MC16250) models, when imaging Windows 11 24H2, despite WinPE boot and task sequence running fine.

LL 21

We have been battling trying to solve this at my higher ed for 3 months now. DELL is saying it's an SCCM issue if the device is able to image without issues using a USB-C to boot into WinPE and image it.

Current deployment in SCCM:
Operating system Image: Windows 11 Education 24H2
Driver Package: Dell Pro Max 14 MC14250 - Windows 11 x64 | Dell Pro Max 16 MC16250 - Windows 11 x64
No Network Port Security is activated on the ports we're trying with

We use MSEndpointMgr but have also tried manually injecting the drivers into SCCM too, but both have failed to have the devices image.

We do not have any issues with other DELL model devices. So, far it's isolated to just the DELL Pro Max's. The new DELL Desktop AIO's are imaging without problems. It's just the new laptops but not sure what else to check for on Microsoft side. I could use some help.

5 answers

Your answer

Answer 1

I’ve encountered a similar issue before, and this approach worked for me:

Try installing Windows via USB on one of the affected devices (specific make/model), then allow it to update all drivers from the internet. Once the drivers are fully updated, export them using the following command:

powershell

Export-WindowsDriver -Online -Destination "C:\Drivers"

After exporting, create new driver packages from these files. You might even prepare a dedicated task for this particular model, which can make the process easier. Also, don’t forget to add the network driver to the boot image.

In my case, this method resolved the problem successfully.

Answer 2

Rahul Jindal 11,511

Is this issue with drivers not installing as part of the imaging process? If yes, have you tried using all drivers installation step to allow relevant drivers being picked directly for the driver catalog in SCCM instead of using model specific drivers installation step pack in the TS?

LL 21 Reputation points

2025-08-16T10:04:57.2233333+00:00

Good morning,

Not sure. During the imaging process, after choosing the task sequence to run, while its imaging, the device restarts a few times which is normal. However, with the new DELL laptops, after one of the restarts, it shows the DELL logo with the spinning dots. At this point, it freezes. No logs on the server that's relevant and the device never reaches the OS; so, can't review any logs there. It's just freezes and does not move forward.

So, I'm not sure if its a driver problem or an SCCM issue. I'll check the driver catalog setting you're referencing when I get to the office.

Answer 3

Jessica Montville 0

I am experiencing similar, it doesn't install the audio driver, ethernet, or a usb driver from the driver pack on the pro max 16 MC16250. I am still using MDT, when manually installed the drivers work ok, devices work ok. I am going to try what Rahul offered now.

Answer 4

James Daniels 0

I'm literally seeing the same thing with our Dell Pro 16 Plus PB16250. I injected the network driver and storage drivers into the 24H2 image just to get it to image. The WinPE drivers work great. The normal drivers work with the 23H2 image perfectly. When the task sequence fails in 24H2, it's when it switches over from WinPE to oobe at domain join or . It doesn't seem to be an issue with older models. Same drivers install fine after it is imaged. Something obviously up with these drivers durning oobe just with 24H2.

Sanders, Tim@CDPR 0 Reputation points

2025-12-15T17:44:18.9466667+00:00

James, I'm experiencing this issue too with our Dell Pro Max 14 MC14250s. Did you find a resolution? I don't have any issue on our older Latitude or Precision models.

The logs report a "the step must be running in full OS" when attempting to join the domain prior to Full OS reboot and a "task sequence cannot continue after reboot because task sequence manager is not configured to auto-start or GINA is not installed" after a Full OS reboot.

I've started looking at other things like maybe the OEM key being an issue, but I don't have a solution yet.
Sanders, Tim@CDPR 0 Reputation points

2025-12-17T22:03:31.5166667+00:00

I got our Dell Pro Max 14 MC14250s imaging in our Task Sequence.

First, I used Dell Command to inject the new storage and network drivers into our WinPE boot image. This video from Dell helped with that: https://www.dell.com/support/contents/en-us/videos/videoplayer/updating-boot-images-using-the-dell-command-integration-suite/6371489529112?msockid=206c352b645f675331c0231065136696

Next, I ran Dell Command to download the MC14250-Windows11-A03-731JJ-X01-00-x64 drivers. Absolutely verify that you are getting the right driver package for your device. The new naming conventions for Dell computers can be confusing. For example, there is an "MA14250" variant and a "MC14250" variant, in addition to a "MC14255" variant.

Finally, I copied one of our existing Driver Package MECM commands and updated the WMI Query to "Select * from win32 computersystem where manufacturer like "Dell%" and model like "%14250%". Also updated the Driver Package pointer to the MC14250 driver package I downloaded in the previous step.

Ran the Task Sequence and I didn't have to change my Join Domain command (we're not using the "Apply Network Settings" command).

Answer 5

RobinDay Genn 0

Share via

Experiencing driver installation failures in SCCM new Dell laptops, such as Pro Max 14/16 (MC14250/MC16250) models, when imaging Windows 11 24H2, despite WinPE boot and task sequence running fine.

5 answers

Your answer