ASRock.com Homepage
Forum Home Forum Home > PC Modding > Project Build & Share
  New Posts New Posts RSS Feed - Request UEFI setting restore after update
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Request UEFI setting restore after update

 Post Reply Post Reply
Author
Message
MihaMarkic View Drop Down
Newbie
Newbie
Avatar

Joined: 10 Nov 2025
Location: Slovenia
Status: Online
Points: 60
Post Options Post Options   Thanks (0) Thanks(0)   Quote MihaMarkic Quote  Post ReplyReply Direct Link To This Post Topic: Request UEFI setting restore after update
    Posted: 15 hours 2 minutes ago at 1:07am
Hi, here is my post.

Topic: Making easier to preserve BIOS settings during upgrade.
Body: For me the biggest pain when upgrading BIOS is to manually reapply the settings that I changed before - IOW, non default ones. Or better, the biggest pain is to list them all. Sure, there aren't many but nevertheless.
So, I understand it might be tricky for the upgrade process to re-apply those and that's fine. However, please give as at least a feature that would output all the non default ones to a file or at least to a screen. That way it'd be much easier to reapply them. Or such a feature already exist?
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 30928
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 11 hours 49 minutes ago at 4:20am
The issue has been discussed here before and ASRock has probably had requests like
this many many times. It used to be possible in the days of the actual "BIOS" but
UEFI is infinitely more complex and intricate. From what I understand it is all
but impossible to "reload" settings from a previous UEFI version after an update.
The key issue is that motherboard manufacturers are not responsible for the core
of the UEFI, that comes from Intel and AMD. Each manufacturer adds a level of customization
to the UEFI but it is mostly just surface level tweaks like hiding or exposing
settings, voltage limit changes etc.

I am pretty sure this will never happen given the function would break every time
there is a new core UEFI update from AMD/intel (AGESA etc).
Back to Top
MihaMarkic View Drop Down
Newbie
Newbie
Avatar

Joined: 10 Nov 2025
Location: Slovenia
Status: Online
Points: 60
Post Options Post Options   Thanks (0) Thanks(0)   Quote MihaMarkic Quote  Post ReplyReply Direct Link To This Post Posted: 49 minutes ago at 3:20pm
Hey, so this feature would be more in an AMD domain then, fair enough.
About the difficulty - from my perspective (as a developer), the settings are a dictionary of key-value pairs. Of course values can be nested. I don't see a big deal of saving this dictionary to an XML text file with all the values and with attributes specifying when a value is a non default.

This step seems trivial to me and it'd solve 90% for me.

Once you have the settings in this format, there could be an option to reapply the non-default ones and a warning during process if the affected property has changed somehow. Honestly, I don't see this a big issue as well. At the end of the day it'd be the same as if user manually applied old non-default values, just in more automated way.
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 30928
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 16 minutes ago at 3:53pm
That is the issue, many of the settings are not simply value=on/off etc. They have
dependencies and these can be completely different from one version to the next.
Can it be done? Probably, but the amount of effort that would be required to ensure
a smooth import with every single new version would be non viable. You need to
understand that the enemy of any tech manufacturer is instability. Complexity is
absolutely not something you want to introduce. If even 1 in 1000 users were to
experience a catastrophic failure due to a mistake implementing loading saved
settings that could be thousands of support hours wasted over 100k boards.

It is easy to see solutions to things we would like when we only consider ourselves
but once you start to factor in the labor, potential for mistakes and subsequent
support labor needed to address the issue it becomes clear why manufacturers prefer
to keep things simple rather than add complexity and points of failure. Also there
is the issue that implementing a feature like this has no benefit to the manufacturer.
They will get nothing for the labor and time spent developing it. Perhaps as a
selling point for a new product line it may have some viability but if there is
even a single bad review on youtube about the feature that value is gone too.

As I said, this discussion has been had here before. I don't disagree that it would
be a nice feature to have, it's just not a practical one I can see any manufacturer
wasting time and resources on.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.125 seconds.