VWBug5000
commented
2 years ago Same issue here - trying to deploy both Win10 and Win11 and having issues identifying the correct drivers. I have moved all the win11 packages to Pilot so it would no longer impact our imaging needs, but it would be nice to have an updated MDM script to go along with the updated DAT script
Hello,
I have enjoyed using Driver Automation and Modern Driver Management in OSD. I have recently noticed an issue when I downloaded both Windows 10 and Windows 11 drivers using Standard Packages. The Invoke-CMApplyDriverPackage.ps1 (version 4.1.3) stalls during the driver portion of the Task Sequence. I am using
as the parameters.
I looked in the script and saw at about line 936 that there is no entry for builds 19044 (Windows 10 21H2) nor 22000 (Windows 11 21H2). I added these to the script in our package and that solved part of the problem.
We use both Windows 10 and 11 in our environment; so I had downloaded both Windows 10 and Windows 11 packages from Driver Automation Tool. I tried removing just the Windows 11 packages from Configuration Manager to see if they were causing confusion and now the Task Sequence will complete.
This may be caused by both builds having the '21H2' label. So, I think I will be downloading only Windows 10 packages until this has been addressed. Will there be an update for Modern Driver Management that makes it Windows more 11 friendly?
Thank you for your time,
Teri