Hi! For the past few weeks, I have an ongoing problem with the Intel(R) Wireless-AC 9560 160MHz network adapter on my ZenBook UX450FDX.313 (running Win11 Pro 64-bit 10.0.22621).
Problem: As soon as I enable the bluetooth adapter by installing a driver, it will cause the wifi adapter to stop working after the next boot, generating a code 10 error. The problem is easily reproducible.
Temporary fix (that I do not like): As soon as I uninstall all bluetooth driver files and shift-shut down/reboot the computer, the wifi connection works fine again, but obviously I don't have bluetooth then. Also, I have to disable Windows Update, as this immediately installs a bluetooth driver, which would again kill the wifi. So this is not a solution.
Steps: 1. disable Windows Update 2. uninstall all bluetooth and wifi drivers 3. Shift+shut down PC, reboot. The bluetooth adapter is now an unknown hardware device in the device manager 4. Install wifi adapter driver (both original OEM driver and latest generic Intel driver 22.214.171.124 work). > The wifi now runs stable, but no bluetooth and no Windows Update 5. installing any bluetooth driver (both OEM driver and latest generic Intel driver) enables bluetooth, but after the next reboot wifi is gone with a code 10 and bluetooth is gone too (no error here, bluetooth just disappears in the device manager). So I have to start again with step 2.
I tried multiple drivers, multiple driver combinations, a clean (un)install of the drivers, MyAsus support, Windows troubleshooting, updating everything I found, BIOS is up to date, Windows is up to date, un/reinstalled Windows, .... . Nothing has worked so far. Any ideas?
@FongPoui, no didn't see this, good find! That is exactly the issue that I'm experiencing here. From closely watching Windows Update I also already had the feeling that this Intel Extension driver could be part of the problem. Anyway, from what those people write, it doesn't look to promising - even the ones that sent their laptop to ASUS for service didn't have it solved afterwards (I might still do that though, @Falcon_ASUS). I did a full reset yesterday (in fact 2 full resets, after the first one didn't work), but it didn't solve the problem. I can still "solve" it the way described in post #1, but again, the fix won't survive a restart.. could this be BIOS-related maybe? I believe that I also updated BIOS to the current version around the time this issue occurred for the first time. Is there a way to downgrade BIOS to an earlier version (maybe by actively screwing up an update? :))
Thread automatically closed due to inactivity. If the reported issue has not been resolved or you require further assistance from one of our moderators, please create a new thread and we will be with you shortly.