Well, all the other drivers installed just fine. It ran overnight doing the same thing--it's now been going nearly 12 hours. In Device Manager there is no SMBus Controller in the "Other Devices" section with a yellow question mark & exclamation point anymore, but there is a line for "SMBus Controller - 27DA" in the System Devices section. So that is good.
Any idea on what would be installed next if it were to somehow finish this step? Is there any harm in rebooting the system at this point before the installation has finished?
The Intel Chipset Device Software is an application that loads a set of dll files to the operating system to properly name the hardware in the system, this is not actually a chipset driver package. In that case there would be no harm on restarting the system at this point. What does not seem normal is that time that it has been taking to install in your computer.
1 of 1 people found this helpful
I had the same problem. I was running it on a fresh Win 7x64 Ultimate ....Sony Vaio Laptop. To fix it I killed the process using process explorer (restarting the computer would work too). Then I navigated to the Intel Chipset Device Software installation file (exe).
- Select the installation file
- Right-click on the installation file
- Select "Properties" at the bottom of the right-click dialog that opens up.
- Select the "Compatibility" tab from the dialog that opens up next.
- Select "Change Settings for all Users"
- In the "Compatibility Mode" group place a check mark by "Run this program in compatibility mode for:"
- The drop-down for selecting your current OS will become selectable.
- In my case I went straight to the bottom and selected "Windows 7"
- For good measure (maybe not necessary or advisable) I I put a check mark by "Run this program as an administrator" located at the bottom of the same dialog in the "Privilege Level" group.
- Click "Apply" in the bottom right corner.
- Click Ok
- Click Ok (again)
Run the program again and it should work a lot better. The problem for me was that it was set to run in compatibility mode for WIndows XP. I am guessing that this is some sort of industry standard technique that is meant to kick off the Windows OS Compatibility Troubleshooter if conflicts arise. But it sometimes doesn't work. Please correct me (someone who knows better), if the above information is erroneous.