June 2015 microcode update for Intel processors in Windows
-
Thanks for that.
I'm not sure i want to update this when i haven't been having any issues i can perceive but then it could be silently corrupting everything in the background! It's been going fine for several years now though with nothing but the very occasional windows hissy fit. But then do i install and find it causes problems requiring a bios update as well which i really do not want to do unless i have to... god, such an innocuous looking update and an optional one at that.
It doesn't look like that second update applies to mine if i'm reading the intel processor id utility correctly though.
That's entirely up to you, you can hide kb3064209 and decide not to download the 2011 Hotfix Kb2493989 too, if you think your Bios is up to date and have the latest one.
"If it ain't broke, don't fix it" :)
-
-
Oh my bios is far from being up to date but i am of the school of thought which says to leave it alone unless you have very good reason to update it.
-
The update finally showed up today for my system. I wasn't having any problems that I know of and it seems to be working OK with the update.
-
-
Was your bios already up to date, fireberd or did you just install the update as is?
-
I have the latest BIOS. The motherboard I have, an ASRock Z77 Professional Fatal1ty is 3 years old and there hasn't been any BIOS update since 2013. I wouldn't expect to ever have another BIOS update.
I just installed the update, along with two other optional updates.
-
Ok, thanks. I'm not sure my ageing gigabyte p55 has anything newer either actually but i can't swear by that. I'm so dubious about these optional updates from microsoft now though that if they don't address any specific issue i am having then i just hide them. Not to mention the whole reclassification nonsense where some were classed as important.
-
-
Was your bios already up to date, fireberd or did you just install the update as is?
Before going in an adventure way, i suggest you to check if your motherboard manufacturer have the latest Bios for you because it may have the proper CPU microcode inside. If not, then try to see the actual Cpu microcode you have.
Bios update is always risky as you might know but is the condition too. Double check manual instruction if not sure of yourself.
You can retrieve infos of your CPU ID with HWiNFO (x32 or x64) portable version or installer, launch Summary only will give the CPU µCU within the codename line.
The Kb3064209 might contain your Intel processor in the list too if not already in their latest Bios. A shame MS did not this time gives the conditions of this update and what particular Intel's Processors are inside. Finally i updated with a guess, i recon and my latest Bios is from May 07, 2014 (CPU Microcode was not updated inside)!!
-
You can retrieve infos of your CPU ID with
HWiNFO (x32 or x64) portable version or installer, launch Summary only will give the CPU µCU within the codename line.
I was gonna ask about that, was the screenshot in your first post from this? I'm finding it difficult to locate any software which shows the microcode update revision.
But yes, microsoft fails in its lack of info yet again, there really should be conditions listed with this update.
-
You can retrieve infos of your CPU ID with
HWiNFO (x32 or x64) portable version or installer, launch Summary only will give the CPU µCU within the codename line.
I was gonna ask about that, was the screenshot in your first post from this? I'm finding it difficult to locate any software which shows the microcode update revision.
But yes, microsoft fails in its lack of info yet again, there really should be conditions listed with this update.
Yes, the screenshot is coming from HWiNFO when full Run. At start you can select with two boxes to check or uncheck if you want selected to display.
-
You can retrieve infos of your CPU ID with
HWiNFO (x32 or x64) portable version or installer, launch Summary only will give the CPU µCU within the codename line.
Hi NoN,
is this what you used to get all the processor info displayed in your first post?
thank you