How to proceed if WiFi problem is detected at the network card driver level? Those lines in the device manager are the real evidence. I practiced it on two laptops.

I have two laptops at home, a five-year-old Lenovo Xiaoxin and my wife’s Honor MagicBook. The symptoms are surprisingly consistent.: The WiFi is stuck for two seconds, the browser spins in circles, and then it is fine again. This is my fault The article that breaks at the correlation layer After a round of troubleshooting, the power saving hook was also cancelled, and it happened again after a while. Last month, I finally made up my mind to dig into the bottom layer - drive. After digging, I discovered that this layer of water was deeper than I thought.: The newer the driver, the better. Windows will replace the driver back to a version that it considers "appropriate" while you are not paying attention. A few lines of inconspicuous small words in the device manager are worth more than any "try restarting".

Let’s talk ugly things first: Most WiFi problems are not caused by the driver. The mobile phone cannot be connected, but other computers are normal. Don’t touch the driver yet. ——Nine times out of ten, it's something on the router side or the signal. Driver-level troubleshooting is applicable to very narrow scenarios: The problem only starts after this machine has a problem, the power saving hook has been canceled, the system has been reinstalled, or a major version has been upgraded. If you don't know the number, go read what I wrote before. Five true murderers in a flash and Drop log reason code Those two articles are more to the point. This article is about the last road: The evidence does point to the network card driver itself, how to proceed.

Those few lines of fine print in the device manager, you must first learn to read them and then use them

Right-click the Start button → Device Manager → Network Adapters, double-click your wireless network card, and switch to the "Drivers" tab. Most people's action is to click "Update Driver" directly, which is wrong. Read three lines first: Driver date, driver version, digital signer .

Each of these three lines says one thing. If the driver date is from the year the system was installed, or even earlier, 80% of the time it is a universal version installed by Windows itself. ； The driver version is a series of dotted numbers, such as 1064.34.705.2019. It matches the number on the official website driver page, and you will know which version you are running now. ； If the signer is Microsoft Windows Hardware Compatibility Publisher, it means that the driver has passed WHQL certification and the probability of something serious is low - if it is "unsigned" or empty, the origin of the driver will be suspicious. The driver date of my Lenovo Xiaoxin is June 2021, and the machine was reinstalled with Win11 in 2024. This means that on the day of reinstallation, Windows conveniently stuffed an old driver from three years ago into it, and it has been running until now. If you don’t read this line of fine print, you’ll never know which version you’re on.

By the way, an entrance question: There is also the "Details" tab in the lower right corner of the Device Manager, and the string PCI\VEN in the "Hardware ID" attribute_8086&DEV_The characters starting with 2723 are the real ID card of the network card. VEN_8086 is Intel, VEN_10EC is Realtek, VEN_14C3 is MediaTek. When the driver cannot be found on the official laptop website, searching with this string of IDs is much more accurate than searching with the machine model - the same model of laptop may have two or three different network cards installed, and there are several official website driver packages packed into one package. If you install the wrong one, your work will be in vain.

Updating the driver will be a waste of time if the order is reversed.

If you click the "Update Driver" button provided by Windows, it will go to Microsoft's driver library to find it. What you find is often a universal version, or a version older than what you have now. The right way is to bypass it and install it yourself with a dedicated driver. My order is:

• Intel network card: The "Intel Driver and Support Assistant" on the official website is installed with automatic model recognition and a download button directly on the web page.
• Realtek and MediaTek: It is difficult to find the driver on the official website. Go directly to the official website of the notebook brand, enter the machine model, and download it under the network adapter category.
• Can't find any: Search for the hardware ID mentioned in the previous section. Make sure the VEN and DEV numbers match. Then download.

There is one step before pretending that I have never done before, but I must do it now.: Copy the current driver date and version . The reason is immediately clear, this is a life-saving action. Restart after installation, use netsh wlan show interfaces Knock it again to see if the negotiation rate and channel are normal, and then see if the two seconds of lag is still a problem. After my new machine was replaced with the 2024 Intel dedicated driver, the lag dropped from seven or eight times a day to once a day or two - it was not cured, but the magnitude changed, which shows that the driver is indeed one of the faults, but there are other factors involved.

Is the new version of the driver causing problems? The back button is reserved for this time

This is the most counter-intuitive thing about the driver layer: New driver does not mean good driver . My wife’s Honor has a Realtek network card. I downloaded the latest 2025 version from a certain driver station and installed it. That night, the WiFi started to convulse and cut out every two to three minutes. It was worse than before the installation. This is the use of copying the version number - click the "Return Driver" button in the driver tab, and the system will return to the previous version, which can be solved in one minute.

Two details are mentioned above. First, the "Rewind Driver" button is usually gray. It only lights up after a new driver is installed, and it only goes back one step - if you install two bad versions in a row, it can only go back to the second to last one, but not the original one. So don’t be too quick to install the drivers. Try one at a time and quit if it doesn’t work. Second, take a look at the power saving hook after exiting. I'm in this trap The article about network card power saving Mentioned it once: Once the driver is replaced, there is a chance that the "Allow the computer to turn off this device to save power" checkbox in the power management will change back on its own. It is a rule of thumb in my house that you must check the power saving hook after the drive is started. Checking it only takes ten seconds.

If the back button is grayed out and you really want to go back to an earlier version, just go to the laptop's official website and install the old version. The driver package allows version downgrade installation without uninstalling it first.

The biggest pit: Windows will quietly replace the driver

The above are all slow efforts, and the real pitfall is here. You choose and install the driver yourself, and Windows Update will replace it with the version in its own library one night when you restart. , without any pop-up prompts. Your WiFi starts to have problems the next day, and you don't know why even if you want to break your head - it was clearly fixed the day before yesterday. The first time I encountered this problem, I thought the driver was broken again, so I reinstalled it three times. It wasn't until I finished installing the driver that I left the Device Manager open and closed, and when I came back the next day to see that the driver date had changed, I finally found out the current situation.

The way to close this hole: Settings→Windows Update→Advanced Options→Optional Updates, take a look at "Driver Update" to see if your network card is listed. If so, uncheck it first. More thoroughly, in the Device Manager, go to the Driver tab → Update Driver → Browse My Computer → Let me select from the list and manually lock the current version - Windows Update will be much more honest if I try to touch it later. This method does not guarantee 100% blocking. When a major version of Windows is upgraded (such as 22H2 to 23H2), it will still make its own decisions. After the upgrade, the driver layer fault recurs. The first thing to check is whether it has been replaced secretly. My current habit is that every time after a major version upgrade, I go to the device manager to see if the driver date is correct. It has become a muscle memory.

By the way, boundaries: This layer only deals with the problem of "the driver version has been changed". If all web pages cannot be opened after uninstalling a certain software, it is a matter of the protocol layer. netsh winsock reset That article talks about the right approach, don't mix up the two hammers. If the measured speed is only half of the negotiated speed, check first Three accounts of negotiated rate and measured rate , and don’t rush to blame the driver.

Which WiFi problems cannot be solved by the driver? A table to clarify them

After writing so much, I am afraid that someone will treat the driver as a universal hammer and smash it whenever there is a WiFi problem. What exactly should I think about? I wrote down the answers I saved over the past two years in a table.:

The order of using this table is: First check which row the first column corresponds to, and check whether it can be sorted by the second column before thinking about driving. The steps for canceling the power saving hook and the method for translating flash logs are listed in the previous link. When it comes to driving, remember this sequence.: Read the version→Copy the version→Install the special driver→Leave the back button for the bad version→Prevent Windows from being replaced. For WiFi problems that cannot be cured after this set of treatments, the problem is probably not in the machine, but on the other end of the router.—— three pings Go over and take a look to see who is losing packets in the router or network card, and the evidence will be there.

ending: Two sentences of experience driving this layer

After fussing with the two machines, I left two words for the driver layer. first sentence: The driver is a base, not a patch ——It determines whether the network card can work normally, but a normal driver cannot cure environmental problems such as poor signal and channel congestion. After correcting the driver, you have to go to the router to check the remaining problems. second sentence: Any conclusion that "the world is clean after installing the driver" should be made after a weekend. ——I initially thought that the Xiaoxin was cured, but it still jammed once the next day, but the frequency did drop from seven or eight times to one or two. This kind of "improved but not cured" conclusion is more honest and more useful than "completely cured."

Finally, leave a self-examination: Now open the device manager and check the driver date of your laptop's wireless network card. If it's still the year of installing the system, it's worth spending twenty minutes this weekend to get it right - you don't have to wait for it to get sick, the base is flattened first, and you can save yourself the blame for WiFi problems in the back row.