OSVersionFallback not working on Custom Package

[Fearless-Fish]

Hi,

I'm really scratching my head with this one. I'm just testing this solution at the moment, and was able to go through the full process successfully with a HP Z440. I created a 20H2 driver pack and installed it with TargetOSVersion being 20H2. I then changed TargetOSVersion to be 21H2 and used the -OSVersionFallback switch, and again it successfully installed the 20H2 driver pack as expected.

I then created a custom package for a Lenovo device. Initially I made it as just "Windows 10 x64" (without a build being specified) as that's how it appeared when I downloaded it from the Lenovo site. This didn't work with or without the -OSVersionFallback switch. I then used the Driver Automation Tool to convert this from "Windows 10 x64" to "Windows 10 20H2 x64" in case the -OSVersionFallback switch still required a specific build to fall back to. But this still doesn't work.

The logs appear to indicate it can't match the OS, but other than that I have no real idea of how to progress as everything seems right. I've attached a log - one for when the driver pack was just "Windows 10" and one for when it was "Windows 10 20H2".

Hope you can help :)

Thanks
FF

P.S. the only slight difference I can see is that the Lenovo package seems to have a double space in it in between 20H2 and x64, whereas the other packages seem to only have a single space (see screenshot). Not sure why, or whether that would make a difference

ApplyDriverPackage-Windows10.log
ApplyDriverPackage-Windows10-20H2.log
.