[SOLVED] Chipset question

[lumpy95]

I have a Gigabyte x470 Aorus Gaming 7 Wi-Fi MB (Rev.1.0) with AMD Ryzen 2700X cpu.
Currently BIOS is F5 (chipset 17.12) and I want to update the BIOS to the latest BIOS F8. There is a note on the BIOS following F5 saying that the chipset needs to be updated to 18.10.20.02 before updating the BIOS.
I tried just downloading the chipset 18.10.20.02 previously and unzipping it and running the setup.exe file but it still showed chipset 17.12 in Control Panel> Programs and Features.
Note: the chipset 18.10.20.02 is no longer listed under chipsets, only the 17.40 but I have the 18.10.20.02 already downloaded from before they evidently pulled it so I'm a bit confused as to what is going on, see attached
This may be a stupid question but do I need to uninstall the 17.12 chipset before running the 18.10.20.02 chipset setup or should I abandon the 18.10.20.02 and just worry about 17.40???
What happens if I uninstall the current chipset driver? I guess the bottom line is do I need to uninstall the current chipset before installing an updated chipset which ever one it is?
I'm pretty confused at this point since they require 18.10.20.02 at one point but have evidently pulled it now.
Thanks for any response.

 

[Digerati]

Are you having problems? I don't update a BIOS unless it addresses a problem I am having. Most BIOS updates just add support for new CPUs or RAM that came out after the board left the factory.

Beyond that, I see date of that 17.40 chipset is just 2 days ago - and now we are into the weekend. I might wait a couple days to see if they update the instructions and make them more clear. You might flick their tech support a note asking them to clarify too.

 

[lumpy95]

I might wait a couple days to see if they update the instructions and make them more clear. You might flick their tech support a note asking them to clarify too.

Previously I asked Gigabyte tech support about the 18.10.20.02 installation that I tried and their explanation was that chipset 17.12 was correct and the 18.10.20.02 was a "Chipset Package" but they couldn't/wouldn't explain why the "chipset package" didn't show up anywhere as installed or failed or anything. There was a log file for it but I couldn't make heads/tails of what it meant and I sent it to them and it was ignored. From the answers to questions that I have gotten from Gigabyte support, they either don't know much or are not interested in being very forthcoming with answers/explanations.
As to Chipset 17.40, it has been available on the support site for quite some time, I don't have a clue as to why the date was changed on it.

Are you having problems? I don't update a BIOS unless it addresses a problem I am having

I was just looking at the "USB Enhancements" for F8 because the USB-C 3.1 Gen2 connector on the I/O shield doesn't seem to work correctly, it doesn't recognize anything plugged into it. So I was hoping that F8 would possibly address that issue.
The wireless on this MB has never worked correctly since first building this computer and I have RMA'd the MB twice and they say that it tested fine for them although it will not work here in my home even though every other wireless device works just fine here. I had another thread dealing with WMI errors that DMcCoy had me run a bunch of test's for the wireless and he came up with the conclusion that it was a hardware problem.
Anyway, if I do try to update the chipset, do I need to uninstall the current 17.12 chipset before updating to a newer chipset or should the newer chipset install over the old one??

 

[Digerati]

From the answers to questions that I have gotten from Gigabyte support, they either don't know much or are not interested in being very forthcoming with answers/explanations.

They are like most tech support people these days. They are under-trained and under-paid. They just follow a checklist and are not allowed to deviate from it - even if they knew how. That's not just Gigabyte either.

As to your question, I have never had to uninstall a driver before updating.

 

[lumpy95]

Thanks
So I'll wait a few days and try to update the chipset over the old one. I guess it would be prudent to set a restore point before doing that and to clone my M.2 SSD C drive.
Just my POV but I always used ASUS MB's in the past and never had a problem but from what I have read, Gigabyte seemed to have a good reputation and I liked the features on this MB. Unfortunately I am no longer keen on Gigabyte.

 

[Digerati]

I guess it would be prudent to set a restore point before doing that...

I would sure make a backup of any data you don't want to lose - always wise before flashing the BIOS. But it is important to remember this update is at the hardware level and takes place well before the operating system is even touched during the boot process. This means if the flash fails and "bricks" your motherboard (extremely rare these days, but still remotely possible), a restore point will be useless.

 

[lumpy95]

After looking at the BIOS updates, I noticed that F8 has no note about 18.10.20.02, I'll bet that the 18.10.20.02 is just to update AGESA from 1.0.0.4 to 1.0.0.6. I guess I'll have to google AGESA to see if I'm concerned about it.
Also there seem to be a number of updates on the support site with new dates on them and noting that they support Ver. 1809. I'm still on 1803 and have set Group Policy to (hopefully) stop 1809 for awhile until it smooths out.
I think I'll hold off for awhile before going to F8. The computer seems to be running ok with the ethernet instead of the wireless at this point.
Good point about system restore on a BIOS update.

 

[lumpy95]

Actually I had kinda forgotten about this thread until TeraWales posted. You can delete that last post of mine if you want (#8).
Any way, as a followup, I updated to F8 and the update actually brings the AGESA up to 1.0.0.6 by itself. I also updated the chipset with the 17.40 chipset offered (it was 17.12 before) and as it was updating the chipset looked like it checked online for a newer version and low & Behold it updated to 18.40.20 during the process.
All seems to be working well except for the USB 3.1 Gen 2 "C" connection (on the MB I/O at the back) when I plug a drive into it. It worked fine when I plugged my Android phone into it though.

 

[Digerati]

I am glad it finally updated. Thanks for your follow up.

PS - I deleted your post and mine.

 

[lumpy95]

I guess this has run it's course on the chipset.
Hmmm, I no longer see a way to mark this as solved. Things have changed since I was here last.