I was previously running Windows 10 64-bit Anniversary edition 1607 without any problems.
I have an Intel dual band 7260AC for desktop installed with IPv4 and IPv6 enabled, driver version 188.8.131.52 from the wireless proset version 19.50.1
A few days ago, I installed the update to the new Windows 10 Creator edition 1703 and ALL applications, including console programs like 'nslookup' and 'ping', using the wirless network started to become 'not responding' after a few minutes or less.
Once an application 'hung', it could not be terminated from task manager, giving an 'access denied' error when attempting and 'end task'.
If I disabled the Intel 7260AC adapter and using a wired Broadcom ethernet connection, everything worked normally again.
After disabling IPv6 on the Intel 7260AC, the wireless network ALSO worked again without hanging.
Looking at the symptoms, it seems there is a problem with the 184.108.40.206 driver on Windows 10 Creator edition, where an application gets 'hung' inside the system call to the driver, because they can't be terminated anymore.
I didn't see any newer drivers available and was wondering if other people have encountered similar problems or are using a 7260AC adapter with IPv6 enabled normally?
This is strange, it actually worked. I already faced this problem 2 months ago, fixed by rollbacking drivers. But after the Fall Creators Update, there was no rollback option. I even tried to reinstall OS and it didn't work.
The workaround from sutto actually works, been stable for few hours without a problem, normally the driver would cause freezes and would have a yellow exclamation mark in the taskbar after 15 minutes.
Tried this and since have been unable to connect to my wireless AP at all anymore. System just says it's trying to connect indefinitely. Tried the network reset solution prior to the Fall Creator's update and sadly even after it, and reboots, and removal of the device, with uninstallation of the driver back to the oldest one, and re-installation of the latest, I continue not to be able to connect at all now.
I haven't spent any more time on it since I attempted it. Will try more this weekend. Curious if anyone else had a problem with this potential solution or if I'm the only one.
So I just tried to connect to my AP again and it worked. Rebooted, still connected. Will see what happens.
Prior to trying sutto's solution I had installed the Release version of the latest drive and was still losing connection but only for a few seconds. Still, it was enough to break the Plex streaming I am running off this machine.
Will report back if the connection is now solid.
*edit* in the time I wrote the message above and clicked Add Reply on this forum the connection died. It did not reconnect itself after a few seconds. So I guess I am not ok.
Sounds like you are having a different issue... I would think that your issue is with your router.... would suggest firmware update on router, maybe replacement depending on age.... if ISP supplied would recommend getting a separate router... if you have already replaced then change channels on router to determine if interference issue. I did not have an issue connecting to the router, so my fix may not work for that. But check for Firmware updates, interference, maybe you need a booster?.... I have a Netgear Nighthawk at home, and Netgear R8000 at my office... both have been stable since the fix, but again my fix was for a different issue.
Don't think I'm having a different issue. You can see my troubleshooting with Carlos /thread/115863 here. Basics are that this machine and the router worked fine for over a year and broke after an update to Win 10. What were you experiencing, sutto?
Before Win 10 Anniversary update
After Win 10 Anniversary update
When the crash happens I lose wireless network connectivity. I am unable to disable/re-enable via Device Manager because it hangs. Sometimes I am unable to Restart or Shutdown Windows. When this happens either option displays the 'working' circle showing Restarting or Shutting Down indefinitely. In all cases to restore connectivity I must hard shutdown the machine using the power button.
If the crash happens and I leave the machine long enough, Bluetooth served by the AC7260 is also taken down rendering my bluetooth mouse and keyboard unresponsive.
I am able to see indicative events in the Event Viewer that state the AC7260 adapter is beginning to restart itself. These events are always logged upon failure event.
1- Rolling back drivers one version at a time, opting to remove the device driver from the system upon rollback. Leaving the system on each driver version for a few days to observe. In all cases the crash reproduces itself excep..
2- ... when rolling back all the way to 22-Feb-2015 (220.127.116.11) which worked for a few months but recently the issue reoccured.
3- I tried installing the latest 5-Apr-2017 (18.104.22.168) and experienced the same issue.
4- Checked the recommended settings for 802.11n connectivity.
After KB4022716 and 19.60.0
Same result of sporadic disconnection, even if rolling back to 22.214.171.124
After Creator's update and 19.70.0
Same result of sporadic disconnection
After 19.71 test driver
Same result of sporadic disconnection
After 19.71 production driver
Connection crashes every 30 mins or so but reconnects almost immediately
After network reset
At cannot connect to AP.
After Creator's Fall update
Able to connect, connection crashes after a few minutes.
@ Carlos, what's the latest on your end? News from Intel has been really quiet. Are you seeing more or less cases? What are the latest discussions between Intel and MS currently?
yeah that sounds the same, Sorry I did not read your past troubleshooting, I just saw that you where unable to connect.
I struggled with the same issue as you, and nothing worked until network reset.
I did not try the registry suggested changes - if you did undo it.
I installed creators update, reinstalled/updated network drivers, and Bluetooth drivers VIA intel driver update utility. Left all settings Default, noticed missing wan drivers in device manager and was unable to see network computers... wifi card was dropping connection, and then becoming disabled and had to hard reboot..... so I completed network reset and missing drivers returned and all computers showed on network... left all settings default after network reset. I was able to connect right away... when I lost connection 1 time, it reconnected instantly (like a normal computer finally)... which it had never done before, normally it would just crash and I would have to hard reboot....
Would recommend you update firmware in your router as well, and confirm with another device that it is working properly. I only suggest that as routers can have issues randomly as well too. I just had to replace one in my office for random connectivity issues.... Well good luck, I just wanted to clarify what I had done to make it work, as I was running a cable for 1year and just about to purchase a USB wifi card.
Intel Corporation wrote:
1. Download and save our latest Intel® PROSet/Wireless Software for Windows® 10:https://downloadcenter.intel.com/download/26653/Intel-PROSet-Wireless-Software-and-Drivers-for-Windo... Wireless_19.50.1_PROSet64_Win10.exe
intel_corp Hi @Carlos
I have something to add to this very discussion, and am making my own thread for it.
I'll link it in a sec ....
here it is:
For the Wireless Dual Band 7260 use driver only 18.33
The Bluetooth USB driver can use 19.60 from memory.
Ensure that the ProSet software isn't installed - Windows is having issues with one of the interface pages. haven't had the chance to go full blown debugging yet.
I'm almost certain that something funky happens in the Windows Update Catalog Database when there is a mix of compatible hardware and software for multiple devices but specific devices aren't included for software installations in certain conditions.
It's like the chipset scenario.
ps. one of the major issues is the Bluetooth or the Wireless going to either a low power mode.
The logs will get filled with the firmware or drivers are limiting the device entering low power ...
that's when windows may try cycling through the different drivers installed on the system
Has any progress been made on this issue? I am having the same problem with my Intel Dual Band Wireless-AC 3160. My symptoms seem to match those outlined by jcray in his recent post.
In /thread/115863?start=15&tstart=0 this thread Carlos A posting on behalf of intel_corp said that a solution would be posted here when Intel found one.
This was an OS sided issue affecting some but not all systems with our wireless adapters and as well as several adapters from other brands. This was eventually resolved through Windows Updates*.
For most users performing a Network Reset resolved the problem:
1. Select the Start button, then select Settings > Network & Internet > Status > Network reset.
2. On the Network reset screen, select Reset Now > Yes to confirm.
3. Wait for your PC to restart.
Are you using the https://downloadcenter.intel.com/download/27309 latest drivers for your adapter?
Thanks for your reply. I've got the latest driver (126.96.36.199) and my Windows 10 is fully updated.
I just tried performing a Network Reset and restarting my PC. I'll post back in here if the problem persists, but if you don't hear from me you can assume it worked.
We hope this resolves your issue. If it doesn't, let us know and attach a complete SSU report so that we may provide some more specific troubleshooting for you.
1. Download and run the http://downloadcenter.intel.com/download/25293 Intel® System Support Utility.
2. Select to scan "everything," and run the scan while connected to your wireless network (if possible).
3. Save the report and attach it to your reply.
Note: To enable attachments, make sure to switch to the advanced editor while replying.
I want to confirm having similar issue on my Lenovo Yoga Pro 2 laptop and AC 7260 network card.
By similar I mean the card dropping the connection, having yellow exclamation mark on the WiFi icon in the task bar, if I try to troubleshoot with windows tool or switch off/switch on the card it gets worse. I found after those actions I can't perform chekdisk (it freezes after displaying "The type of the file system is NTFS". After that only reboot helps.
I tried the network reset but I lost the connection after 2hrs.
But... as someone mentioned in another thread here this time I used workaround - put the laptop in the sleep mode for ~15 seconds, after that everyting becomes normal, no need to reboot that after the described state above lasts for minutes ending with a BSOD (mostly Driver Power Failure State).
I use up to date Windows 10 Pro and the latest Intel drivers from the ProSet package 20.40.0.
Why the sleep mode can fix the WiFi while Windows itself make it even worse?
Thanks for posting. In this case, the issue description seems somewhat different.
The sleep mode behavior and the chkdsk results suggest a hardware problem. We recommend to backup your data and reinstall the operating system.
If the issue persists, please https://www.intel.com/content/www/us/en/support/topics/oems.html contact your system OEM for further assistance.
thanks for your reply,
I would like to mention that same time I have following symptoms in Windows System Log as described here:
I freshly installed Win10 (again) last week.
Do you think it's the hardware not the driver issue?
Seb aka eSbek
Many customers have reported that similar issues were fixed after a hardware replacement with the assistance of their computer Original System Manufacturer, even when replaced with another Intel® Dual Band Wireless-AC 7260.
Hello Carlos !
Working solution with my situation.
Got update - Windows 10 Pro 1803 and after installation, reboot my wireless connection cannot receive ipv6 settings from router Zyxel Keenetic Ultra II
uninstalling default windows driver ind installing WiFi_20.50.0_PROSet64_Win10.exe recovered situation !
Thank you !
Years later, issue still exists on Windows 10 1903, whatever driver version being installed. Forcing 802.11n on 2.4Ghz actually does the trick, except that it's no longer an AC card in this mode.
And there's clearly something to do with hardware because I have another one in another computer that works flawlessly and swapping them also swaps the issue. Both are revision BB.
OK: 48-51-B7-15-86-EB KO: AC-FD-CE-E5-9F-7A