cancel
Showing results for 
Search instead for 
Did you mean: 

New IME and chipset for z270 heroix

MrAgapiGC
Level 13
Good morning to all. I have a note that IME 11.7.0.1014 and Intel Chipset 10.1.1.44 is live! any one try these? since i did my clean install 4 days ago i have all ready, from MS servers, the IME. But still running the chipset 10.1.1.38. It is ok to install the new one? Or i do both? IME download said ConsumerME jajaja.
Learn, Play Enjoy! We help and collaborate, NOT complain!
7,016 Views
12 REPLIES 12

MrAgapiGC
Level 13
I remember my former boss. He always told me and teach me..... PLEASE CHECK everything before sending SOMETHING. I am checking the information, and BTW only change some file not the entire Chipset data. driver date 1968 REALLY! someone has to go home, like NOW!

66107
Learn, Play Enjoy! We help and collaborate, NOT complain!

MrAgapiGC
Level 13
New drivers are on. IME, Chipset, Lan, and new audio codex Has anyone has try those?
Learn, Play Enjoy! We help and collaborate, NOT complain!

Notes:
All included *.INF files have been finalized by Intel and digitally signed by Microsoft on 04/19/2017 (v10.1.1.44) or 04/03/2017 (v10.1.2.86), but will be shown by the Device Manager as being dated 07/18/1968.
Bad consequence: If you want to update your previously installed correct dated INF file, you have to force the installation by hitting the "Have Disk" button.
Supported are nearly all Intel Chipsets (incl. the old, the "Enterprise" and the upcoming ones) and all 32/64bit Windows Operating Systems from XP up.

http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html

KSMerg wrote:
http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html


??????? That is on the case that is a missing file from the device manager?
Learn, Play Enjoy! We help and collaborate, NOT complain!

Retired
Not applicable
Hi;
I Have The Same
I Update My Intel Chipset INF Driver V. 10.1.1.44
But The Date is 18/7/1968 WoW

What Happen Man ?????

Probably Intel intentionally puts an incorrect date, since in the previous version of 1970.
; ************************************************************
; ************************************************************
; ** Filename: KabyLakePCH-HSystem.inf **
; ** Abstract: Assigns the null driver to devices **
; ** for yellow-bang removal and **
; ** brands Intel(R) devices **
; ************************************************************
; ************************************************************

[Version]
Signature=$WINDOWS NT$
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=KabyLakePCH-H.cat
DriverVer=01/01/1970, 10.1.1.42

[SourceDisksNames]

[SourceDisksFiles]

[ControlFlags]
ExcludeFromSelect=*

[PackageInfo]
Name=Chipset

[Manufacturer]
%INTEL%=INTEL,NT,NTamd64

[INTEL.NT]
%PCI\VEN_8086&DEV_A290Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A290
%PCI\VEN_8086&DEV_A291Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A291
%PCI\VEN_8086&DEV_A292Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A292
%PCI\VEN_8086&DEV_A293Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A293
%PCI\VEN_8086&DEV_A294Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A294
%PCI\VEN_8086&DEV_A295Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A295
%PCI\VEN_8086&DEV_A296Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A296
%PCI\VEN_8086&DEV_A297Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A297
%PCI\VEN_8086&DEV_A298Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A298
%PCI\VEN_8086&DEV_A299Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A299
%PCI\VEN_8086&DEV_A29ADesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29A
%PCI\VEN_8086&DEV_A29BDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29B
%PCI\VEN_8086&DEV_A29CDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29C
%PCI\VEN_8086&DEV_A29DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29D
%PCI\VEN_8086&DEV_A29EDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29E
%PCI\VEN_8086&DEV_A29FDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_A29F
%PCI\VEN_8086&DEV_A2A0Desc%=Needs_NO_DRV,PCI\VEN_8086&DEV_A2A0
%PCI\VEN_8086&DEV_A2A1Desc%=Needs_NO_DRV,PCI\VEN_8086&DEV_A2A1
%PCI\VEN_8086&DEV_A2A3Desc%=Needs_NO_DRV,PCI\VEN_8086&DEV_A2A3
%PCI\VEN_8086&DEV_A2C0Desc%=Needs_MSISADRV,PCI\VEN_8086&DEV_A2C0
%PCI\VEN_8086&DEV_A2C1Desc%=Needs_MSISADRV,PCI\VEN_8086&DEV_A2C1

no1yak
Level 8
Intel probably not bothered cos it's an INF File and not a driver. Still it's an extremely sloppy attitude .

Retired
Not applicable
What do you think install intel chipset inf v. 10.1.1.44
Yes or no ????
And what i install version ???

mutaz1912mkk wrote:
What do you think install intel chipset inf v. 10.1.1.44
Yes or no ????
And what i install version ???

Here's a tip with http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files-24.html#msg40481
Why do you want to install/update the Intel Chipset Device INF files at all? It only makes sense, if you see any "unknown" or yellow flagged device within the "System devices" section of the Device Manager.