I have Intel(R) Dual Band Wireless-AC 3165. Windows 10 pro. I've tried every solution so far; resetting, updating, downgrading driver, delete, changing parameters etc. but nothing helps. The thing is when my HP notebook wakes after sleep it takes time to find my wireless network. It takes everything from 10 seconds to a couple of minutes and sometimes not at all. Or it finds it but stays in connection mode. The problem comes and goes and has been a problem for the last 6-8 months. I can reset the network and I got no problem for 2-10 days and then it starts over again with not connecting with no reason so far I can see. I get the warning: 6105 - deauth after EAPOL key exchange sequence.

My personal toshiba laptop (Windows 10 pro) is running out of disk space and there is the above application that is listed as 12.6GB. I read that I could uninstall this program but when I try to do that, it asks me to confirm the uninstall and then comes back with the following question:

Do you want to remove drivers for all wired Intel Network Connections? When I enter Yes, nothing happens and the software is not removed.

So, my question is, do I need this software and if not, why can't I uninstall it. And how do I overcome this problem?

Bonsoir, je cherche à faire fonctionné un dongle Miracast branché sur ma télé LG.

Je suis donc passé à Windows 10 à reculons afin de bénéficier du support natif de Miracast. Problème, je ne dispose pas de l'option " Ajoutez un affichage sans fils ". Après quelques recherches sur Internet, je finis par mettre mes pilotes à jour, notamment la carte Wifi ainsi que la carte graphique intégré au CPU.

Et voici le résultat en image.

Le gestionnaires de périphérique m'indique la version 15.18.0.1 qui est censément la dernière version pour se matériel mais l'utilitaire d'intel pour la mise à jour s'obstine à me demandé d'effectuer une mise à jour. Dans le même temps, la commande " netsh wlan show drivers m'indique que mon pilotes wifi ne prend pas en charge l'affichage sans fils.

Je joint également un DxDiag

Cordialement

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

Our Dell E5580 Latitudes aren't switching from a "wired" connection to a "wireless" connection.  So, I installed the Intel ProSet wireless wifi connection utility version 19.10 to match our wireless driver on one of the laptops.  I created a new package that Enabled Adapter Switching under the Application Settings tab.  I then save the package as the .exe. and apply the package to the current machine.  The current machine works fine.  However, I am unable to use the .exe package that I created and saved for the remainder of my machines.  Am I making the wrong assumption that the .exe package that I've created should work on the remainder of my E5580 Latitudes with that driver version?  When I go to another machine and click on the .exe package that I have saved on our shared network drive, it thinks for a while and acts like its making a configuration change but it doesn't work.

I have 9260ngw for upgrade my asus n752vx notebook. My router is Netgear 7800.

Drivers:  BT_20.10.0_64_Win10.exe and WiFi_20.10.2_PROSet64_Win10.exe.

Work fine at 5ghz, connection speed 1.7Gbps is real.

But after system susped at resume new conection speed degrade to 173Mbps.

Only disable/enable 9260ngw  in device manager can help to return to 1.7Gbps.

I have a dell 9020 aio optiflex with intel 7265n wireless card and after pc wake from a sleep the pc doesn't reconnect to the internet

my driver is up to date 18.33.11.2

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.

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?

Hi. Am using HP notebook 15-ay190nia and I need to install Intel(R)l dual band wireless -ac 3165. Where can I download and install them? Currently Iam using Realtek adapter

i've been using a 8265 PCIe add in card from Gigabyte to share my computer's LAN connection for my phone. and there're issues:

1) every 15-30 minutes, the wi-fi connection is lost due to 8265 resetting. it will be back to work after a while, but it's very annoying.

2) several minutes after my phone disconnected from wi-fi, the hotspot will be automatically turned off.

i've tried following and the issues persist:

1. unchecked "allow the computer to turn off this device to save power." for 8265 and its virtual adapters.

2. in advanced power plan, set wireless adapter settings to "Maximum Performance".

3. updated the driver to most recent 20.10.2.2.

to be specific, before i updated the driver to 20.10.2.2 (i don't know which version the previous driver is), the adapter didn't reset itself. i had to disable and enable it to make it work. Windows Event Viewer was spammed by "Intel(R) Dual Band Wireless-AC 8265 : Has determined that the network adapter is not functioning properly." error (dozens of entries every second).

with the 20.10.2.2 driver, in Event View i get following errors every 15-30 minutes:

5007 - TX/CMD timeout (TfdQueue hanged)

<EventData>

The network interface "Intel(R) Dual Band Wireless-AC 8265" has begun resetting.  There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. This network interface has reset 10 time(s) since it was last initialized.

<EventData>

information about my system:

Add-in Card Model: Gigabyte GC-WB867D-I rev4.3

OS: Windows 10 version 1709 (64bit, updated to most recent patch)

CPU & Motherboard: Intel Xeon E3-1245 v6 on Gigabyte GA-X170-EXTREME ECC (Intel C236 Chipset, BIOS and driver updated to most recent version)

I upgraded the WiFi card in my Lenovo Yoga 2 Pro almost a year ago to an Intel Wireless-AC 7260 7260NGW 802.11ac Dual Band NGFF Wifi Card, and it's been performing flawlessly until the last week or so.

I'm now experiencing drop-outs in wi-fi every few minutes / hours. The severity is strangely erratic: sometimes these can be be resolved by right-clicking the system tray icon and letting the troubleshooter restart the adapter, but occasionally it's as if the card's not there at all, it's not even listed in the device manager, defying refreshes and sometimes even restarts.  Eventually it will come back, only to be as unstable as before.

I have physically removed the card, cleaned the contacts and checked that it's seated correctly and removed and re-installed the drivers with no success

After searching online I found reports on this forum of other issues associated with 7260 cards and Windows 10 updates and wondered if my experiences could be linked, there have certainly been a lot of Windows updates recently.

I'll be very grateful for any suggestions / advice.

Is the Intel Advanced N 6230 comparable with 802.11 ac/ad

Dear Team,

I have an  ASUS ZenBook UX430UA with a Dual Band Wireless AC 8265 (

I believe I have the latest driver 20.10.2.2 ) running Windows 10 home.

I have performance issues.

If I force the network to be 802.11b   ( by going to Properties -> Advanced -> Wireless Mode: 2. 802.11b  )

I am getting ALMOST  ( see last paragraph ) acceptable pings Max and Average

(but of course the performance of 802.11b is not  ( 11Mbps)  )

    Minimum = 1ms, Maximum = 55ms, Average = 3ms

    Minimum = 2ms, Maximum = 404ms, Average = 13ms

    Minimum = 2ms, Maximum = 47ms, Average = 5ms

    Minimum = 2ms, Maximum = 198ms, Average = 6ms

When I switch back to the default 802.11n: ( by going to Properties -> Advanced -> Wireless Mode: 6. 802.11/a/b/g )

The Average goes back  up significantly:

    Minimum = 1ms, Maximum = 119ms, Average = 21ms

    Minimum = 1ms, Maximum = 393ms, Average = 22ms

    Minimum = 2ms, Maximum = 149ms, Average = 21ms

    Minimum = 1ms, Maximum = 280ms, Average = 36ms

I don't understand why this network card is not happy to work in 802.11n mode...

Note: doing the same (802.11n) test with an old laptop also 10m away from the router

with a Qualcomm atheros AR956x card  gives me

Maximum 74ms Average: 4ms

Maximum 48ms Average: 3ms

Maximum 47ms Average: 2ms

Maximum 56ms Average: 3ms

Which is much better than the 2 previous sets of test with the Dual Band Wireless AC 8265

Please note that this is a hom.network .

No downloads taking place during the test. 7 idle devices altogether.

I am ALSO getting bad ping responses if i connect to a standalone (no internet / no other devices ) old WRT300N ...

any suggestion?

Bonsoir, je cherche à faire fonctionné un dongle Miracast branché sur ma télé LG.

Je suis donc passé à Windows 10 à reculons afin de bénéficier du support natif de Miracast. Problème, je ne dispose pas de l'option " Ajoutez un affichage sans fils ". Après quelques recherches sur Internet, je finis par mettre mes pilotes à jour, notamment la carte Wifi ainsi que la carte graphique intégré au CPU.

Et voici le résultat en image.

Le gestionnaires de périphérique m'indique la version 15.18.0.1 qui est censément la dernière version pour se matériel mais l'utilitaire d'intel pour la mise à jour s'obstine à me demandé d'effectuer une mise à jour. Dans le même temps, la commande " netsh wlan show drivers m'indique que mon pilotes wifi ne prend pas en charge l'affichage sans fils.

Je joint également un DxDiag

Cordialement

This is on a Lenovo Thinkpad P70 with Windows 10 64-bit.  It is just over a year old and just out of warranty.  I have not previously used Bluetooth on this device, and would now like to attach a Bluetooth 3.0 keyboard.

In the Device Manager Bluetooth was originally hidden and the drivers said "Currently this device is not connected".  I uninstalled these, deleting the software, and installed BT_20.10.0_64_Win10.exe (Verion 20.10.0.9).  The drivers then said "This device is working properly".

It appears to work, but fails to connect to any Bluetooth devices I have tried.  It does discover the devices and show them as available.  (See the image).  They just don't pair.  The same devices pair and work fine with my Galaxy S7 phone and Microsoft Surface Book.

I also tried BT_19.71.0_64_Win10.exe (Version 19.71.0.2) with the same results.  I tried the download from the Lenovo site, which is for 19.71.0.2).  It appears to run successfully, but the drivers have light blue icons, say "Currently this device is not connected", and you have to select Show hidden to see them.  (This was how the Device Manager looked when I started.)  Thus, this Lenovo driver update doesn't seem to work.

The BIOS is the latest and Windows is up to date with Creator's Fall Edition.

The Intel drivers both appear to work, but don't pair.  I'm not sure what to do next.

I am having connectivity issues on TWO laptops (different brands HP and Lenovo) using the same adapter with Windows 10 Home 64 bit as the OS.  I have a p50 laptop with Win7 that works FINE.  The HP used to work well until a windows update seemingly caused issues.  I can get a few really good speed tests at speedtest.net and then I'll either get a latency error or a very slow (0.84Mb/s) download speed.  Most of my download speed on the test were between 24.0 and 29.0 Mb/s.  I have tried many different things including updating wireless driver, rolling back the driver, etc.  to no avail.  Please advise.  Just an FYI - the HP is a year old and the Lenovo is two weeks old.  Thanks.

My laptop can not detect Wigig Dock(HP)

My laptop is HP Elite X2 1012 G1

and Related Drivers is below image.

but Bios Version was upgraed 01.22 to 01.24

Here is the thing.

Wiress Dock Manager's Version(2.6.1.102...it's the latest version in HP Support page)

is not match with Wireless Gigabit 18260(3.0.50134.10)

WiDock's version is should be 3.0.50135(Intel's latest version)

So I downloaded it from Intel suport site(file name : WiDock_3.0.50135)

And trying to install it.

But unfortunately it was interrupted with showing this image.

How can I install Rigth version?

And how can I detect the Wigig Dock?

After updating my Wifi driver to 20.0.2.3 (2-3 weeks ago), I've twice gotten a blue screen crash on resume from sleep. As this driver version is the first to include the KRACK vulnerability fix, it is not reasonable to roll back to an older version. An inspection of the last memory dump reveals the following:

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: ffff8009f4c00000, memory referenced.

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

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

    address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  20FQS04X00

SYSTEM_SKU:  LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Carbon 4th

SYSTEM_VERSION:  ThinkPad X1 Carbon 4th

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  N1FET55W (1.29 )

BIOS_DATE:  09/08/2017

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  20FQS04X00

BASEBOARD_VERSION:  SDK0J40697 WIN

DUMP_TYPE:  1

BUGCHECK_P1: ffff8009f4c00000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80032d896af

BUGCHECK_P4: 2

READ_ADDRESS:  ffff8009f4c00000 Nonpaged pool

FAULTING_IP:

nt!memcpy+af

fffff800`32d896af 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0

MM_INTERNAL_CODE:  2

CPU_COUNT: 4

CPU_MHZ: af8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: BA'00000000 (cache) BA'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

TRAP_FRAME:  ffffcb80e41c3ec0 -- (.trap 0xffffcb80e41c3ec0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000040000 rbx=0000000000000000 rcx=ffff8009f4c00020

rdx=0000377d57080000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80032d896af rsp=ffffcb80e41c4058 rbp=0000000000000000

r8=0000000000000000  r9=0000000000000800 r10=00000000ffffffff

r11=ffff8009f4c00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na pe nc

nt!memcpy+0xaf:

fffff800`32d896af 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0 ds:ffff8009`f4c00000=????????????????????????????????

Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80032db3156 to fffff80032d7d580

STACK_TEXT: 

ffffcb80`e41c3c28 fffff800`32db3156 : 00000000`00000050 ffff8009`f4c00000 00000000`00000002 ffffcb80`e41c3ec0 : nt!KeBugCheckEx

ffffcb80`e41c3c30 fffff800`32c9e6c6 : 00000000`00000002 ffff8009`f4c00000 ffffcb80`e41c3ec0 ffff8009`d7e8d500 : nt!MiSystemFault+0x116c36

ffffcb80`e41c3cd0 fffff800`32d86d72 : ffff8009`00000005 ffff8009`00000001 00000000`00000000 ffffcb80`e41c3f30 : nt!MmAccessFault+0xae6

ffffcb80`e41c3ec0 fffff800`32d896af : fffff800`3309960a 00000000`00040000 00000000`00000000 ffff8009`00000005 : nt!KiPageFault+0x132

ffffcb80`e41c4058 fffff800`3309960a : 00000000`00040000 00000000`00000000 ffff8009`00000005 ffff8009`eb7c7190 : nt!memcpy+0xaf

ffffcb80`e41c4060 fffff800`330993a4 : 00000000`00040000 00000000`00040000 00000000`00f3ef48 ffffcb80`e41c4160 : nt!CcCopyBytesToUserBuffer+0x4a

ffffcb80`e41c40b0 fffff800`32c5588b : ffff8009`f11081f0 00000000`00000000 ffff8009`00040000 00000000`00000001 : nt!CcMapAndCopyFromCache+0x114

ffffcb80`e41c4150 fffff802`b07d4032 : ffffa08d`00000002 00000000`00000001 ffffa08d`00f3ef48 ffffa08d`00000000 : nt!CcCopyReadEx+0x12b

ffffcb80`e41c41e0 fffff802`b07cc5e3 : ffff8009`d7e50180 ffffcb80`e41c4470 ffffa08d`fa82fc00 00000000`000000ff : NTFS!NtfsCachedRead+0x1a6

ffffcb80`e41c4250 fffff802`b07cb93e : ffff8009`ea73bad8 ffff8009`e4b70880 ffffa08d`fa82fc90 00000000`00000001 : NTFS!NtfsCommonRead+0xad3

ffffcb80`e41c4440 fffff802`ae60563d : ffff8009`eb629b00 ffff8009`e4b70880 ffff8009`dc0c3df0 ffff8009`e4b70c68 : NTFS!NtfsFsdRead+0x1ee

ffffcb80`e41c44f0 fffff802`ae6034d6 : ffffcb80`e41c4580 00000000`00000001 00000000`00000000 ffffcb80`e1cc0180 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x18d

ffffcb80`e41c4560 fffff800`330a672f : ffff8009`eb7c7190 ffff8009`e4b70880 ffff8009`e4b70cb0 00000000`00000001 : FLTMGR!FltpDispatch+0xb6

ffffcb80`e41c45c0 fffff800`330a5499 : ffff8009`00000001 ffff8009`eb7c7104 ffff8009`eb7c71e0 ffffcb80`e41c4870 : nt!IopSynchronousServiceTail+0x1af

ffffcb80`e41c4680 fffff800`32d88413 : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x6a9

ffffcb80`e41c4780 fffff800`32d80760 : fffff802`b5f73ea9 fffff802`b5e27a60 00000000`00000100 fffff802`b5e27ac8 : nt!KiSystemServiceCopyEnd+0x13

ffffcb80`e41c4988 fffff802`b5f73ea9 : fffff802`b5e27a60 00000000`00000100 fffff802`b5e27ac8 fffff802`b5e27a98 : nt!KiServiceLinkage

ffffcb80`e41c4990 fffff802`b5f74188 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00f3ef48 : Netwtw06+0x533ea9

ffffcb80`e41c4a30 fffff800`32c2fe9b : ffff8009`00f3ef48 ffff8009`dcbc12f0 ffff8009`dcbcd060 ffff8009`e2333040 : Netwtw06+0x534188

ffffcb80`e41c4a90 fffff800`32c4f168 : 00000000`00000100 ffff8009`ed89d640 fffff800`32c2fda0 00000000`00000000 : nt!IopProcessWorkItem+0xfb

ffffcb80`e41c4b00 fffff800`32cedeb7 : 00000000`00000001 00000000`00000080 ffff8009`d7e8d500 ffff8009`ed89d640 : nt!ExpWorkerThread+0xd8

ffffcb80`e41c4b90 fffff800`32d82a06 : fffff800`311fa180 ffff8009`ed89d640 fffff800`32cede70 ffffcb80`e41c4d29 : nt!PspSystemThreadStartup+0x47

ffffcb80`e41c4be0 00000000`00000000 : ffffcb80`e41c5000 ffffcb80`e41be000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC:  e8a4222b200fd5e09a45e55f7343347a90e99999

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3008069a119e51096ddb4b95f9511eca7af74429

THREAD_SHA1_HASH_MOD:  acd05c535281c782b7d45b17bb5c152018f5e1ee

FOLLOWUP_IP:

Netwtw06+533ea9

fffff802`b5f73ea9 33d2            xor     edx,edx

FAULT_INSTR_CODE:  4489d233

SYMBOL_STACK_INDEX:  11

SYMBOL_NAME:  Netwtw06+533ea9

MODULE_NAME: Netwtw06

IMAGE_NAME:  Netwtw06.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  59d213eb

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  533ea9

FAILURE_BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_INVALID_Netwtw06!unknown_function

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-09-29 09:20:26

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  c5e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_invalid_netwtw06!unknown_function

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

Our Dell E5580 Latitudes aren't switching from a "wired" connection to a "wireless" connection.  So, I installed the Intel ProSet wireless wifi connection utility version 19.10 to match our wireless driver on one of the laptops.  I created a new package that Enabled Adapter Switching under the Application Settings tab.  I then save the package as the .exe. and apply the package to the current machine.  The current machine works fine.  However, I am unable to use the .exe package that I created and saved for the remainder of my machines.  Am I making the wrong assumption that the .exe package that I've created should work on the remainder of my E5580 Latitudes with that driver version?  When I go to another machine and click on the .exe package that I have saved on our shared network drive, it thinks for a while and acts like its making a configuration change but it doesn't work.