Hi i'm having problem with this card and honnesly it already worked with older microsoft drivers and now it doesn't anymore.
I tried to roll back but can't make it work anymore.

Channel width 5.2ghz auto just won't stay connected more than few seconds.

At 20 mhz it'S more stable but i bought the card for ac speeds...

Just an FYI for anyone interested. I have a Intel AC 7260 dual band wifi card in my Zotac ID90.

"Wifi Proset" Windows 10 64b.

New Driver Version - 18.33.11.2

here is the ssu file

My router is a netgear x10 r8900 and also had netgear r7000. Same result, the problem is in intel drivers because it already worked.

Thanks for your help.

When booting Linux, the Linux drivers upload firmware build 103 to the Bluetooth part of my Intel AC 8265 wireless adapter. Build 103 seems to be the latest one available to Linux users:

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=1dcf7691f623c24762976e2debe05248d627e814

Then, when rebooting the into Windows, the Windows driver doesn't work. In the device manager, the Intel Bluetooth device is marked with a yellow triangle and STATUS_DEVICE_POWER_FAILURE is shown as an error message when checking the properties of the device.

When booting to Windows first, a subsequent reboot to Linux reports that the firmware of the Bluetooth adapter is build 107. My best guess here is that the Windows driver won't accept build 103 and thus refuses to work with it. It seems like the Windows driver does not or cannot upgrade the device firmware to build 107 if build 103 has already been uploaded. Ideally it would simply reset the device and upload whatever firmware it comes with.

Is this a known issue?

How can this issue be resolved?

How is the Windows driver supposed to behave in a dual boot environment?

I actually have the Problem that I'm unable to use Bluetooth at my MSI CX61 Laptop. I installed the Drivers that the Intel® Driver Update Utility said but after I installed the drivers it's still said that the drivers were already up to date.

I already ran the Bluetooth troubleshooter and it says that my device does not have Bluetooth.

Please help me.

Hello,

Using the ONLY driver for the 9260 I cannot get this to work on my laptop (HP Envy x360).

I get the following error's in event viewer:

Event 5000, Netwtw06

     Intel(R) Wireless-AC 9260: Has encountered a conflict in resources and could not load.

Event 5001, Netwtw06

     Intel(R) Wireless-AC 9260: Could not allocate the resources necessary for operation.

Event 5002, Netwtw06

     Intel(R) Wireless-AC 9260: Has determined that the network adapter is not functioning properly.

Event 5003, Netwtw06

     Intel(R) Wireless-AC 9260: Could not find a network adapter.

Event 5005. Netwtw06

     Intel(R) Wireless-AC 9260: Has encountered an internal error and has failed.

Event 5006, Netwtw06

     Intel(R) Wireless-AC 9260: The version number is incorrect for this driver.

Event 5010, Netwtw06

     Intel(R) Wireless-AC 9260: The network adapter has returned an invalid value to the driver.

Event 5032, Netwtw06

     5032 - Driver Miniport reset watchdog

Event 5055, Netwtw06

     5055 - HW error

Is this an incompatibility with the laptop, a driver issue, or is the hardware actually failed.

~TY

Hello everyone.
My card mounted on a Dell, has a strange problem:
1. If I do a speed test, I surf at 5 megs, despite a 150Mbps connection at least and with the phone surf at 180 Mbps from the same position.

2. While I browse, I lose the connection and to get it back I have to open a tab on the browser and upload the site facebook.com, then load all the tabs otherwise nothing to do.

3. The connection is unstable: if I try to start a teamviewer, this is impossible because of this continuous loss of signal.

The modem is located a few meters from the notebook. I have updated all the drivers and made all the possible solutions around, but nothing. I have a Windows 10 Pro operating system. The modem is a new model so it is compatible with all the parameters a / b / g ac n etc ...
I await your help and any procedure to be performed. Meanwhile, I am attaching reports from the utility tool intel



Thanks so much

Grazie Mille

Alessandro

I have a Intel(R) 82579LM Gigabit Network Connection adapter

I run Windows 10

My network keeps disconnecting while in hibernate mode, and while working as well

I installed PROWinx64.exe

I disabled the function Energy Efficient Ethernet

Both to try to solve the problem.

But it does not work

The strange thing is that there is nog yellow triangle or red cross and it says there is internet access.

Can someone please help me, this is very annoying

Hello everyone.
My card mounted on a Dell, has a strange problem:
1. If I do a speed test, I surf at 5 megs, despite a 150Mbps connection at least and with the phone surf at 180 Mbps from the same position.

2. While I browse, I lose the connection and to get it back I have to open a tab on the browser and upload the site facebook.com, then load all the tabs otherwise nothing to do.

3. The connection is unstable: if I try to start a teamviewer, this is impossible because of this continuous loss of signal.

The modem is located a few meters from the notebook. I have updated all the drivers and made all the possible solutions around, but nothing. I have a Windows 10 Pro operating system. The modem is a new model so it is compatible with all the parameters a / b / g ac n etc ...
I await your help and any procedure to be performed. Meanwhile, I am attaching reports from the utility tool intel



Thanks so much

Grazie Mille

Alessandro

• Intel.txt.zip4.1 K 

Treiber BlueTooth aktuallisiert auf 20.10.0.9 und sofort Probleme mit der BlueTooth-Maus - sporadische Hänger für mehrere Sekunden nach wenigen Sekunden Betrieb oder Inaktivität erneut Hänger. Keine sinnvolle Arbeit mehr möglich. Mit dem bisherigen Treiber der Vorversion lief die Maus absolut problemlos. Wie bekomme ich den alten (funktionierenden) Treiber wieder zurück? Im Gerätemanager konnte ich den vorherigenTreibern nicht wiederherstellen.

Each time I shut down computer connected to WiGig the computer freezes and won't shut down. When I tried to disconnect WiGig in Action center with disabling it in Airplane mode, the computer freezed, too and I lost any control. Only solution is each time hard reset (long press of hardware shut down button). Any help, please? I'm using ThinkPad WiGig with ThinkPad T460.

Я пытаюсь настроить N mode в ноутбуке Sony VAIO SVF 15N190X. В настройках Wireless Mode есть только b, b/g, g. N режим отсутствует.

Драйвер обновлял: 18.33.11.2.

QoS mode: WWM enable.

Метод шифрования роутера WPA 2 - AES.

HT mode - enable.

Что можно сделать? Помогите пожалуйста.

hallo

Ik krijg de volgende fout melding tijdens de update van mijn wifi ac 3165 driver.

Weet iemand een oplossing hiervoor ik gebruik de  intel driver and support assistant hiervoor

mvgr wjke.

I'm  having massiv problems with WIFI. Its impossible to run HD or FullHD streams. In most cases its only SD or it switches for a short time to HD and then back again. On the same place a Lenovo T500 or W520 running without any problem.

Some Data from AVM Fritzbox 7490 - 2.4GHz

the NUC :

-max. mögliche Datenrate 144 / 144 Mbit/s

- aktuelle Datenrate 1 / 29 Mbit/s

the W520 :

- max. mögliche Datenrate 217 / 217 Mbit/s

- aktuelle Datenrate 51 / 29 Mbit/s

Streams interupts and are waiting for internet. Even usual use of internet is nearly impossible or needs too much time.

-Win10 pro

-BIOS 65

-all drivers uptodate

-Samsung M.2/120GB for System

-SSD 480GB Data

-8GB RAM

Hope there is a solution. Thanks in advance

I have an HP laptop with the AC-3165 wireless adapter.  I will do a speed test and it will get about 25-30 mbits, if I turn off the adapter, give it a few seconds and turn it back on it will get my full speed of 100 mbits.  Has anyone else had this issue?  Running Windows 10 64-bit latest drivers installed.

I was currently running the 20.0.2 driver set that worked fine.  I have a Lenovo T440s.  Their system update software, updated the driver to 20.10.2.  It was listed as "critical" and was auto updated. Once the update happened, windows saw the network adapter in Device Manager, but there was a yellow exclamation, and the system did not have any wireless connectivity.  I tried rebooting to see if that had anything to do with it, and it got stuck on the "restarting" screen.  I had to hard power it down after waiting 10 minutes.

I started down the path of uninstalling the Intel PROSet/Wireless Software, then uninstalled the AC 7260 device in device manager, and cleared the temporary files.  I downloaded the latest 20.10.2 version from Intel, and tried installing after a reboot.  Same issue.  I did not know I had the 20.0.2 version prior at this point.  I was extremely lucky and windows had created a restore point earlier that morning.  I reverted to it, and my wireless was back.  I checked the driver and it was the 20.0.2 (Driver version 18.33.9.3). 

I have not attempted to go to 20.10.2 again, and have since disabled lenovo system update from allowing auto installation. 

This post is more of a FYI than anything.  I cannot afford to lose the network in the middle of a work day again so will have limited ability to test anything if that is needed.

I have installed the meltdown/spectre patches from MS, and have updated the BIOS for that too.  I'm not sure if that potentially has any barring on this at all (probably not but figured I would mention it).  Those were the most recent significant changes to the system prior to the wireless driver update/failure.

Request to Send / Clear to Send (RTS / CTS) is an optional 802.11 protocol commonly used to address a condition which occurs in wireless networks called "Hidden Node."  The 802.11 protocol is otherwise vulnerable to the Hidden Node condition because the 802.11 family is based on Carrier Sense Multiple Access.  Generations of chipsets have supported this MAC-layer protocol since before Draft-n.

While characterizing the Intel Joule (AC8260 wireless adapter) as a client of an 802.11n Access Point in the 5GHz band.  802.11n Access Point products from two different vendors were tried; these products use differing generations of Qualcomm Atheros chipsets.  The protocol was enabled in the Access Points and in the Joule.

The result is that the Joule does not "Request to Send."  Additional testing will determine whether the Joule respects "Clear to Send" messages.

Is there a reason that support for RTS was dropped from the AC8260?  Is a firmware update contemplated or available?

Poor SISO RF threshold performance was encountered while characterizing the Intel Joule (AC8260 wireless adapter) as a client of an 802.11n Access Point in the 5GHz band.  802.11n Access Point products from two different vendors were tried; these products use differing generations of Qualcomm Atheros chipsets.  Threshold degradation of 8dB was observed during wired hard-line-connected testing.

Under SISO conditions, for signal levels below an early threshold and above the MIMO threshold, the AC8260 wireless adapter module on the Joule enters a state where it remains connected to the AP, does not search for other AP's, does not disconnect, but also changes to a high MCS level and ceases to transmit.  The situation is exacerbated if the RTS/CTS protocol is enabled.  Then a 20dB early threshold can occur, and in this range of power levels, the Joule will not use the connection but also will not search for a better connection.  Other issues have been observed with RTS/CTS and the Joule.

Is this behavior a known or understood problem?  What are work-arounds?  Is new firmware anticipated?

Sorry, I have reposted the same issue of this thread, since it is closed:

Intel 8265 ac constant high latency jitter

I meet a similar issue of my MSI VR One Backpack PC. And I tried to follow all instructions of the above thread but the problem is still here.

For the MSI VR One, it has been minor updated on last mid yr for upgrade the wireless card from Killer 1535 to Intel 8265.

Does anyone meet the same issue?

Thanks,

Kimkind

I would like to revisit an issue that has been raised a couple of times in the past.  The AC8260 wireless adapter used with the Intel Joule does not support "hotspot" or Access Point or even Ad Hoc configurations in the 5GHz band.  Enable 5G for AC 8260 wireless adapter

The rationale provided for this is generally that there are regulatory issues.  Apparently, the new Intel AC8260 did not inherit the Dynamic Frequency Selection (DFS) radar-detection implementations incorporated into its predecessors over the past decade and more.

Nevertheless, DFS restrictions on 802.11 transmitters only apply to the "US" regulatory domain, not Europe or UK or elsewhere.  And within the US regulatory domain, DFS restrictions do not apply to 5GHz channels 36, 40, 44, 48, 149, 153, 157, 161, and 165.

How can "Hotspot," Access Point, or Ad Hoc configurations be enabled on 5GHz channels 36, 40, 44, 48, 149, 153, 157, 161, or 165?

Hi, I have an 8265 wifi adapter.  I experience BSOD's randomly on system boot up, maybe every 2- 3 or so.   I see this same topic in earlier posts where someone had the same issue then stated it was resolved,

Here is the debug of mini dump file.  It is flagging the Netwtw06.sys file as the probable cause.

Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`d2c9c000 PsLoadedModuleList = 0xfffff801`d3002fd0

Debug session time: Sun Jan  7 16:10:30.213 2018 (UTC + 3:00)

System Uptime: 0 days 4:36:23.158

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..............

Loading User Symbols

Loading unloaded module list

.............

*******************************************************************************

* *

*                        Bugcheck Analysis                                    *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffff960631a00000, 2, fffff801d2e2566f, 2}

*** WARNING: Unable to verify timestamp for Netwtw06.sys

*** ERROR: Module load completed but symbols could not be loaded for Netwtw06.sys

Could not read faulting driver name

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : Netwtw06.sys ( Netwtw06+531eb9 )

Followup:     MachineOwner

---------

4: kd> !analyze -v

*******************************************************************************

* *

*                        Bugcheck Analysis                                    *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced.  This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffff960631a00000, memory referenced.

Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

Arg3: fffff801d2e2566f, If non-zero, the instruction address which referenced the bad memory

               address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Timi

SYSTEM_PRODUCT_NAME:  TM1701

BIOS_VENDOR:  INSYDE Corp.

BIOS_VERSION:  XMAKB5R0P0200

BIOS_DATE:  09/07/2017

BASEBOARD_MANUFACTURER:  Timi

BASEBOARD_PRODUCT:  TM1701

BASEBOARD_VERSION:  MP

DUMP_TYPE:  2

BUGCHECK_P1: ffff960631a00000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff801d2e2566f

BUGCHECK_P4: 2

READ_ADDRESS: fffff801d3098380: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

ffff960631a00000

FAULTING_IP:

nt!memcpy+af

fffff801`d2e2566f 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0

MM_INTERNAL_CODE:  2

CPU_COUNT: 8

CPU_MHZ: 708

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: a

CPU_MICROCODE: 6,8e,a,0 (F,M,S,R)  SIG: 70'00000000 (cache) 70'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-9J1D3C6

ANALYSIS_SESSION_TIME:  01-07-2018 16:36:07.0613

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

TRAP_FRAME:  ffffb008f7dced90 -- (.trap 0xffffb008f7dced90)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000040000 rbx=0000000000000000 rcx=ffff960631a00020

rdx=00001dfb99dc0000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801d2e2566f rsp=ffffb008f7dcef28 rbp=0000000000000000

r8=0000000000000000  r9=0000000000000800 r10=00000000ffffffff

r11=ffff960631a00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na pe nc

nt!memcpy+0xaf:

fffff801`d2e2566f 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0 ds:ffff9606`31a00000=????????????????????????????????

Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801d2e3b71d to fffff801d2e116e0

STACK_TEXT: 

ffffb008`f7dceb18 fffff801`d2e3b71d : 00000000`00000050 ffff9606`31a00000 00000000`00000002 ffffb008`f7dced90 : nt!KeBugCheckEx

ffffb008`f7dceb20 fffff801`d2cebbbd : 00000000`00000002 ffff9606`31a00000 ffffb008`f7dced90 ffffb008`f7dcecc0 : nt!MiSystemFault+0x15151d

ffffb008`f7dcebc0 fffff801`d2e2074e : 00000000`00000000 ffffac80`03f95850 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x23d

ffffb008`f7dced90 fffff801`d2e2566f : fffff801`d313a48a 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 : nt!KiPageFault+0x40e

ffffb008`f7dcef28 fffff801`d313a48a : 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 ffff9606`2c6e34e0 : nt!memcpy+0xaf

ffffb008`f7dcef30 fffff801`d313a214 : 00000000`00040000 00000000`00040000 00000000`00c89848 ffffb008`f7dcf030 : nt!CcCopyBytesToUserBuffer+0x4a

ffffb008`f7dcef80 fffff801`d2cd2cbc : ffff9606`275c8260 00000000`00000000 00000000`00040000 ffff9606`29e58701 : nt!CcMapAndCopyFromCache+0x114

ffffb008`f7dcf020 fffff80c`3ceb25ee : ffff8502`00000000 ffff8502`00000000 ffff9606`00c89848 ffff8502`00000000 : nt!CcCopyReadEx+0x12c

ffffb008`f7dcf0b0 fffff80c`3ceb4dff : 00000000`00c89848 ffffb008`f7dcf350 ffff8502`d4653bf0 ffff8502`d4653c48 : NTFS!NtfsCachedRead+0x182

ffffb008`f7dcf120 fffff80c`3ceb29b8 : ffff9606`303f0558 ffff9606`2b6a3010 00000000`00000064 ffff8502`d4653bf0 : NTFS!NtfsCommonRead+0x224f

ffffb008`f7dcf320 fffff801`d2cb62d9 : ffff9606`304b4c00 ffff9606`2b6a3010 00000000`00000000 ffff9606`2b6a3440 : NTFS!NtfsFsdRead+0x1d8

ffffb008`f7dcf3e0 fffff80c`3ba08773 : ffff9606`2b6a3010 ffffb008`f7dcf4c0 ffffb008`f7dcf4d9 00000000`00000000 : nt!IofCallDriver+0x59

ffffb008`f7dcf420 fffff80c`3ba06db6 : ffffb008`f7dcf4b0 ffffc562`b15b5f10 ffff9606`28349b01 fffff801`d2d5c0c5 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a3

ffffb008`f7dcf490 fffff801`d2cb62d9 : ffff9606`2b6a3010 fffff801`d3136440 ffffaf80`00009040 00000000`00103100 : FLTMGR!FltpDispatch+0xb6

ffffb008`f7dcf4f0 fffff801`d3115efe : 00000000`00000000 ffff9606`2c6e34e0 ffff9606`2b6a3488 fffff801`d30b3200 : nt!IofCallDriver+0x59

ffffb008`f7dcf530 fffff801`d31168fa : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb008`f7dcf7c0 : nt!IopSynchronousServiceTail+0x19e

ffffb008`f7dcf5e0 fffff801`d2e24203 : 00000000`00000300 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x68a

ffffb008`f7dcf6d0 fffff801`d2e15100 : fffff80c`3ef71eb9 fffff80c`3ee242c8 fffff80c`3ee24270 fffff80c`3ee24330 : nt!KiSystemServiceCopyEnd+0x13

ffffb008`f7dcf8d8 fffff80c`3ef71eb9 : fffff80c`3ee242c8 fffff80c`3ee24270 fffff80c`3ee24330 fffff80c`3ee24300 : nt!KiServiceLinkage

ffffb008`f7dcf8e0 fffff80c`3ee242c8 : fffff80c`3ee24270 fffff80c`3ee24330 fffff80c`3ee24300 ffffb008`f7dcf930 : Netwtw06+0x531eb9

ffffb008`f7dcf8e8 fffff80c`3ee24270 : fffff80c`3ee24330 fffff80c`3ee24300 ffffb008`f7dcf930 ffff9606`31a00000 : Netwtw06+0x3e42c8

ffffb008`f7dcf8f0 fffff80c`3ee24330 : fffff80c`3ee24300 ffffb008`f7dcf930 ffff9606`31a00000 fffff801`00c89848 : Netwtw06+0x3e4270

ffffb008`f7dcf8f8 fffff80c`3ee24300 : ffffb008`f7dcf930 ffff9606`31a00000 fffff801`00c89848 00000000`00000000 : Netwtw06+0x3e4330

ffffb008`f7dcf900 ffffb008`f7dcf930 : ffff9606`31a00000 fffff801`00c89848 00000000`00000000 00000000`00000000 : Netwtw06+0x3e4300

ffffb008`f7dcf908 ffff9606`31a00000 : fffff801`00c89848 00000000`00000000 00000000`00000000 00000000`00000240 : 0xffffb008`f7dcf930

ffffb008`f7dcf910 fffff801`00c89848 : 00000000`00000000 00000000`00000000 00000000`00000240 00000000`00000000 : 0xffff9606`31a00000

ffffb008`f7dcf918 00000000`00000000 : 00000000`00000000 00000000`00000240 00000000`00000000 00000000`00000018 : 0xfffff801`00c89848

THREAD_SHA1_HASH_MOD_FUNC:  3d6cde47e773f16403bbc07451cb0ace9284a31c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ed0efe6e78434f104d261aa9ca0339c46a8eb59f

THREAD_SHA1_HASH_MOD:  a748b77ec3bc3a3a63336300a46c45387f2d3225

FOLLOWUP_IP:

Netwtw06+531eb9

fffff80c`3ef71eb9 33d2            xor     edx,edx

FAULT_INSTR_CODE:  4489d233

SYMBOL_STACK_INDEX:  13

SYMBOL_NAME:  Netwtw06+531eb9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Netwtw06

IMAGE_NAME:  Netwtw06.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  59fb46b2

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  531eb9

FAILURE_BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_INVALID_Netwtw06!unknown_function

TARGET_TIME:  2018-01-07T13:10:30.000Z

OSBUILD:  16299

OSSERVICEPACK:  192

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-01-01 14:07:05

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.192

ANALYSIS_SESSION_ELAPSED_TIME:  2037

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_invalid_netwtw06!unknown_function

FAILURE_ID_HASH:  {2101a6f1-56d4-96a1-954f-0b4ab4996965}

Followup: MachineOwner

---------

I have an HP Pavilion 15-au123cl notebook with an Intel(R) Dual Band Wireless-AC 3168 adapter. My internet  is Google Fiber full Gigabit (1000 mbps) service. I am only getting about 65mbps download and 165mbps upload with this setup. The router is the newer Google Fiber Network Box that supports 802.11ac and I am using the 5Ghz band exclusively with the notebook.

I was expecting much better performance from the 802.11ac setup and believe there must be a problem with my adapter settings. I am not highly technical, and am looking for information on how to configure my adapter, etc. to achieve higher wireless connection speeds (and hopefully not half the speed for uploading as downloading).

BTW: I have confirmed that the Google Fiber runs around 950mbps upload and download when I connect with a ethernet cable directly to the Google Fiber Network Box (although not using the Pavilion which only supports 10/100 ethernet) so I know the internet connection is not a barrier.

Pavilion 15-au123cl