Windows 11 / Bios update?
- Thread starter romah
- Start date
pusb87
Trusted Helper
Yes, Ive just done mine
https://files.theminixforum.com/shared/bios/G41V-4 Max BIOS v0.18.rar
to clarify, I have just updated the BIOS, but not yet updated to Win 11
Last edited:
notrui
Trusted Helper
MINIX Drivers for G41V-4/G41V-4 max are not available.
BIOS update is available and working (For both G41V-4 and max) :
Check Link - post #2
MINIX - Alex
Staff member
The driver of the G41V series is the driver of the J50C series. The two drivers are the same.
https://theminixforum.com/index.php?threads/j50c-4-plus-windows-10-bit-drivers.4135/
notrui
Trusted Helper
Ok. Thank you ?
I didn't know that.
notrui
Trusted Helper
It is up to you install windows 11 or stay with windows 10.
My advice:
1- if you are going to install win 11 first do a backup
2- update BIOS and use windows update or update from scratch: (Minix image here)
https://files.theminixforum.com/sha...x-Win11_Pro_21H2-Multi_languages-20211112.zip
3-don't use Internet untrusted win11 images
4-another option is to install win 11 from Microsoft website and then install the drivers
Note:
-more storage is recommended (SSD)
-end of windows 10 support (October 14th, 2025)
Last edited:
pusb87
Trusted Helper
I would use Windows update
I have a Neo G1V-4 (not MAX version). It has BIOS version 5.13 (GMLOC 0.10 x64 -see the attached image). I downloaded the GMLOC 0.18 file and tried to update the BIOS to make it ready for Win11 upgrade. I got the following warning from AfuEfix64.efi (see the image). It says:
The ROM file information does not match with the system BIOS!
If forcedly update BIOS, it may destroy the system BIOS!
We strongly do not suggest to flash the BIOS!
I used the "A" option to jump out. Do you know what is wrong? Am I doing something wrong? Is it safe to force the update?
The ROM file information does not match with the system BIOS!
If forcedly update BIOS, it may destroy the system BIOS!
We strongly do not suggest to flash the BIOS!
I used the "A" option to jump out. Do you know what is wrong? Am I doing something wrong? Is it safe to force the update?
Attachments
Last edited:
Villa
Administrator
As far as I'm aware you should be alright selecting "E"
I don't know why these warnings appear but they seem to for most of the BIOS updates for MINIX devices?!
I believe this normal, see image 6 from this post:
https://theminixforum.com/index.php?threads/neo-j50c-4-bios-verison-0-15.2169/post-15201
Thanks for the quick responses. looking at the dates on the different files/folders in the downloaded file, it seems that most of the files including the Release_Note are old files and were not updated. It seems that the GMLOC018 is the new file added. I have not done the update yet so I don't know if the update will change the GMLOC version from 0.10 to 0.18 and leave the BIOS version as 5.13. It is likely that the BIOS version 5.13 has a size or checksum for the GMLOC file that is different for 0.18 from 0.10 and that is what the updater is complaining about.
For some reason the system is not letting me see image 6 in the posting that Marty had mentioned. Can you tell me what it shows?
Also, do you know what the difference between option "E" and "F" is? both seem to perform the command but "F" says "will be forcing ..."
For some reason the system is not letting me see image 6 in the posting that Marty had mentioned. Can you tell me what it shows?
Also, do you know what the difference between option "E" and "F" is? both seem to perform the command but "F" says "will be forcing ..."
Last edited:
Thanks Marty. It is exactly the same message. I noticed that the parameters used in this posting (/p /n /x) is slightly different from the one in the script that I used (/p /n /x/ /l). I looked up the AfuEfix64.efi command and the /l parameter is for "Program all ROM Holes". I still don't feel comfortaable doing this fearing that it can kill the PC I wish Minix would release a complete .exe or .efi package with all the right updated files and release notes etc. to let everyone do this with more confidence. Does anyone know if that work is in progress?
I wish Minix would release a complete .exe or .efi package with all the right updated files and release notes etc. to let everyone do this with more confidence. Does anyone know if that work is in progress?
Villa
Administrator
I can't remember if I already updated my G41V-4 BIOS. If I did then it went well as it did for @pusb87 and @notrui .Thanks Marty. It is exactly the same message. I noticed that the parameters used in this posting (/p /n /x) is slightly different from the one in the script that I used (/p /n /x/ /l). I looked up the AfuEfix64.efi command and the /l parameter is for "Program all ROM Holes". I still don't feel comfortaable doing this fearing that it can kill the PC
But I will check!
If I haven't I will do it. I'm sure it will be OK as I know I have updated several J50C-4 and they have updated just fine having displayed the same warning.
pusb87
Trusted Helper
yes, no issues updated fine using "E" option.
Now running Win11 after using Windows update
notrui
Trusted Helper
No issues as well.
First i updated the BIOS and after that i installed windows 11.
The only minor concern is that now “sysinfo” reports the main board to be “Minix G41V-4 Max” and my PC is not a Max version. I don’t know what the difference between the old version and Max version is but hopefully this will not be a problem.
Villa
Administrator