ASUS TUF Gaming X570 Pro Wifi - Nearly no driver possible to install

dbam

Hello all,

i am really completely disapointed with my current system i bought.

I bought a AMD 5800X with a ASUS TUF Gaming X570 Pro WIFI + NVME Samsung 980 1TB M2 Gen4.

I managed to install windows by setting CSM active in the bios and also updared the BIOS to the latest version.

Now being in Windows 10 i have multiple problems with the ASUS drivers.

I took the ones from the CD but most of them simply do not istall. Especially the LAN driver constantly stops installation at 10% in the driver SW.

Going to the HW-monitor to update the driver manually it does not find any driver on the CD and also in the driver folder i downloaded on the intel page.

Getting the new drivers from ASUS page also does not help as i cannot install the LAN driver.

Only the chipset and the audio was ok.

Of course i did a new Windows install once again to see if it works afterwards but no.

Does anyone know what i could do?

Ian

Greetings, the LAN driver from here does not work? https://www.asus.com/us/Motherboards-Components/Motherboards/TUF-Gaming/TUF-GAMING-X570-PRO-WI-FI/HelpDesk_Download/

Do you get any sort of error message / error code when you try to install it? Do the drivers show up in Device Manager at all?

dbam

Hi!

No this driver does not work, same as the driver from CD. as the board has Wi-Fi I managed to install this driver in the device manager but still even being connected to the internet it does not find the right driver for LAN...

In the device manager I see the Ethernet with a questionmark on it but I can't find a driver when going to search.

No error message, only the message that it could not find the right driver.

Can this be some Bios setup? 

dbam

Or could it be that Windows needs to be updated first?

dbam

Ok the issue was really Windows. With the latest updates it worked. Strange because normally I need the network adapter to do Windows updates 😂
Good that the board has Wi-Fi....

Ian

I am glad to hear that worked out, reading over your latest post I figured we were looking at a Windows issue.