25 Posts

4642

December 8th, 2021 17:00

Aurora R9, Bios Update 1.0.15

I am attempting to update my R9 BIOS but have encountered the following. I have BIOS V: 1.0.14 however, I am receiving a NOTICE: "Running on an unsupported system."


Darqology_0-1639014478591.png

 

Please Advise.

 

Thank You.

9 Legend

 • 

15.2K Posts

December 8th, 2021 18:00

Dell bios update exe was not able to read your current bios for whatever reason.

flashing bios has inherent risk even with Dell recommended update (often labelled "urgent").  unless there is strong real urgent reason for your pc, think twice before taking a risk for nominal benefit of update that you may not need.  

25 Posts

December 12th, 2021 12:00

UPDATE:

I went ahead and flashed the BIOS to 1.0.15 via a USB through the F12 key on startup.  The system accepted the BIOS Update and it's recognized in the F2 Settings.  Interestingly, Alienware update system information and device manager do not recognize the updated BIOS as version 1.0.15 and still have it as 1.0.14. It is recognized through msinfo32 in cmd prompt though.  

Updating BIOS isn't for the faint of heart through the executable in windows and flashing the BIOS from the USB only adds additional anxiety for the unexperienced.  Even though it's an urgent update from the DELL site, I do recommend for BIOS Updates if it ain't broken, don't fix it.

Update BIOS at your own risk. You can brick your system even if unintentionally. 

2 Intern

 • 

396 Posts

December 9th, 2021 02:00

I noticed that under "System Information" your operating system is listed as APAC (Asian Pacific)...please make sure your BIOS update windows executable is the proper one for your location and also that it is not the .rcv file but the .exe file.  Hope this helps.

 

Community Manager

 • 

56.9K Posts

December 9th, 2021 08:00

This out of warranty Aurora R9 sold in the USA. I wonder if in this case APAC means something else?

2 Intern

 • 

396 Posts

December 9th, 2021 12:00

Curiouser and curiouser...well, I'm fresh out of bright ideas.

25 Posts

December 10th, 2021 21:00

Darqology_1-1639201725221.png

 

Msinfo32 shows the BIOS Version/Date: Alienware 1.0.14 9/6/2021.  There is no easily explainable reason as to why 1.0.15 will not install with the exe. I am on windows 11 too. 

2 Intern

 • 

396 Posts

December 10th, 2021 22:00

Just a thought, when I updated both BIOS 1.0.14 and 1.0.15 I used my trusty Rufus loaded USB drive, copied the BIOS update file, went through the Update BIOS section in the Boot Menu and presto--Windows 11 Pro with the latest Intel security updates in BIOS 1.0.15.

Although I have updated the BIOS through Windows in the past; it is not for the faint of heart...it just seems prudent to have the least amount of things going on when you flash a new BIOS.

25 Posts

December 10th, 2021 23:00

If anyone else has had this issue and updated the BIOS to 1.0.15 through the F12 function from the USB successfully, I’d be interested in hearing it. 

25 Posts

December 10th, 2021 23:00

I hear you on the RUFUS USB. I am not terribly worried about updating the BIOS, but so find it curious that the tools I have used verify the 1.0.14 BIOS version and yet the 1.0.15 executable update cannot verify it, as I have updated the BIOS through that method times before. This also occurred on windows 10 prior to upgrading to windows 11. Mostly curious to see if others are experiencing this same issue too. 

2 Intern

 • 

396 Posts

December 12th, 2021 13:00

Personally, I prefer HWiFO and CPUID CPU-Z for information...

Screenshot 2021-12-08 035224.png

Screenshot 2021-12-12 153136.png

25 Posts

December 12th, 2021 13:00

Now that is very odd that your Alienware update shows version 1.0.15 and mine does not. Perhaps it will just take a bit to show up. I do understand the driver situation the more I thought about it after your explanation and to be fair, I believe I've done the same thing as you have. I do periodically hit the update button on the drivers either in device manager or windows update optional driver updates and in the past this has worked fine.

The system is stable with no issues, so I think at the end of the day that's what counts.

Thanks for the replies and screenshots. 

2 Intern

 • 

396 Posts

December 12th, 2021 13:00

You are quite welcome...glad it all worked out.

2 Intern

 • 

396 Posts

December 12th, 2021 13:00

Now that is odd that Alienware update system doesn't realize what BIOS you are using...however, the device manager shows Windows drivers...not actual BIOS information, the Windows drivers BIOS seems to always be a few months behind the actual BIOS.  I don't know the details as to why they don't change together, just that they two different things. After a while I will hit "update driver" for the Windows BIOS driver as I have done several times in the past after upgrading the real BIOS...and magically it will load a new driver and show the same number as the actual BIOS.  Spooky, huh?

 

BIOS matches with actual BIOSBIOS matches with actual BIOS

Most confusing...isn't it?Most confusing...isn't it?

 

1 Message

December 23rd, 2021 03:00

I have exactly the same problem.

I've read through all the solutions and whilst they may work the point in my mind is that Dell/Alienware need to sort it out. 

There is no point having an executable which downloads via an automated update service which does not work.

It's shoddy and clearly untested, which does not inspire confidence in the update.

Dell, sort it out please...

25 Posts

December 23rd, 2021 13:00

Agreed. If there's a method (the executable) that has worked before and been created to avoid USB Flashing, it needs to work. It should work. The End.

We the beta testers. We the support.

No Events found!

Top