I was thinking 50650, CPUID's ending in zero are often ES/QS/Confidential CPU's. If you don't use those ever then we can remove this one, then if you do end up needing to use a CPU with that ID in the future you can just reflash stock BIOS before putting the CPU in, then get new mod when that time comes.

Results in search look like that is some ES and some Xeon's

@zz309

Could you try this new one please ?

https://drive.google.com/open?id=1m2jEhE...ZykslL1mNDgPBGf

Anyway, I've always used FPTW64 in order to flash winbond/mxic eeproms, as the USB Bios Flashback is not a 100% safe procedure,
but in your case if you have the flash descriptors locked, is the only choice.

@Sylar76 thanks again for your help! i'll try it later

And here is my mod to try - see below post instead. If both of these from us fail now, then we know to try MMTool next instead.
If both of these do fail, and then next edits fail with MMTool too, I am unsure what could be causing the issue.

Wait a few minutes, I figured out the issue now! Editing fix now, and will edit into this post once done! (Due to this problem, above mod will fail too, I checked the file)

@Lost-N-BIOS Sylar'new one cannot work yet

@zz309 - I know, and I know the issue, uploading BIOS now that should work!

See edit here in one second, let me finish typing out my reply about the issue

Problem was FIT, in all mods I checked including @sylar76 mods too. _FIT_ must be corrected, and that must be done by hand due to McodeFit.exe -fixfit does not work on this BIOS.

This should be working now, I still did remove one ucode to keep the microcode file overall size the same, in case that was also causing issues in previous mods (Although, probably not, main issue was probably only the FIT table all along!)
This probably cannot be flashed by regular in BIOS method, use USB Flashback or FPT


https://www.sendspace.com/file/jlyqlw << Link dead, see below, two posts down for new link

@Sylar76 - you mod may work too, with all the microcodes and the updated file size, but you have to correct FIT table so it all is right and shows up in UEFITool NE 45 as seen in the image above.
Open your mods in that UEFITool and see FIT, then compare with original BIOS before editing, you'll see table is populated before mod but not correct after mod. If you need the guide on fixing that let me know I'll send you links.

Redoing mod now in MMTool, to see if it messes up the FIT table too or not! - Confirmed both MMTool 5.02.0024 (CPU Patch Tab) and UEFITool 0.25 (GUID extract/Hex edit) mess up the FIT table when editing microcodes on the Asus PRIME X299-A 1401 BIOS
I did not test GUID extract and edit with MMTool, assuming the same outcome from using the CPU patch tab.

strange, after Press the BIOS-Flashback button, flashback-led starts didn't blink, so bios cann't be flashed
anyway, thanks for your kinds again @Lost_N_BIOS
i'll go home, this pc is in my office
wish you have a nice weekend

@zz309 - You're welcome! Sorry for the issue still! Maybe because it's not in cap file? Ohh wait, I know flashback need certain file name, I forgot that when I mentioned flashback

Please rename to X299A.CAP If that fails, here is same file in capsule again (May fail, due to capsule is to prevent modifications).
http://s000.tinyupload.com/index.php?fil...287443471241288

You may need to, and should probably use Intel FPT to flash anyway, but hopefully one of these methods, rename or use this new cap file
If you do end up using FPT, use the .rom file.

@Lost_N_BIOS

Please, could you provide me valid links for _FIT_ fix ?

Edit: Nevermind, I've found by myself how fixing _FIT_ entries.

@zz309

Here is modded and fixed bios.

https://drive.google.com/open?id=1fV2o2e...4hsZTcT448L1jXQ

@SoniX

can you please check this? [Discussion] UBU Tool related Questions, Reports and Suggestions (280)

Regarding MSI Z97.
So, all went well ! I flashed the modified BIOS with fpt, although it said the bios was identical. So whats the next step? I would like to patch the Sata Controller, GOP,Network and the actual Haswell microcde. Can i use ubu now for that?

@Sylar76 I know you got it, but in case anyone needs the info later after finding our discussion, this helped me along - [GUIDE] AMI INTEL CPU Microcode Update Guide
and this post here on page 3 - [GUIDE] AMI INTEL CPU Microcode Update Guide (3)

@sgthawk - Good all went well! From what @SoniX said sounds like you can go ahead and modify the BIOS and reflash now. Maybe wait for him to confirm which/what method is OK, but I assume he meant once that BIOS tested OK you can go ahead and use UBU then reflash again.

I have updated with the UBU Tool my NIC Cards, and the NIC Intel i211 is now seen at the BIOS as an Intel PRO/1000 Network Connection. Is there a way to fix this, that it is seen again as an Intel i211? I have added also two screenshots of it. I used this version v1_70_b19_Dev_fix1 of the UBU Tool. In Windows is the Network Card correctly detected and in the BIOS Boot Order it is also correctly displayed.

@aiocr & @ALL

If, when updating the microcode with UEFIReplace, you received such a message

then use the update with MMTool

@Lost_N_BIOS
Do not quite understand what needs to be confirmed?

@hitman20
Provided little information.