Solved Windows Update: AMD SMBus

[DavidE]

I have this SMBus update available on a Win 7 x64 OS with a Gigabyte motherboard and AMD CPU.
This system has a SMBus Controller in system devices.
I haven't installed any of the Win 10 updates on this system.
I'll be creating a Backup Image within the next few days for the upcoming Patch Tuesday updates.
I'll install the SMBus update after i create the Backup Image.

My Test box is an Abit motherboard with AMD CPU.
This system does NOT have a SMBus Controller in system devices.
This OS has all the Win 10 updates installed, but i have not reserved Win 10.
On the Win 7 x86 OS, I don't get the SMBus update offered (there is no SMBus Controller).

Based on what i see on my systems, i think how the Motherboard manufacturer built the mobo makes a difference.
They may or may not use a SMBus Controller.

 

[GokAy]

This one got offered to me as well. My board is AMD though. I will update now and see what happens!
------------

Alright, ATI SMBus changed to AMD SMBus, didn't ask for a restart.
Date: 1/18/2015
Version: 5.12.0.31

 

[DavidE]

It would be interesting to see what your current driver version is, and what it is after the update ...
If you see this post before you update, you might want to grab some screen prints of the current driver, so you can compare what changed ?

 

[GokAy]

Old one was 2006 so probably the one from earlier post. http://www.sevenforums.com/general-discussion/371893-windows-update-amd-smbus-2.html#post3081806

 

[Boozad]

Just installed W8.1 SMBus driver on my W10 install from ASUS support page for my motherboard dated 2013 and all is well following a reboot. 2006 drivers are so yesterday.

 

[Jesse Williams]

My system didn't ask for a restart either. Did I do the right thing by installing the update?

 

[DavidE]

You should be fine with the update.
Boozad installed the update and has no problems.

I just don't make any "major" changes to my primary PC without making a backup image before the change.
I'll apply this update later, it's probably a long overdue useful update.

 

[GokAy]

Mine is backed up daily, and a clone was made yesterday so I was ok to do it right away

 

[heffeque]

After the Windows Update.

 

[Jesse Williams]

After the Windows Update.

I went to what you went to heffeque, and unfortunately it says no drivers are installed for this device under device status.

 

[derekimo]

I got this update on my laptop today after doing a clean install of W7, it was one of the first offered so I think it's just an update.

I retract my W10 theory/guess.

 

[DavidE]

After the Windows Update.

I went to what you went to heffeque, and unfortunately it says no drivers are installed for this device under device status.

I see the same thing for "No Drivers installed" on the General tab (default tab) !
Click on the Driver tab, and see what it shows for you.

I just installed this update and here is what i see on the Driver tab:

 

[derekimo]

Yeah, this was an interesting post about that driver over on EF,

If you look at the driver INF file it is a null driver

; ************************************************************
; ************************************************************
; **  Filename: Chipset_SMBus.inf                           **
; **  Abstract: Assigns the null driver to SMBus            **
; **            devices for yellow-bang removal.            **
; ************************************************************
; ************************************************************

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=Chipset.cat
DriverVer=02/25/2014, 10.0.13
[SourceDisksNames]
[SourceDisksFiles]
[ControlFlags]
ExcludeFromSelect=*
[PackageInfo]
Name=Chipset
[Manufacturer]
%INTEL%=INTEL,NT,NTamd64
[INTEL.NT]
;9.1.9.1004 5000XZVP.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_269B
;9.4.3.1008 AvotSMB.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F15
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F3C
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F3D
;9.3.1.xxxx CentSMB.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C59
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5A
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5B
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5C
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5D
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5E
;9.2.0.1034 cougsmb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1C22
;9.2.2.1038 DH89xxCC-smb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_2330
;9.1.9.1004 ibexsmb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_283E
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_2930
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_3A30
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_3A60

 

[Jesse Williams]

Yeah, this was an interesting post about that driver over on EF,

If you look at the driver INF file it is a null driver

; ************************************************************
; ************************************************************
; **  Filename: Chipset_SMBus.inf                           **
; **  Abstract: Assigns the null driver to SMBus            **
; **            devices for yellow-bang removal.            **
; ************************************************************
; ************************************************************

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=Chipset.cat
DriverVer=02/25/2014, 10.0.13
[SourceDisksNames]
[SourceDisksFiles]
[ControlFlags]
ExcludeFromSelect=*
[PackageInfo]
Name=Chipset
[Manufacturer]
%INTEL%=INTEL,NT,NTamd64
[INTEL.NT]
;9.1.9.1004 5000XZVP.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_269B
;9.4.3.1008 AvotSMB.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F15
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F3C
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1F3D
;9.3.1.xxxx CentSMB.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C59
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5A
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5B
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5C
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5D
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_0C5E
;9.2.0.1034 cougsmb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_1C22
;9.2.2.1038 DH89xxCC-smb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_2330
;9.1.9.1004 ibexsmb.inf
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_283E
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_2930
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_3A30
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_3A60

What does that mean?

 

[derekimo]

https://msdn.microsoft.com/en-us/li...608(v=vs.85).aspx?f=255&MSPPError=-2147217396

You might install a "null driver" (that is, nonexistent driver) for a device if the device is not used on the machine and should not be started. Such devices do not typically exist on a machine, but if they do, you can install a null driver. Additionally, the system installs null drivers for devices that do not have a function driver, if they are capable of executing in raw mode.

Basically, a blank placeholder, if I understand the above correctly.

Which would also fit with the small size of it. (30kb)

 

[tblob]

Here is a screenshot of notes from a 2011 version of the driver (13-9?)

 

[SirTenTea]

Am I to understand that this is a "null" driver? If so, then what benefit is it to my machine? it's listed as an "optional" update as well.

 

[tblob]

At the most basic level, the "benefit" it provides is that Windows device manager knows what that device is, knows its device ID info, and it won't show the little "unknown device" warning icon. It won't spend any resources looking for that driver or wondering about what it should do about the situation.