Quantcast
Channel: Intel Communities: Message List - Wireless Networking
Viewing all articles
Browse latest Browse all 15514

Re: 17.1.0 wifi adapter disabled after sleep

$
0
0

Here are my findings:

 

I have been having similar problems with the AC7260 as everyone else when waking from sleep and powering on.  The only way I could get wireless to work after a boot or after waking from sleep was to right click on the wireless icon in the systray>Open Network and Sharing Center>Change Adapter Settings: then right click on the AC7260 adapter and Disable/Enable.  Once I did that it all seemed to work fine.  I had to do this every time I booted or waking my laptop from sleet.

 

In an attempt to fix this I installed the latest drivers from the site v.17.1.0.  This only made the situation worse.  Now on boot the adapter was completely missing when I went to change adapter settings.  I had to go into the device manager to find it and it had errors.  I could then enable from here and it seemed to work.  On boot I pulled these errors from the event log and thought it may help shed some light on what is going on:

NETwNb64: Intel(R) Dual Band Wireless-AC 7260 : Could not allocate the resources necessary for operation.

NETwNb64: Intel(R) Dual Band Wireless-AC 7260 : The version number is incorrect for this driver.

NDIS: Miniport Intel(R) Dual Band Wireless-AC 7260, {83079d22-ae82-4800-9a93-27739f60a4a4}, had event Fatal error: The miniport has failed a power transition to operational power

 

I travel all over the place with my laptop and routinely connect to about 3 or 4 different access points every week.  The behavior is the same no matter where I connect.  I tried reverting to 17.0.6 which one user said works.  So far I am able to reconnect when I wake from sleep.  Granted, I just installed this older driver so I will keep an eye on it and report back here.

 

Update 9/11/2014

I have successfully been connected after sleep a number of times with the 17.0.6 drivers but I still need to disable/enable the adapter on boot.  It is in a perpetual state of "identifying the network".  The second I disable and enable it connects just fine.


Viewing all articles
Browse latest Browse all 15514

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>