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 Reputation points
2025-08-15T20:11:51.8733333+00:00

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.

Microsoft Security | Intune | Configuration Manager | Deployment
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Rahul Jindal 11,501 Reputation points
    2025-08-15T22:18:52.02+00:00

    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?


  2. Jessica Montville 0 Reputation points
    2025-08-21T11:38:22.6066667+00:00

    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.

    0 comments No comments

  3. James Daniels 0 Reputation points
    2025-10-20T20:24:30.7433333+00:00

    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.

    0 comments No comments

  4. RobinDay Genn 0 Reputation points
    2025-10-20T22:30:10.3433333+00:00
    
    
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.