Zitat von plutomaniac im Beitrag #2840

---

@ atomota:

If that was the case the problem would have been solved after updating to 11.6.25.1229. Remember that if the problem is at the ME data then ASUS won't be able to fix it remotely by a BIOS update (as we extensively discussed before). If the problem is at the ME firmware then a simple update will solve it. Also, no need to tag me at this thread, I monitor it regardless.

---

I think these firmware will come out only for Corporate systems. Consumers are not affected by such issues.

Zitat von plutomaniac im Beitrag #2845

---

Zitat von Pacman im Beitrag #2842

---

Older version ME FW 11.6.12.3202 Corporate H & LP showed up at HP today.

---

I don't understand what this firmware is. It makes no sense. Intel and their partners all mention firmware 11.6.27.3264 and now we have another with build 3xxx (11.6.12.3202) which was built yesterday apparently (04/05/2017) based on an older hotfix version (11.6.12 instead of 11.6.27) and with an older VCN number of 174 instead of today's 192. Why?

---

HP is special. This *will* look fanboyish[1], but the fact is that HP _typically_ takes far more care of their server and corporate lines than any other vendor. They are the only ones that shipped firmware updates containing certain microcode updates (that cannot be found *anywhere else*) fixing security issues on old Intel processors such as the Core Duo, and Core2. Such processors were used on some of their 6-year-old corporate desktop lines, and it does look like it was HP that requested that Intel produce such updates for the older SKUs, even when they were already listed as EOL according to Intel ARK.

So, yes, you can and should expect HP corporate machines (servers/desktops) to show up with firmware you won't find anywhere else.

[1] I don't actually like HP hardware because it does way too much behind your back in SMM (massive headache for HPC, and low-latency + low-jitter work), and it also has a tendency of being "special" in very bad ways.

If it's not mentioned before:

9.1.41.3024 (I think it's the 5MB Firmware) can be found on Fujitsus support pages , search Desktop => ESPRIMO E520

I'd be happy if somene found an updated 9.0 version (5MB) :-)

I read the note but I would like double confirmation from the experts here.

The vulnerability in INTEL-SA-00075 does not affect systems with the 1.5MB consumer version of MEI? Am I correct?

See, for example, here and here for an alternative view.


Sadly, there's no news of updates for the 9.0 branch? It seems to be left hanging.

Zitat von plutomaniac im Beitrag #2840

---

@ atomota:

If that was the case the problem would have been solved after updating to 11.6.25.1229. Remember that if the problem is at the ME data then ASUS won't be able to fix it remotely by a BIOS update (as we extensively discussed before). If the problem is at the ME firmware then a simple update will solve it. Also, no need to tag me at this thread, I monitor it regardless.

---

Zitat von bronxamigo im Beitrag #2852

---

.......Sadly, there's no news of updates for the 9.0 branch? It seems to be left hanging.

---

Zitat von plutomaniac im Beitrag ME 9.1.0.1120 *required* for Intel Haswell Refresh CPU ???

---

8-series came with ME9.0
9-series came with ME9.1

8-series can be upgraded to ME9.1 to support HSWR
BIOS needs to be updated as well to work with ME9.1

If your mobo supports HSWR based on ASUS support list, then the BIOS should be ME9.1 compatible and thus you can use FWUpdate to upgrade to the latest ME9.1 firmware

---

Zitat von plutomaniac im Beitrag ME 9.1.0.1120 *required* for Intel Haswell Refresh CPU ???

---

8-series can be upgraded to ME9.1 to support HSWR
BIOS needs to be updated as well to work with ME9.1

If your mobo supports HSWR based on ASUS support list, then the BIOS should be ME9.1 compatible and thus you can use FWUpdate to upgrade to the latest ME9.1 firmware

---

The problem is that i have an asus b85 plus motherboard.
It support haswell refresh. ( i have it with a i5 4460)
And the ime of latest bios is 9.0.xx.xxxx

Can i update it to 9.1?