Minisforum MS-01 BIOS

[junjun]

My apologies and thank you for pointing that out. Somehow I was blind to that on earlier pages of this thread. That fixed it and I was able to flash 1.26 successfully. In case anyone else needs more clarity, you need to Setup > Security and set an admin password. Be sure to save and exit that screen and also allow it to save and reset everything. When you cold boot again, enter the admin password, then you can go in and disable secure boot on the same screen where you set the admin password.

Thanks, needed this to disable Secure Boot. Without the admin password it wouldn't even show me the option to disable secure boot.
Updated to 1.26 successfully with this and @kenosborn 's instructions. I needed Shell.efi in my USB drive's root else clicking UEFI in the BIOS just flashed black and did nothing.

After the update, it wiped out my admin password but was able to re-enable secure boot without it.

 

[myn]

You are comparing 13th/14th Gen Desktop CPUs with the 13th/14th Gen Mobile CPUs being used in the MS-01. They don't use the same versions of microcode. The 0x12B update you mention is strictly for Desktop CPUs.

Point remains the same. Bios Firmware 1.26 does not update the microcode to 4123 so unless you manually apply it through your host OS or other means, you're MS-01 with a 06_BAH CPUID is open to CPU degradation.

Affected Processors: Transient Execution Attacks & Related Security...

Review the impact of transient execution attacks and select security issues on currently supported Intel products.

www.intel.com

 

[cj2]

Point remains the same. Bios Firmware 1.26 does not update the microcode to 4123 so unless you manually apply it through your host OS or other means, you're MS-01 with a 06_BAH CPUID is open to CPU degradation.

Point is you are incorrect.

The link you provided only lists the latest MCUs for security-vulnerability fixes. Where does it say that 0x4123 MCU for their mobile family fixes CPU degradation issues?

The CPU degradation problem only affects the 13th/14th gen Desktop CPUs, not their mobile CPUs. In fact, they also suggest the crashes on their mobile processors are related to other issues as Intel mentioned here.

Ever since I switched to 1.26, it has been super-stable compared to Miniforum's earlier versions.

 

[myn]

Point is you are incorrect.

The link you provided only lists the latest MCUs for security-vulnerability fixes. Where does it say that 0x4123 MCU for their mobile family fixes CPU degradation issues?

The CPU degradation problem only affects the 13th/14th gen Desktop CPUs, not their mobile CPUs. In fact, they also suggest the crashes on their mobile processors are related to other issues as Intel mentioned here.

Ever since I switched to 1.26, it has been super-stable compared to Miniforum's earlier versions.

Oh interesting. The folks over here believe its also the mobile chips impacted by this as well. But feel better knowing at least Intel has indicated formally that mobile isn't impacted.

I am not sure at this point who to believe

[INTEL]-How To Update Your Microcode for Intel HX 13/14th Gen. CPUs Laptops/Mobile Easily.

Let me start with a small background info... Since we know all Intel's fiasco about what is happening with Raptor Lake/Raptor Lake Refresh which is Intel's codename for the 13th and 14th generations of Intel Core processors, Most OEM/Vendors doesn't want to provide BIOS update that includes...

www.techpowerup.com

 

[cj2]

Oh interesting. The folks over here believe its also the mobile chips impacted by this as well. But feel better knowing at least Intel has indicated formally that mobile isn't impacted.

I am not sure at this point who to believe

Yeah, but that thread is a bunch of anecdotal "degradation" on HX mobile CPUs. It could be due to overheating, laptop design/manufacturing flaw, BIOS flaw, or user-modified, out-of-spec overclocking, who knows... They're over there trying to establish a conspiracy theory that the desktop CPU degradation also affects HX mobile CPUs, when Intel clearly said the Vmin shift issues that are causing instability/degradation on their desktop CPUs don't affect mobile CPUs. Unless we see actual root cause analysis of these failures or we hear from Intel regarding HX CPU fixes, it's a nothing-burger. Besides, the MS-01 doesn't even use the HX CPU.

What I would suggest is to stop worrying about who to believe. The most important thing is to have a stable working system you can use. Initially, I thought the desktop CPU gradation affected the MS-01, too, because MS-01 was way too unstable and required power cycles to recover from a hang. It wasn't until I upgraded the BIOS to v1.26 did all my MS-01 problems go away and have not had a hang/crash since. That's what most important to me: stability.

 

[hostinglocal]

Hi, I'm trying to setup two proxmoxservers with two MS-01's, but its a bumpy road to say the least.
For the moment I'm blocked because there are some networksettings stored in AMT, and I cannot enter it anymore (don't know password, tried anything, probably a keyboardlayout issue). It took me some weeks, but now I know thats the reason my setup won't do what I say.

As I can't find any way to reset AMP/vPro or the password, I at least want to try to update the BIOS.
I did all the steps described here, but run into "error 30: unable to open specified file."
In UEFI Shell I used 'map' to find my usb stick, I enter the reference of my USB-stick. (it doenst do anything, just gives me a new prompt without saying anything). After that I enter 'AfuEfiFlash.nsh', and recieve that error. commands like 'ls' and other documented UEFI shell commands don't allways work by the way. Its like a very basic version of UEFI-shell.

So I would want to know a solution for flashing the BIOS, and or, to reset AMT so I can reconfigure my networkadapters in Proxmox to the IP's they need.

I hope someone can help. I started with a destroyed proxmoxcluster 2 months ago, and narrowed it now down to this. What a journey...

Kind regards,
Thomas

 

[JamfSlayer]

So, under a load, even with Windows Server 2025 Feb ISO, this thing pukes back to the bios screen under a heavy load, like Hyper-V doing heavy replication. Opened a case with Minisforum, and they're trying to tell me I have a bad 990pro 4tb. I don't think that's the case, and I'm on BIOS V1.26, it ran for a couple months without issue, but then failed again, when I had a channels DVR server running on it that was pretty CPU intensive. Has the issue regularly with 1.22. I even as a measure re-did the CPU paste, which you should do anyway with one of these. Ran a solid month after the paste change, but started to barf again. I cannot run this in a "pseudo-prod" role until this is figured out. I had high hopes for this machine, but until this instability is corrected, I can't rely on it, and until it's stable, it's simply a very powerful backup server lol

 

[Lethos]

If anyone is reading this and the previous posts have not fully helped with regards to updating the MS-01 BIOS, here is what did the trick for me:

• Formatted USB Drive as FAT32 (using Rufus on Windows, using MS-DOS bootable option and selecting UEFI - this will land some un-necessary files on your USB drive like autorun, etc. but they won't hurt anything)
• Copied over the 1.26 BIOS files to the root of the USB Drive
• ***Downloaded shell.zip from the bottom of this site, extracted and copied shell.efi to the root of the USB Drive (prior to doing this, I could not boot off of the USB and nothing would happen when I selected the UEFI Shell from the BIOS menu, it would just flash briefly and do nothing. I'm sure you can get shell.efi from elsewhere but this worked for me). 10/26 EDIT: Official/Clean build of shell.efi here (courtesy of @Avamander)
• Either boot using F7 at MS-01 power-on or select the UEFI shell from the BIOS
• Change into your USB directory (you cannot use 'cd', 'dir' or 'ls' commands, simply type the drive letter designation and press enter (for me it was FS0: ) <-that's a zero at the end and not an O as in oscar.
• Type this file name and press enter to start the BIOS update: AfuEfiFlash.nsh

Hope this helps.

Thank you good Sir

 

[Magsy]

So, under a load, even with Windows Server 2025 Feb ISO, this thing pukes back to the bios screen under a heavy load, like Hyper-V doing heavy replication. Opened a case with Minisforum, and they're trying to tell me I have a bad 990pro 4tb. I don't think that's the case, and I'm on BIOS V1.26, it ran for a couple months without issue, but then failed again, when I had a channels DVR server running on it that was pretty CPU intensive. Has the issue regularly with 1.22. I even as a measure re-did the CPU paste, which you should do anyway with one of these. Ran a solid month after the paste change, but started to barf again. I cannot run this in a "pseudo-prod" role until this is figured out. I had high hopes for this machine, but until this instability is corrected, I can't rely on it, and until it's stable, it's simply a very powerful backup server lol

This may or may not be useful but I have the same issue with 990 pro 4tb, server 2025 and HyperV replica. High replica load (resyncs) and it dies. I did send the SSD back but they stated it was healthy. Any other SSD including 2.5 u2 NVME is fine. I moved the 990 pro elsewhere.

i am not using ms-01 but another mini server - my conclusion is perhaps its using more power than can be supplied on the m.2 3v3 rail.