Get-LSUpdate finds updates even though none are available.

[rainerfGasp]

Version

1.8.0

Computer Model

11KG001YGE

Problem

When Get-LSUpdate is used to check for driver updates in our local repository, it finds updates that have already been installed.
Specifically, these are the two:
• u6vdof5us17_v55tare: ((AM4) AMD Onboard Graphics Driver - 11 (21H2 or Later))
• u6chp7jus17_v55tare: AMD Chipset Driver - 11

These updates have already been downloaded and installed via Lenovo SystemUpdate for testing purposes.
However, Get-LSUpdate keeps finding these two updates over and over again.

Additional context

No response

[jantari]

Hello, please run Get-LSUpdate with -Verbose -Debug on an affected machine and we can troubleshoot precisely why this happens

[rainerfGasp]

Hello, here is the Log-File.

driverdebug.log

[jantari]

It looks like you have older versions of these drivers installed.

1. AMD Onboard Graphics Driver (u6vdof5us17_v55tare)

   Installed:	31.0.12027.9001 from March 2023
   In your repository:	31.0.21923.4006 from August 2025

2. AMD Chipset Driver (u6chp7jus17_v55tare)

   Installed:	5.17.0.0 from June 2021
   In your repository:	5.42.0.0 from October 2025

so the updates from your repository being returned would seem to be correct.

[rainerfGasp]

That could be possible.
I just manually searched for and installed updates from our repository using ThinInstaller.
After the reboot, they were displayed again.

To me, that means the issue isn't with Get-LSUpdate, but rather that these updates might not be compatible with silent installation.

[jantari]

Hmm I'm not sure I understand correctly. So you pointed both ThinInstaller and LSUClient at the same internal repository, without installing updates in between or updating the repository, and they returned different results? That would be an issue, if all things are equal (the state of the repository and the state of the system) then the results should be the same.

[rainerfGasp]

What I meant was that the problem is Lenovo.
On their website, under “Manual Download,” the affected drivers have the same version number.
I tried using SystemUpdate in the meantime. -> Same error
That's why LSUClient, ThinInstaller, and SystemUpdate all produce the same result here.

Both marked Drivers contains the same Package. (u6chp7jus17_v55tare)

[jantari]

I think the same driver being linked twice under slightly different names is an error on Lenovos part, maybe @parkerj-lnv can look into this: https://pcsupport.lenovo.com/us/en/products/desktops-and-all-in-ones/v-series-desktops-and-aio/v55t-15are/11kg/11kg0031ge/pc21ycxw/downloads/driver-list/component?name=Motherboard%20Devices%20%28Backplanes,%20core%20chipset,%20onboard%20video,%20PCIe%20switches%29&id=FB762CAD-DE8B-49C2-A04B-809B4958F608

But that only seems to affect the website, LSUClient and Update Retriever only see the driver once as they both pull from https://download.lenovo.com/catalog/11KG_win11.xml .

Like I said, the log you posted on March 19th indicates that these driver updates were not installed yet, so it makes sense for them to show up. If you installed them but they show up again and again the error has to be that they fail to install. Can you capture an Install-LSUpdate -Verbose -Debug log when you try to install this chipset driver u6chp7jus17_v55tare ?

[parkerj-lnv]

The Lenovo V series devices are done by a completely different group inside Lenovo than the one I'm in, so I don't know exactly who works on them. I'd agree that there doesn't appear to be any reason for having the two entries with the same version on the support page. There is another update on that page that is targeted for 21H2 only. The catalog of updates for that machine type has the one update that is targeted to 21H2 and the other that is for the other builds of 11.

As mentioned already, the 11KG_Win11.xml catalog file just has the two chipset updates and what's on the support download page doesn't affect LSU or Update Retriever. What is odd to me is that the catalog file does not contain that AMD Onboard Graphics driver in it so I'm not sure how/why it was offered previously.