0

So I have a wifi driver (the adapter is a Qualcomm Atheros qca9377 for reference) which is apparently just an executable file (QcomWlanSrvx64.exe), it doesn't show up at driverquery nor can it be seen on windows services. and the worst part is that it starts up really late after bootup (2-3 minutes after login, sometimes worse) and this can get really infuriating. I need a way for this executable to start earlier during bootup, but how am I supposed to do this? Also, if there is a simpler alternative please let me know. Thanks in advance.

5
  • That appears to be a service. Can you confirm?
    – Ramhound
    Oct 20 at 11:45
  • The fastest way I've managed to get something to run is to create a scheduled task with the trigger "at login of any user". It's still quite slow to start after login, but not as much as 2-3 minutes.
    – Richard
    Oct 20 at 11:46
  • If it is running as a service (which it should be) try updating the driver.
    – John
    Oct 20 at 12:16
  • I rechecked, there's "AtherosSvc" which is apparently handling bluetooth, with path to executable being C:\Program Files (x86)\Bluetooth Suite\adminservice.exe, there's also a "WLAN AutoConfig" with C:\WINDOWS\system32\svchost.exe -k LocalSystemNetworkRestricted -p being its path to executable, there doesn't seem to be anything directly linked to this issue there
    – Iammethe24
    Oct 21 at 1:20
  • I figured out something, it apparently only happens when I boot up Windows after using Ubuntu. It works fine otherwise, but I need to switch between them quite a lot. Windows is still booting up via Windows Boot Manager, if I need to boot up Ubuntu I would need to press F12 to enter the boot menu than selecting GRUB there, which is listed as Ubuntu. I still don't know what really is causing this, and how I can fix it
    – Iammethe24
    Oct 21 at 1:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.