Slow WiFi until Change Setting On Adapter. Then Eventually Slows Again

Page 2 of 2 FirstFirst 12
  1. Caledon Ken's Avatar
    Posts : 20,267
    Windows 10 Pro x64 Version 1909
       #11

    Changing setting causes adapter to reset to apply that change. This would not happen if you disconnected and reconnected.

    In advance power setting under Wireless Adapter Settings is everything set to maximum performance.

    Are your test done connected to power or on laptop battery operation?
      My Computer


  2. Posts : 7
    Win 10 Pro
    Thread Starter
       #12

    Hey all,
    I have finally figured it out and fixed the issue.

    I decided to try an ipconfig /all before and after changing a setting on the adapter. I have listed the output below and highlighted the difference.

    The difference is an item called "Microsoft Wi-Fi Direct Virtual Adapter". Apparently, this is related to a setting in Windows 10 called "Projecting to This PC".

    For some reason, after I first boot this virtual adapter is active, but as soon as I change a setting on the Killer adapter, the Killer adapter restarts and the virtual adapter becomes a hidden device. It's still enabled but hidden.

    I have disabled the virtual adapter and my problem is solved. I have no idea why it was hobbling my WiFi but it was.

    Thanks everyone for the help, without your ideas, I doubt I would have ever got there.

    Cheers
    Mick



    The Wireless Section Before

    Wireless LAN adapter Local Area Connection* 11:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
    Physical Address. . . . . . . . . : 38-00-25-83-58-FC
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Local Area Connection* 12:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
    Physical Address. . . . . . . . . : 3A-00-25-83-58-FB
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::c136:88a6:f4bc:79ee%3(Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.121.238(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 641335333
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-20-26-55-B4-A9-FC-2A-89-6E
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled


    Wireless LAN adapter WiFi:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
    Physical Address. . . . . . . . . : 38-00-25-83-58-FB
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2002:d31e:fdef:e472:388c:8106:6d38:7b78(Preferred)
    Temporary IPv6 Address. . . . . . : 2002:d31e:fdef:e472:d82:cab6:f13c:dbba(Preferred)
    Link-local IPv6 Address . . . . . : fe80::388c:8106:6d38:7b78%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : 23 May 2020 3:40:38 PM
    Lease Expires . . . . . . . . . . : 24 May 2020 3:40:40 PM
    Default Gateway . . . . . . . . . : fe80::861b:5eff:fee3:afe2%11
    192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 87556133
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-20-26-55-B4-A9-FC-2A-89-6E
    DNS Servers . . . . . . . . . . . : fe80::861b:5eff:fee3:afe2%11
    192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    The Wireless Section After
    Wireless LAN adapter Local Area Connection* 11:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
    Physical Address. . . . . . . . . : 38-00-25-83-58-FC
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter WiFi:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
    Physical Address. . . . . . . . . : 38-00-25-83-58-FB
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2002:d31e:fdef:e472:388c:8106:6d38:7b78(Preferred)
    Temporary IPv6 Address. . . . . . : 2002:d31e:fdef:e472:d1c1:db56:16b3:c39(Preferred)
    Link-local IPv6 Address . . . . . : fe80::388c:8106:6d38:7b78%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : 23 May 2020 3:43:39 PM
    Lease Expires . . . . . . . . . . : 24 May 2020 3:43:41 PM
    Default Gateway . . . . . . . . . : fe80::861b:5eff:fee3:afe2%11
    192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 87556133
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-20-26-55-B4-A9-FC-2A-89-6E
    DNS Servers . . . . . . . . . . . : fe80::861b:5eff:fee3:afe2%11
    192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled
      My Computer

  3. Caledon Ken's Avatar
    Posts : 20,267
    Windows 10 Pro x64 Version 1909
       #13

    Excellent. Great detective work. Thanks for posting your solution.


    Could you mark your thread solved please, it helps other to find it.
      My Computer

  4. Paul Black's Avatar
    Posts : 2,653
    Win 10 Pro 64-bit v1909 [Customised]
       #14

    mikeyjames said:
    I have finally figured it out and fixed the issue.
    Thanks for sharing the solution!
      My Computer

  5. Compumind's Avatar
    Posts : 2,209
    Windows 10 Pro x64, Various Linux Builds, Networking, Storage, Internet Security Specialty.
       #15

    @mikeyjames -

    Oh, you had a Killer AX? I missed that. Sorry.

    You need to run their uninstaller and then re-run the install again.

    1) Use the Killer Uninstaller and reboot.
    2) Install the Killer Software Package.

    Killer Uninstaller support.killernetworking.com
    Killer Software Package Windows 10 1803+ support.killernetworking.com

    Glad that you solved it anyway, mate!



    P.S. When there is a new driver package release, use the uninstaller and then install the new package!
      My Computer


  6. Posts : 616
    Windows 10 - 1809
       #16

    Compumind said:
    Oh, you had a Killer AX? I missed that. Sorry.
    You need to run their uninstaller and then re-run the install again.
    1) Use the Killer Uninstaller and reboot.
    2) Install the Killer Software Package.

    Killer Uninstaller – support.killernetworking.com
    Killer Software Package – Windows 10 1803+ – support.killernetworking.com

    Glad that you solved it anyway, mate!


    P.S. When there is a new driver package release, use the uninstaller and then install the new package!


    Hi Compumind, I'm just curious, why is it necessary to use the Killer uninstaller first?

    I found it to be a PITA to locate the correct download package for my not so current Killer E2400 Gigabit Ethernet Controller.
      My Computer


  7. Compumind's Avatar
    Posts : 2,209
    Windows 10 Pro x64, Various Linux Builds, Networking, Storage, Internet Security Specialty.
       #17

    W10 Tweaker said:
    Hi Compumind, I'm just curious, why is it necessary to use the Killer uninstaller first?
    It's not necessary but I prefer it since it cleans out the previous install. Does a good job.

    The E2400 is listed...

    Killer Uninstaller support.killernetworking.com

    HTH
      My Computer


  8. Posts : 616
    Windows 10 - 1809
       #18

    Compumind said:
    It's not necessary but I prefer it since it cleans out the previous install. Does a good job.
    The E2400 is listed...
    Killer Uninstaller – support.killernetworking.com
    HTH
    Thanks for the update. I did find the files, I just didn't appreciate the somewhat ambiguous presentation. Maybe I was just having a slow day.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:31.
Find Us




Windows 10 Forums