This change was actually made some time ago to support a specific scenario but never made it here on GitHub.
The scenario is for a prestaged OSD Task Sequence, where the packages for driver content are already on the local disk. OSDDownloadContent.exe doesn't check for prestaged content, nor does the invoke-CMApplyDriverPackage script.
Further details are in the version history section of the script.
The intention is to also update version 3+ of the script.
This change was actually made some time ago to support a specific scenario but never made it here on GitHub. The scenario is for a prestaged OSD Task Sequence, where the packages for driver content are already on the local disk. OSDDownloadContent.exe doesn't check for prestaged content, nor does the invoke-CMApplyDriverPackage script.
Further details are in the version history section of the script.
The intention is to also update version 3+ of the script.