This problem seems to be nearly identitical to what @FFayz reported in "Intel 3165 losing connection to wi-fi". @LeoC_Intel recommended I open this separate thread.
I have a fresh and fully-updated installation of Windows 10 Pro on my computer. Though I have configured the PC's wireless network to "connect automatically", it does not do so. If, for example, I reboot the computer, it does not connect to the wireless network. I have to manually connect it. The driver and version that shows in the wifi properties is Intel(R) Dual Band Wireless-AC 3165 19.51.21.1, which appears to be the latest version. I nevertheless did try downloading "WiFi_21.10.1_Driver64_Win10.exe" and installing it, but the installer silently quit after a couple of seconds displaying a rotating cursor.
I have followed the instructions in the above-referenced thread to generate event logs while reproducing the problem. While initially connected to the "PlazaLofts" wireless network, which is configured to "connect automatically", I:
- Cleared the System and WLANAutoConfig event logs.
- Connected to the "quiche - 5GHz" wireless network (thereby dropping the connection to the "PlazaLofts" network).
- Disconnected from the "quiche - 5GHz" network.
- Verified that the "PlazaLofts" network is still configured to "connect automatically".
- Waited for a couple of minutes. The machine did not automatically reconnect to the "PlazaLofts" network.
Please note that this problem with reconnects occurs with other wireless networks I have tried.
Please find the System event log and the WLANAutoConfig event log. Also, I have filled out what I can in the Intel Windows WiFi Issue - Customer Info Request.
链接已复制
For others who are likely experiencing the same issue, I wanted to point out that Intel has released a new driver version as of August 13, 2019. The release notes state:
Wi-Fi connection may have no internet access after resume from sleep/hibernation mode or system restart.
I am disappointed that @LeoC_Intel at no time acknowledged that the Intel driver might be the cause of the issue, instead blaming it on the "integration and the OS".
It is possible he is right, as installing the new driver did not fix my issue, despite the fact that the new version was specifically intended to fix issues like mine.
Roger
