https://i.ytimg.com/vi/2Z4m4lnjxkY/hqdefault.jpg good news for rpcs3 users

Cplifj:

oh wow, MSI thinks it can dictate Intel and how Intel products get used ... some nerve they got, if MSI want to do this they'd better start making their own cpu's. As if Intel is the only company that has nothing to say about it's own products, unheard of while others try to dictate everything. Bad move from MSI, but sure they only want sales of their products. So they'd negate any security fixes by using whatever microcode they want instead of the latest. Can't trust this MSI for my safety and security.

We with Asus Apex z690 have new up to date bioses with imported old cpu microcode. Unofficial is allways the best 😀

Cplifj:

oh wow, MSI thinks it can dictate Intel and how Intel products get used ... some nerve they got, if MSI want to do this they'd better start making their own cpu's. As if Intel is the only company that has nothing to say about it's own products, unheard of while others try to dictate everything. Bad move from MSI, but sure they only want sales of their products. So they'd negate any security fixes by using whatever microcode they want instead of the latest. Can't trust this MSI for my safety and security.

Ugh what? Intel deliberately removed a feature from a microcode update and MSI restored that functionality. Exactly how is MSI the bad guy 🙄

Agent-A01:

Ugh what? Intel deliberately removed a feature from a microcode update and MSI restored that functionality. Exactly how is MSI the bad guy 🙄

He sounds like someone from Intel would sound.

Cplifj:

oh wow, MSI thinks it can dictate Intel and how Intel products get used ... some nerve they got, if MSI want to do this they'd better start making their own cpu's. As if Intel is the only company that has nothing to say about it's own products, unheard of while others try to dictate everything. Bad move from MSI, but sure they only want sales of their products. So they'd negate any security fixes by using whatever microcode they want instead of the latest. Can't trust this MSI for my safety and security.

You ok there?

Govern me more big corporation your word is law,I will do as you say,please keep controlling me that is what I really want blah blah blah frigging sad words I read in these threads at times. I will be buying only MSI Motherboards from now on,I think it is a good move on MSI part even though I do not uses AVX512 ever and I am just a PC Gamer lemming that only into conspiracy theory and I am probably a mouth breather who is racist and misogynistic low intelligence white male who should be in jail because I believe Intel is a-hole with there moves.If this hurts your feeling,I will gladly take the ban and never use this forum again

Cplifj:

Maybe Intel has a sound reason for disabling it, despite most users knowing everything better on the internet.

they disabled it for market segmentation.

Cplifj:

oh wow, MSI thinks it can dictate Intel and how Intel products get used ... some nerve they got, if MSI want to do this they'd better start making their own cpu's.

Do you...work for intel or something? Your reaction is...abnormal. It's not like this is the first time motherboard manufacturers have done similar things, both amd and intel have stated things are not possible or disabled some feature, PCI-express 4.0 on 400 series amd or 300 series support for 5000 series cpus, intel saying cpus are incompatible and various other things, and i have never seen a reaction as....odd as yours....

Cplifj:

oh wow, MSI thinks it can dictate Intel and how Intel products get used ... some nerve they got, if MSI want to do this they'd better start making their own cpu's. As if Intel is the only company that has nothing to say about it's own products, unheard of while others try to dictate everything. Bad move from MSI, but sure they only want sales of their products. So they'd negate any security fixes by using whatever microcode they want instead of the latest. Can't trust this MSI for my safety and security.

I didn't know we had an Intel rep. on these forums!

This is something you can do manually anyway, in most cases. Just download microcode 15 from the github repository, create a raw version "bin or rom" file of the original BIOS or use tools to make a non EXE Version if possible, then delete microcode 18 with mmtool, insert back in microcode 15, then flash the BIOS with USB flashback or a SPI flasher or Elmor tool device. (most in-bios flashers will not flash a bios that has been user modified because of checksum violation).