AMD chipset update installs but is not recognized by OS

Here's a screenshot of the OMEnt job indicating update of the AMD SMBus driver is successful:

My group is also having this issue on multiple servers. I have spent several hours poking at it and researching but have come up empty. I'm interested in any solution or advice found.

Hello all, it looks like an OS issue to me-the application is installed based on the screenshot attached however the OS still is forcing generic drivers that were delivered with the OS image.
Could you make sure if you followed this article?
https://dell.to/3zUH54n
As a workaround, you could also try to delete the device in device manager and let it search again.

@DELL-Young E​ Looks like an issue with the driver package versus what OMEnt is expecting.

I rant the installer and grabbed the temp folder that it extracted. In the install folder is the 'payload' folder containing the AMD Chipset Drivers.

As you can see from the screenshot below, the payload actually contains SMBus driver 5.12.0.38 and not 6.02.22.100 as expected:

Let me know if this helps.

@DELL-Chris H ​ Yes, that's the file I am using. If you extract the contents you will see that despite the 6.02.22.100 file name, the actual driver contained in the package is 5.12.0.38. Which is why the driver does not update even though the install runs successfully.

Hello, it is working as designed, the snippet you shared is correct, I got confirmation from the team. This is what you get with this bundle.

Respectfully,

@DELL-Young E​ If the package is working as designed, then the issue lies with OMEnt.

We can see that it reports that it has updated the driver from v5 to v6, yet this has not actually happened as the installed version stays at v5

And then we see that OMEnt still flags the device(s) as non-compliant because it is expecting v6 but the package doesn't update the driver to v6.

The underlying issue remains the same: the driver package has been successfully installed but OMEnt does not recognize that and reports the devices out of compliance.

Looks like I'm unable to edit my previous post to include the OMEnt screenshot. Here's where we see the flag for non-compliance even though the driver update was successfully applied:

Thank you for clarifying. I went ahead and reached out to the OpenManage group and they are looking into the issue. I am not certain if it will be corrected, or when that may be. 

Thank you for taking the time to point out the issue.

@DELL-Chris H ​ Same issue here and I believe the SMBus driver 5.12.0.38 is correct while 6.02.22.100 does not really exist. Hence the update catalog is incorrect.