Open PeterDodemont opened 5 years ago
Proposed fix that has been tested and confirmed working. May want to change default from freshest to highest build number but would require additional logic in case no build specific driver packs were found.
I would suggest adding another switch to the script where you can specify OS version. That way you can be sure you get the right version to match the OS version you are installing
It's being redone in the upcoming version that's out very soon.
Hi,
Driver matching seems to pick the latest drivers added rather than the drivers with the highest version number when there are multiple matches. I initially added Surface drivers for 1903 for testing purposes and then added 1803 drivers once initial testing was complete. And now even devices with 1903 are getting the drivers for 1803 installed. See below log where it matches fully with Windows 10 1903 and then later partially with Windows 10 1803. But it then picks 1803 because that package was added after the 1903 package.
EDIT: This is from a driver upgrade within the OS using the "-DeploymentType DriverUpdate" switch.
<![LOG[===== SCConfigMgr Invoke-CMApplyDriverPackage Version 2.2.3 ====]LOG]!>