New Microsoft/Intel microcode update KB4100347 breaks Haswell-E and Broadwell-E overclocks

Published by

Click here to post a comment for New Microsoft/Intel microcode update KB4100347 breaks Haswell-E and Broadwell-E overclocks on our message forum
https://forums.guru3d.com/data/avatars/m/243/243702.jpg
sykozis:

Doesn't matter if it is supposed to affect it or not. It should have never been downloaded in the first place.
Important part is, if it is installed. MS uses its users as torrent network for distribution of patches. So, maybe they just downloaded it. Either way, it is good catch.
data/avatar/default/avatar02.webp
sverek:

Is it limited to specific maker (ASUS, etc) or a global issue?
Well the good news is that this isn't universally true. This update did not affect my overclock at all with my 6850K on an Asus X99 Deluxe USB 3.1. Everything is working just as it was and as it should.
data/avatar/default/avatar14.webp
Margalus:

Well the good news is that this isn't universally true. This update did not affect my overclock at all with my 6850K on an Asus X99 Deluxe USB 3.1. Everything is working just as it was and as it should.
From what I gather, it's a BIOS microcode incompatibility and it is board model specific.
data/avatar/default/avatar39.webp
Well, what a complete load of bullshizz. RS5 pretty much kills any overclocking at all on my board. Even XTU is fukced and wont work. What kind of stupid shizz is this?
data/avatar/default/avatar37.webp
lol this pc platform is such crap lately it on life support. better buy your new intel chip next rtx patch gonna be worse. typed this on my 1k toaster.
data/avatar/default/avatar27.webp
Anyhow a *simple fix for now is to take ownership of mcupdate_genuineintel.dll rename it and replace it with an earlier version. I used a July version. Also set it to read only.
https://forums.guru3d.com/data/avatars/m/246/246921.jpg
yeap.. intel microcode update did breaks my overclock .. (i'm also a bit skeptical after having wierd issue on my 2ndary system (i2600k/sabertooth z77 as DAW) since July (microcode update rollup on build 1709) having trouble with corsair platinum timing keep revert to native jedec spec. Bios changed did fix it but wont last to 2nd boot) ...i wonder if this related with the update even on SandyBridge.. 🙁 they really own us now
https://forums.guru3d.com/data/avatars/m/90/90026.jpg
Why the hell using automatic updates anyway...I always use ms service to install very few that do not destroy stability/perf, and some drivers, then left it disabled to the end of the world...or system change. You wanna be safe, install good firewall...
https://forums.guru3d.com/data/avatars/m/239/239175.jpg
GREGIX:

You wanna be safe, install good firewall...
A firewall has no defense against Meltdown and Spectre. It is completely bypassed.
https://forums.guru3d.com/data/avatars/m/105/105757.jpg
Just found this update on my Ryzen 1600X system, WTF! Uninstalled and blocked. Feck off Microsoft!
https://forums.guru3d.com/data/avatars/m/274/274948.jpg
Jagman:

Just found this update on my Ryzen 1600X system, WTF! Uninstalled and blocked. Feck off Microsoft!
The reason it installs on AMD systems is if you ever change CPU (keeping OS installed) the patch is applied to the Intel system it has 0 effect on AMD systems.
https://forums.guru3d.com/data/avatars/m/90/90026.jpg
Well as I understand, the fun with spectre/meltdown is when somebody has physical access to device and/or maybe by successful java script injection (but all browsers are patched already for that)
RealNC:

A firewall has no defense against Meltdown and Spectre. It is completely bypassed.
data/avatar/default/avatar06.webp
LOL oh man gotta love INTEL news lately. Time to sell that stock and rock an AMD.
data/avatar/default/avatar15.webp
Some of you up above missed something The mcupdate_genuineintel.dll is now integrated in RS5. If you update and you are affected there's no KB to remove. You have to use the simple procedure as outlined. Take ownership and replace with an earlier version. I used the one from July in SXS backup. Save a copy. Who knows when they will fix it or....patch this workaround...SMH...ha ha.
https://forums.guru3d.com/data/avatars/m/105/105757.jpg
Alan Stables:

The reason it installs on AMD systems is if you ever change CPU (keeping OS installed) the patch is applied to the Intel system it has 0 effect on AMD systems.
Had to think back and investigate to be sure but it's a fresh install for this 1600X PC build (8th June 2017). Also I had to remove xtuservice.exe (Intel® Extreme Tuning Utility) which I noticed running a few weeks back! I mean, what the heck is going on?
https://forums.guru3d.com/data/avatars/m/259/259045.jpg
Yeah that KB does the same to my 6800k+R5E, OC 4.4 down to 3.6. I posted about this a couple weeks ago in the Intel section. I hope something is done prior to RS5 release cause the Microsoft rep I spoke to claimed it would fix it when it releases...
https://forums.guru3d.com/data/avatars/m/216/216490.jpg
Brother in law has my previous 4.6 5820k chip paired with the MSI X99 Krait. Don't remember if it's the S or A one in case it matters. Will check if he's affected(if update is installed that is) and report back.
data/avatar/default/avatar06.webp
Does this really affect Haswell-E? I have 5820K and Asus X99-S mobo running 2101 bios. Update KB4100347 is installed on my system. My overclock is working just fine like it did for the last 3+ years. All cores go up to 4.4Ghz, I just tested.
https://forums.guru3d.com/data/avatars/m/239/239175.jpg
R41DZ3R0:

yeap.. intel microcode update did breaks my overclock .. (i'm also a bit skeptical after having wierd issue on my 2ndary system (i2600k/sabertooth z77 as DAW) since July (microcode update rollup on build 1709) having trouble with corsair platinum timing keep revert to native jedec spec. Bios changed did fix it but wont last to 2nd boot) ...i wonder if this related with the update even on SandyBridge.. 🙁 they really own us now
No issues on 4.2GHz 2500K here. No BIOS update is available from MSI (and extremely unlikely that they will offer one.) So system boots with old microcode, Windows then updates it at startup, the OC doesn't seem to be affected.