Open sveken opened 2 years ago
I was hoping we could do that as well. Many vendors don't provide drivers specifically for Windows 11 yet. More often than not drivers for Windows 10 20H2+ are fine though.
So i can't find the issue that this was suggested, but to get around this currently i have the following, It only runs when win 11 drivers cannot be found.
_SMSTSLastActionSucceeded
the same goes for the inverse situation for instance latest dell models just have w11 driver packs... and w10 22h2 just came out...
So i can't find the issue that this was suggested, but to get around this currently i have the following, It only runs when win 11 drivers cannot be found.
_SMSTSLastActionSucceeded
Hi @sveken , would you be so kind to share your command? Tried to make it work for us as well, but it doesn't install any drivers then if Windows 11 drivers are not available.
Thanks!
Hello I've been using the "_SMSTSLastActionSucceeded" for OSD, but now i need to use it for a driverupdate deployment.
The problem is that it uses the actual OS build to validate if the build exists as a package. So when you specify "Windows 10", it can't find the W11 build within W10 builds and crashes. For now i need to duplicate driver packages with Windows 11 in the text. I'll try to code around it and find a way to make it work, OSFallback maybe.
@danielbessler The command is the same one used in my Windows 10 Step. Just reuse your windows 10 step and only run it if the windows 11 one fails.
@sveken I tried it but it failed. I currently tried all possible combinations. May you can share your parameter, without the -Endpoint details
First: -BareMetal -Endpoint 'xxxxxxxxxxxxxx' -TargetOSName 'Windows 11' -TargetOSVersion '22H2' Second: -BareMetal -Endpoint 'xxxxxxxxxxx' -TargetOSName 'Windows 10' -TargetOSVersion '22H2' (which has the Variable set)
On the Windows 11 one on the options tab make sure to click continue on error, then it will go properly to the windows 10 one otherwise it will just end on the 11 with the error.
Is there a fallback option for TargetOSName? ie if no windows 11 drivers are found attempt the windows 10 drivers, Like what -OSVersionFallback does?
Thanks