Warning for Windows 10 10162 Users.

Yeah, I noticed HwInfo64 also supports Intel ME so I'm assuming it does in fact have other options for thermal control than we know from Intel's docs.. Also, the AMT your referring to isn't in our systems, that's 5MB sku, we're consumer chipsets so 1.5 sku.. As for how much control Windows has with ME and BIOS interactivity, we don't know.. But ME does control CPU clocks and such now also this generation so ME is important to BIOS.. It's on the same chip, just different region. A lot of users don't even have the drivers installed in Windows, so can't say for sure, but the firmware is there and active, even if Windows can't interact.

 

so how does the IMEI firmware work for Alienware laptops anyway?

 

The Intel ME firmware allows BIOS and Windows to communicate, but it also controls aspects of the BIOS now also since 8.x.xx.xxxx. It's a necessary component in our chipsets.. Because we're consumer sku, we have basic remote monitoring, not the full AMT package, but it's used for other things now.. It's part of the backbone of the chipset. It's usually updated with BIOS updates, but with the latest BIOS that Dell has released, they have failed to update to 9.1.30.1008 which is required for Windows 10, so we have to manually flash it.. Which is safe to do as the ME firmware can be downgraded if another BIOS release is made by Dell with an older version. Hopefully we will see BIOS updates to properly support the new ME, and if not, flash yourself..

 

So which version should we flash though I am using uefi so not sure how that will work.

Sent from my HTC One using Tapatalk

 

UEFI is fine as Intel ME isn't dependent on that. Go to latest leaked build which is 9.1.30.1008 1.5MB version. You can get it at http://www.station-drivers.com/inde...ntel-ME-Firmware-Version-9.1.30.1008-(1.5Mo)/ and includes the flash utility.

Only warning is, if your machine has 9.1.xx.xxxx, we CANNOT use 9.5.xx.xxxx or 10.x.xx.xxxx... We have to stick to 9.1.xx.xxxx.... We can't jump major builds.. But you can use ANY 9.1.xx.xxxx, so use the latest which now includes Windows 10 support.. Even tho you have to flash using a command line, you can do it in Windows without needing a MS-DOS bootable USB stick.

Run MEInfo first and take note of the version you have installed.. Not the driver version as it depends on your model and the note I made above.. The flash process is simple.. Do a "FwUpdLcl -F ME_9.1.30.1008_1.5M.bin" without quotes. Takes about 20 secs to flash. After flash is done, reboot and verify using MEInfo which is in that package.

I have done this to my AW17R2 and works fine. If Dell releases another BIOS update, it will downgrade or update the ME.. It's not protected region and can be downgraded if needed.

 

ok, will check what version it is first before flashing....this might be the root cause of my issues with win 10.

 

Depends on the issues.. If its video, you need BOTH Intel's new Win 10 drivers from a day ago or so, and the latest NVidia driver for Windows 10, or you won't see the devices.. A few manufacturers have asked MS to change the hardware ID's on some products to determine if it's Windows 10 driver that's needed, or previous version cause of compatibility issues... Hence the jump from Windows 8.1 to 10.. This has happened in Windows Server 2016 Technical Preview also.

Won't hurt to have latest ME firmware installed though, then you can just forget about it until a new BIOS update comes out from Dell and Compal..

 

Can you please help me understand why you would say this is required by Windows 10? Required? How so? Or, do you mean required for Windows 10 to "own you" the way they intend for it to, LOL?

I've already run several technical preview builds with the original MEI firmware on my Sandy, Ivy and Haswell machines. What are the benefits of giving Windows 10 the MEI firmware that it wants to work with, and what are the potential harmful side effects?

So, any Sandy Bridge, Ivy Bridge or Haswell Alienware laptop owner can flash the 9.1.30.1008 firmware in safety? What about creating a backup of your current MEI firmware, just in case you don't like how it works after flashing it? Does using the -save command with a file name back it up for you?

What about the people that see this error message? Are they just out of luck?

I know on my M18xR2 the MEI 9.1.30.1008 Firmware Update tool cannot even correctly identify my chipset. It thinks it is a Series 6 but it is Series 7.

 

Ok will check when I get home.

EDIT: I think it is safe to say that alienware won't update the BIOS for the R1s so there's no worry of the ME firmware being up or down graded.

Sent from my HTC One using Tapatalk

 

The tool in that package only works with 9.1.xx.xxxx.. You'll need the package for the series you have..

And I meant its required in the sense the older versions won't work properly in Windows 10, but its still working between ME and BIOS.

The version of ME is different depending on your chipset.. That's why there so many versions available.. ME 6.x, 7.x, 8.x, 9.0, 9.1, 9.5, 10, and now 11 for 100 series chipsets (Skylake).

You have to stay with your branch, you can't go from 6.x to 7.x or 8.x.... It will kill the ME.
The 9.1.30.1008 I pointed to is for the Echo line on the HM87 chipsets.

 

OK, good... that's what I was thinking, but it wasn't clear until now. Thank you for clarifying this. That version only applies to a small portion of the Alienware Community.

 

If your using a R1, don't use 9.1.xx.xxxx... I think your on 9.0.xx.xxxx.. Get a package for 9.0 if the MeInfo in the 9.1 package doesn't recognize it. If your using a 2015 model, then use 9.1.xx.xxxx....

 

Yeah, but there are Windows 10 updated versions of the other branches.. But only since ME 8.xx.xxxx its got more control of the hardware and BIOS.. Before that, it was more for remote management and a lot of machines didn't even include ME or MEI..

 

so i should use 9.0.31.1487 for R1?

what's the difference between the 1.5mb and 5mb version? Is there some instructions I can follow?

 

Here's some of the most detailed info: http://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html

This is about as detailed as you will find... still doesn't give me enough insight to decide whether or not I actually want this crap on my system. I know I don't want the DPTF filth. I have that disabled in my BIOS (unlocked BIOS FTW) and the drivers are not installed. I have all thermal sensors turned off and all the limits maxed out. Intel builds thermal protection into the CPU and anything extra added through firmware or OS management is just unnecessary fluff that cripples performance.

Anything I can do to block Windows from knowing what is happening at a hardware level and taking steps to "help" is worth doing IMHO. This is none of the OS's business and needs to stay that way. If that means using obsolete firmware to block the communication from taking place, then that's the right approach to take as long as Windows 10 doesn't do something stupid when it discovers that it cannot communicate with the hardware. That last part is what has me worried. No telling what kind of silly cancer they might have lurking around in Windows 10, but I guess we will start finding out tomorrow, LOL.

 

Will have to double check and provide the correct information of my board cos i am still confused and I am not at my PC atm (at work )

 

Just don't do something you might regret. This can wait until we know what to expect... definitely not urgent unless we run into problems that only MEI firmware updates can cure. Since we don't have crippled BGA machines with puny TDP limits and inadequate AC adapters, we don't have to worry about Windows 10 helping us "do more with less" in order to have a mild-manner and sedate machine.

 

will just do some investigation.

EDIT: @Lord Zog - when i mean R1 I meant the 2013 model, not the M17XR1.

 

ME Analyzer v.1.2.2 will help you identify what MEI firmware and drivers are being used by your system. I believe it will work with most versions.

Here's what my M18xR2 has...

 

Judging by how old / recent my hardware I should be at least version 9.x but will verify when I get home.

Sent from my HTC One using Tapatalk

 

The latest driver version (see image) available from Dell is 9.0.2.1323, but not sure what firmware version you have.

 

Almost home LOL

EDIT: dell's latest version of the IMEI driver for the AW17 R1 is 9.5.15.1730 and that's from december 2013. will download it and the analysis app to see what i have installed.

actual firmware is 9.0.2.1345

The AW17 R1 is using the series 8

Getting Error 9256...it can't communicate with the ME and it's showing in device manager as working.

OK, not touching this further cos i really want to get the 120hz screen going.

EDIT: now the screen flickers on and off when booting....not sure what's the deal there maybe need to reinstall windows.

 

That's old. Use this package.. http://smtp.station-drivers.com/ind...ntel-ME-Firmware-Version-9.0.31.1487-(1.5Mo)/

Even tho the driver is 9.5, we're looking at firmware only.. You can use 11.x drivers, but firmware, we have to stay in the major builds. In your case, 9.0.xx.xxxx.. 9.0.31.1487 is what you need. USE 1.5MB firmware. 5MB is for different chipsets.

 

hmmm....not sure how to actually do it when MEInfo and MEManf give the 9256 error.

EDIT: Update says it can't find the ME driver

found some better instructions and i can get MEinfo to get the info.

http://forums.tweaktown.com/gigabyte/54860-about-intel-management-engine-firmware.html

ok, looks like HWInfo was blocking MEinfo.

ME firmware now fully flashed

 

So, any luck ?

 

with what?

 

so far windows 10 is looking good in terms of system compatibility and stability but it's a bit slow when loading since i am testing with an HDD than an SSD.

 

****************** WINDOWS 10 UPGRADE WARNING TO ALL ALIENWARE OWNERS ******************​

Windows 10 has blown out the display panels from my M18xR1 and M18xR2 within 24 hours of installing Windows 10. 8 beeps, no backlight, no boot. So, first time I blew it off as a one-off coincidence. Hardware fails, right. OK, but the sSecond time, I'm ready to go ballistic now. Don't know if it is the OS or the GeForce drivers, but I don't see how it can be a a one-off coincidence twice within 24 hours.

 

sounds quite rare but still weird.