@Zardoc :
Yes, I missed your recent question about how to get rid of the “bloatware” after having installed unneeded/unusable INF files, because you didn’t use the directly address option, which would have given me a notification about your request.
My answer: The best way to get rid of such bloatware is to do a clean fresh OS installation.
The other option is extremely time consuming: Navigate into the C:\Windows\INF folder, open all files named “oem***.inf” by using an Editor, read their content to check their usability and delete the wrongly installed files thereafter. Nevertheless the related registry entries will remain.
There’s an easier way: pnputil -e will give you al list of installed drivers like
"Microsoft PnP Utility
Published name : oem2.inf
Driver package provider : Microsoft
Class : System devices
Driver date and version : 08/17/2012 6.2.9190.0
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem11.inf
Driver package provider : Lascar Electronics Ltd.
…"
pnputil -d oem??.inf will completely delete the corresponding driver. For drivers in use you’ll get quite reliably an error in Windows 10. But there is a (slight) chance to remove drivers that are essential for system boot, or- less dramatic- drivers for not connected devices
@Fernando
The 10.1.3.1 IvyTown .inf and .cat are missing since at least the 06-16-2020 AIO and are still missing in the 09-04-2020 AIO.
If anyone’s wondering, these may be found in Intel’s 10.1.17903.8106 and 10.1.18010.8141 releases, among others (I’d link but as a new user I can’t).
Somewhat off topic: Prior to 10.1.3.1, device names in the IvyTown .inf erroneously started with “Intel(R) Xeon(R)”. Honestly, seeing ~15 entries that looked like e.g.
Intel(R) Xeon(R)Â E7 v2/Xeon(R) E5 v2/Core i7 Crystal Beach DMA Channel 0 - 0E20every time I opened up devmgmt.msc had been bothering me for years. I understand it’s all cosmetic, but fixing the device names is a pretty good reason to “upgrade” IMO
@ded_kiev - I am having the same problem like yours however my board is Asrock J3455-ITX. I downloaded the file per Lost_N_BIOS wrote: Intel Dynamic Platform and Thermal Framework Drivers v8.2.11003.3588 WHQL drivers. This driver package don’t match the IDs. Can you tell me where you downloaded the drivers?
@ptran3014 :
Which sort of problems do you have, which OS are you running and which are the HardwareIDs of the devices, whose drivers are missing?
@Fernando - I tried to install Windows 7 x64 and x86 on both motherboards: Asrock J3455-ITX and Gigabyte GA-J3455N-D3H. Both are using Intel Apollo Lake J3455 SoC. As you know, they don’t support Windows 7. I found most drivers for them, but still missing some system drivers:
Asrock J3455-ITX:
PCI Simple communications Controllers: PCI\VEN_8086&DEV_5A9A&CC_0780
Unknown device: ACPI\INT3452
Gigabyte GA-J3455N-D3H
PCI Simple communications Controllers: PCI\VEN_8086&DEV_5A9C&CC_0780
PCI Simple communications Controllers: PCI\VEN_8086&DEV_5A9E&CC_0780
Someone wrote a tutorial on Amazon: https://www.amazon.com/review/R19B0HAAKK…_=fsclp_pl_fr_8
I downloaded the driver but the IDs are not the same.
Thank you so much for your help.
@ptran3014 :
Your listed devices belong to the Intel Management Engine Interface and not to the "Intel Chipset Devices". As you already have mentioned, specific Win7 drivers for these devices are not available.
I repeat my question: Which problems are caused by the missing driver?
@Fernando - I am looking for the Intel chipset driver for these boards. If I post this question in a wrong area, please tell me where to post it. I need to find the drivers for those board to fix the missing drivers. I remember I did not ask you. I asked someone who had the same problem like I am having now and you told him the link which I downloaded but did not work. Then I asked him again to see how he solved the problem. However you jumped in and gave me all hard time. You are hunting me and it looks like I owed you money and not paying?
@ptran3014 :
If you would have read the start post of this thread, you would know, that the “Intel Chipset Device Software” does not contain any real driver, but just simple text files, which give the OS the information, that the device has been manufactured by Intel and doesn’t require any driver.
If the “missing driver” flag shown by the Device Manager should be your only problem, I recommend to stop searching for the related driver - it is wasted time!
@Fernando - I am not looking for drivers in Intel INF Chipset Setup. I am looking for drivers for the boards which are missing. Someone reviewed the Asrock board on Amazon and he successfully found drivers for the Asrock board. So, I am looking for TEX and SerialIO Windows 7 drivers for the boards. OK. From now on, I stay away from you. I remember I already did but you are the one who chase after me all the time. I asked someone a question but you jump in in the middle and gave me hard time.
@ptran3014 :
I just have read your linked “Tutorial for installing Windows 7 on J3455 ITX and other apollo lake systems”. The author hasn’t written, that his used “Intel Dynamic Platform and Thermal Framework driver v8.1.10605.221 WHQL” did support the HardwareIDs of his board. He obviously just forced the installation by using the “Have Disk” option and disregarded the warning he got from the OS.
I’ve cleanly installed Win10x64 on an Acer Veriton X4610G (Intel Q65 Express Chip-set, which is in the Intel 6 Series/C200 Series Chipset Family (CougarPoint) with 2nd generation Intel Core processor family (SandyBridge), hardware contained in the X4610G). Acer have ended support after Win8 and now I’m on my own to find the right drivers for Win10x64.
It’s my main rig and I want to get it running sound and stably.
I’m facing what looks like a chipset .INF file problem (see attached picture).
It’s for device: PCI\VEN_8086&DEV_1C3D&SUBSYS_04921025&REV_04
Its event log in device manger shows:
Device PCI\VEN_8086&DEV_1C3D&SUBSYS_04921025&REV_04\3&11583659&0&B3 requires further installation.
Device PCI\VEN_8086&DEV_1C3D&SUBSYS_04921025&REV_04\3&11583659&0&B3 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: ACPI\PNP0A08\0
Device PCI\VEN_8086&DEV_1C3D&SUBSYS_04921025&REV_04\3&11583659&0&B3 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: ACPI\PNP0A08\0
Windows troubleshooter couldn’t identify the problem.
I ran Intel Driver and Support Assistent (iDSA) and it finds no updates for my 6 Series chip-set. The downloads section for the Q65 Express Chipset at Intel doesn’t show anything at all either.
When I look the device ID up in DeviceHunt, it says: 6 Series/C200 Series Chipset Family KT Controller, but it finds no drivers for the device. I have no clue to what a KT controller is.
I’m at loss here.
Who knows what it is, where to get a driver / .INF file for this device and what I can do to get it working properly under Win10x64?
@Marty1 :
Welcome to the Win-RAID Forum!
The INF file for the Intel device with the DeviceID DEV_1C3D belongs to the "Intel(R) Active Management Technology - SOL" and not to the Intel Chipset Device "drivers".
The related "driverpack" v11.0.0.1136 WHQL is attached (it contains just the matching INF file and the associated CAT file with its digital signature). It should support all Windows Operating Systems.
Good luck!
Dieter (alias Fernando)
Intel(R) Active Management Technology - SOL Driver v11.0.0.1136 WHQL.rar (7.24 KB)
@Fernando just a question, you are going to release a aio winth the updated dates, i have a lot of issues with windows update on windows 10 downgrading the drivers
thanks in advance
@yamazakirobert :
Within the start post I am offering an AIO package, which contains the currently newest WHQL signed Intel Chipset Device INF files for all Intel Chipset systems from 6-Series up, but since all these original "drivers" were wrongly dated by Intel, I could not correct the dates without breaking the WHQL stamp given by Microsoft.
Some years ago I have offered a mod+signed AIO Intel Chipset Device INF files package, where I had corrected the driver dates, but I have given up this offer.
why intel doesn’t support with chipset driver and amd supported?
@pipes80 :
It is not easy to understand what you mean. Please explain, what you are missing and what you expect from Intel.
Please consider, that it is the task of the mainboard manufacturer and not of the chipset manufacturer to deliver/offer the appropriate drivers for all on-board devices to the customers.
For a very long time Intel was both (manufacturer of chipsets and consumer mainboards), but since several years Intel offers on its Download Pages only drivers for Intel Server mainboards and Nucs.
What has Intel to do with AMD?
what i was saying is amd offers system component updates with drivers, i believe they use proprietary sys file unlike intel which uses microsoft sys file to make its various components of a chipset and cpu work
@pipes:
AMD’s chipset driverpacks contain real drivers,
whereas Intel’s “Chipset Device Software” contains just simple text files to give the OS and the user the information, that the related devices
a) have been manufactured by Intel and
b) don’t need a real driver.
For all Intel chipset devices, which need a real driver (= *.SYS file), Intel offers separate drivers (e.g. for the Intel Management Engine Interface, SATA AHCI/RAID and I/O Controllers etc.).
That is why you cannot really compare Intel’s and AMD’s “Chipset Driverpacks”.
By the way - the OS own Device Management is done by in-box MS drivers and this is valid for Intel and AMD chipset devices.