F5F Stay Refreshed Hardware Desktop Unable to modify my profile – Gigabyte B450 Aorus ELITE (version 1.0)

Unable to modify my profile – Gigabyte B450 Aorus ELITE (version 1.0)

Unable to modify my profile – Gigabyte B450 Aorus ELITE (version 1.0)

N
Niclin13
Member
193
09-25-2018, 08:32 AM
#1
The situation matches what was talked about two years back. No fix has been found yet. Someone might have a workaround for this issue?
N
Niclin13
09-25-2018, 08:32 AM #1

The situation matches what was talked about two years back. No fix has been found yet. Someone might have a workaround for this issue?

J
jupe36382
Junior Member
14
09-27-2018, 09:51 AM
#2
If you attempt the latest update, F60, it will check whether your flash drive uses FAT32 formatting.
J
jupe36382
09-27-2018, 09:51 AM #2

If you attempt the latest update, F60, it will check whether your flash drive uses FAT32 formatting.

M
mackattackar
Junior Member
17
10-04-2018, 07:52 PM
#3
Yes, you can access information from @bios within Windows.
M
mackattackar
10-04-2018, 07:52 PM #3

Yes, you can access information from @bios within Windows.

K
KTHEDEVASTATOR
Junior Member
16
10-06-2018, 04:41 AM
#4
Fixed! The issue stemmed from additional files and folders on my thumb drive that were interfering with performance. The drive used FAT32, so I reformatted it again as FAT32 and simply copied the BIOS file B450AE.65A. When I proceeded with the update, I accidentally downloaded the wrong version. During the "Update BIOS" process, I encountered a "BIOS ID check error," which is the expected behavior. Once the correct file was loaded onto the drive, everything functioned properly.
K
KTHEDEVASTATOR
10-06-2018, 04:41 AM #4

Fixed! The issue stemmed from additional files and folders on my thumb drive that were interfering with performance. The drive used FAT32, so I reformatted it again as FAT32 and simply copied the BIOS file B450AE.65A. When I proceeded with the update, I accidentally downloaded the wrong version. During the "Update BIOS" process, I encountered a "BIOS ID check error," which is the expected behavior. Once the correct file was loaded onto the drive, everything functioned properly.