Open swoonhusker1 opened 1 year ago
It appears that driver might already be installed and is falsely returned by LSUClient as an available update.
If you have Lenovo System Update installed too, does it show the same driver as an available update or no?
When I check Lenovo system update it does not show any available updates. Sorry I didn't include that before
Thanks, so the cause for the driver showing up again is in here:
The first _Driver test fails because the device PCI\VEN_8086&DEV_467D
doesn't use this driver. It's one of three device IDs Lenovo tests for and the other two do pass the test.
Currently I require all hardware IDs listed in a _Driver test to pass which is why this package comes back as not installed yet. I'm going to have to take some time to look into this case and if the behavior can be tweaked to match System Update but without regressing on another end.
Okay, thanks for looking at it Jantari.
I have run some comparisons of the results when passing _Driver tests if just one found device passes the test vs all like it is currently. Most of the time it does not make a difference but I found a system where it did:
This is also an Intel Chipset Driver package but a different one. This was on a Lenovo 20FN (T460). In this example I don't think the IsInstalled test should've passed. The package version is 10.1.5.2 which is clearly an update to the 10.1.1.9 used by the first device, and the Synaptics driver being used for an Intel device feels more like another problem than intentional.
But, another idea is that System Update might be failing what it considers inbox drivers. The current driver version in your log is 10.0.19041.1202
which is most likely a windows inbox driver as it corresponds to a Windows version. I can do some more tests around that.
Version
1.5.3
Computer Model
21CES50100
Problem
Running a get-lsupdate finds the following: n3aic04w "Intel Chipset Device Software - 10 (20H2 or Later)/11 (21H2 or Later)" 9/19/22 release date
When installing the failure reason is INSTALLER_EXITCODE
I'm attaching logs of the get-lsupdate -verbose -debug and also install-lsupdate. install-lsupdate debug.log get-lsupdate debug.log
Additional context
No response