Gateway DX4850 bios update via Windows prior to Tumbleweed install:
Hi, I have a question about updating the BIOS on a Gateway DX4850 machine with Windows 10 operating system installed. The installer here > https://www.acer.com/us-en/support/product-support/DX4850 Which I have placed and then (installed on win10 on the machines drive and once envoked), does not *offer* a bios update path from P01-A3 *to* P01-A410 . P01-A3 is current bios on Acer DX4850 ....hard to get BIOS to P01-A4...... your suggestions are very helpful due to bios utility run in Windows usually offer a more easy bios update road then say flashrom.... -Seasons Best🫥
On 12/13/24 7:41 PM, -pj via openSUSE Users wrote:
Hi, I have a question about updating the BIOS on a Gateway DX4850 machine with Windows 10 operating system installed. The installer here > https://www.acer.com/us-en/support/product-support/DX4850
All I see there is the Acer-Updater app listed (may be my browser settings) Generally bios updates are distributed in a .zip bundle that requires you unzip and extract the bios and installer. Presuming you have done that and have attempted running the installer, the only thing I can think of is that Win10 itself is preventing the bios updater from running if the installer isn't signed by Microsoft or is signed with a key that has expired. If that is what you are facing, you should be able to enable "Developer Mode" and then run the installer without windows complaining. Also make sure however you are starting it has been "run as administrator". Those are the only windows guesses I have... -- David C. Rankin, J.D.,P.E.
Generally bios updates are distributed in a .zip bundle that requires you unzip and extract the bios and installer. Presuming you have done that and have attempted running the installer, the only thing I can think of is that Win10 itself is preventing the bios updater from running if the installer isn't signed by Microsoft or is signed with a key that has expired.
If that is what you are facing, you should be able to enable "Developer Mode" and then run the installer without windows complaining. Also make sure however you are starting it has been "run as administrator".
Those are the only windows guesses I have...
Thank you for responding, I was able to activate "Developer Mode". Then proceeded to execute the .exe (bios update) as administrator, the *gear* is displayed as spinning and nothing more (displayed on the Desktop Environment... Are you aware of a Powershell command or something like that which may allow me to see what is being done while the *gear* is spinning when attempting to execute the .exe bios update? -Seasons Best🫥
On 12/14/24 2:29 PM, -pj via openSUSE Users wrote:
Are you aware of a Powershell command or something like that which may allow me to see what is being done while the *gear* is spinning when attempting to execute the .exe bios update?
Not a powershell command, but Task Manager "Details" or the full blown Windows Performance Monitor will show in detail what is happening. You can sort the running processes by CPU use. Also bring up with Windows Event Viewer and you should be able to watch the startup and catch any log entries. I'd just start the "Command Prompt" as administrator and run the .exe file there. Then you will see the output to stdout and stderr (which it may be waiting on you to confirm (y/n) something.... Yes, there are installers that are gui as well, but I've always preferred the command line for bios updates, etc... Good luck! -- David C. Rankin, J.D.,P.E.
Cannot seem to update bios from A09 to A13 on Inspiron 660s.. Do you think Win11 is holding up the process? Process displays a 'successful' message though. After powercycle + bios entry, no joy. Going to reread and look more deeply into suggestions on viewing output.. as bios installer executes....
On 12/14/24 4:27 PM, -pj via openSUSE Users wrote:
Cannot seem to update bios from A09 to A13 on Inspiron 660s.. Do you think Win11 is holding up the process? Process displays a 'successful' message though. After powercycle + bios entry, no joy. Going to reread and look more deeply into suggestions on viewing output.. as bios installer executes....
Oh, That's a big "dunno?". I've managed to steer clear of Win11 so far, and with the kids out of the house, will likely be able to stay clear of it as well. Bios installers are pretty good at not displaying "successful" unless the write of the required number of bytes to the bios has actually succeeded. I don't have a lot of "new" hardware, I simply don't have any need for it. Yes, AVX512 extensions would be nice for C, but AVX is fine. Now newer bioses (those withing the past 8-10 years, often have copies of the actual bios code stored to provided a way to recover if something goes wrong. It would be worth going though your bios carefully to see if there isn't more than one copy and whether the copy to use can be selected. These are educated GUESSES. So don't take this a gospel. -- David C. Rankin, J.D.,P.E.
That's a big "dunno?". I've managed to steer clear of Win11 so far, and with the kids out of the house, will likely be able to stay clear of it as well.
Bios installers are pretty good at not displaying "successful" unless the write of the required number of bytes to the bios has actually succeeded.
I don't have a lot of "new" hardware, I simply don't have any need for it. Yes, AVX512 extensions would be nice for C, but AVX is fine.
Now newer bioses (those withing the past 8-10 years, This bios is 2012 often have copies of the actual bios code stored to provided a way to recover if something goes wrong. It would be worth going though your bios carefully to see if there isn't more than one copy and whether the copy to use can be selected.
These are educated GUESSES. So don't take this a gospel.
Thank you for responding David. I created a post here > https://www.dell.com/community/en/conversations/inspiron-desktops/inspiron-6... -Seasons Best🫥
participants (2)
-
-pj -
David C. Rankin