And another strange thing i discovered is that this problem only happend when i trying to connect to my TP-Link routers, if i connect to my iphone personal hotspot, the wifi works very good, no lags and disconnects at all, it seems that the 8260AC is not capable with my TP-Link router? Now i have to use a network bridge to re-broadcast the TP-Link wifi, this solution is really stupid.Īnd i have another problem is that i discovered i can't use my wifi and my bluetooth at the same time 5G wifi is also disconnect, if i connect bluetooth and wifi at the same time, the wifi will be disconnected immediately, and can't be reconnect anymore, even can't search any hot points. I have the same question, my desktop pc is using 8260AC adapter and when i'm trying to connect to my home wifi, it will send errors in Windwos Event Viewer, Intel(R) Dual Band Wireless-AC 8260 : Has encountered a conflict in resources and could not load.
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?
Looking at the symptoms, it seems there is a problem with the 18.33.6.2 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. If I disabled the Intel 7260AC adapter and using a wired Broadcom ethernet connection, everything worked normally again.Īfter disabling IPv6 on the Intel 7260AC, the wireless network ALSO worked again without hanging. Once an application 'hung', it could not be terminated from task manager, giving an 'access denied' error when attempting and 'end task'. I have an Intel dual band 7260AC for desktop installed with IPv4 and IPv6 enabled, driver version 18.33.6.2 from the wireless proset version 19.50.1Ī 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. I was previously running Windows 10 64-bit Anniversary edition 1607 without any problems.
0 kommentar(er)
