- May 19, 2011
- 21,631
- 16,908
- 136
Something odd happened on a customer's computer today. It was built in 2014, Haswell gen, and the customer upgraded it from Win81 to Win10 about a month ago.
I was fixing some unrelated bits (e.g. Nuance's PDF viewer and some printer settings) when I noticed that an update was waiting to install and as I needed to restart the computer anyway, I picked that time to do it.
When the machine rebooted, the network interface couldn't get an IP. I already had to reboot the wireless router earlier because the printer (connected via wifi and USB) wasn't printing from the desktop PC over wifi. I did the usual things to try and get the interface working again, ipconfig /renew, disable/enable the adapter, nothing. Reboot the computer, no difference. I tried setting static IP settings that I knew would be fine with that router, but it still couldn't ping the router. After running out of other ideas (such as cutting the amount of network services bound to the adapter down to IPV4 and that's it), and logically the last (possibly relevant) change made was the Windows update that had gone on, so I removed it and rebooted. Still no difference. Running low on ideas (there's no security software on the computer except what comes with Win10), I decide to try shutting down the computer and at the same time I'd reboot the router again.
When both come back up, the computer can get an IP again, and all is good. Not exactly satisfied with things, I decide to install the update again. I do that and reboot, the interface doesn't work again. I remove the update again and reboot, still off. I think, "well, it came back on after switching off the PC and back on again", so I try that and the interface works again.
I try this a couple more times, same thing each time, reboot the computer and the interface goes off, switch it off and back on again, the interface works fine. The update doesn't *seem* to be triggering the problem, but why did this problem only start today?
Running low on ideas again, I decide that if I'm going to leave the problem 'as is' with a workaround that consistently works, then I ought to try and make the platform as ideal as possible. The NIC is an onboard Intel I217-V adapter, so I downloaded the latest updates from there, unzip and install them through Device Manager.
Since doing that, the problem appears to have completely disappeared, no amount of sleep / reboot / power-cycle makes any difference. However, why did it start today?
Anyway, if anyone has any network connectivity shenanigans with recent Win10 updates, it might be worth bearing this in mind.
I was fixing some unrelated bits (e.g. Nuance's PDF viewer and some printer settings) when I noticed that an update was waiting to install and as I needed to restart the computer anyway, I picked that time to do it.
When the machine rebooted, the network interface couldn't get an IP. I already had to reboot the wireless router earlier because the printer (connected via wifi and USB) wasn't printing from the desktop PC over wifi. I did the usual things to try and get the interface working again, ipconfig /renew, disable/enable the adapter, nothing. Reboot the computer, no difference. I tried setting static IP settings that I knew would be fine with that router, but it still couldn't ping the router. After running out of other ideas (such as cutting the amount of network services bound to the adapter down to IPV4 and that's it), and logically the last (possibly relevant) change made was the Windows update that had gone on, so I removed it and rebooted. Still no difference. Running low on ideas (there's no security software on the computer except what comes with Win10), I decide to try shutting down the computer and at the same time I'd reboot the router again.
When both come back up, the computer can get an IP again, and all is good. Not exactly satisfied with things, I decide to install the update again. I do that and reboot, the interface doesn't work again. I remove the update again and reboot, still off. I think, "well, it came back on after switching off the PC and back on again", so I try that and the interface works again.
I try this a couple more times, same thing each time, reboot the computer and the interface goes off, switch it off and back on again, the interface works fine. The update doesn't *seem* to be triggering the problem, but why did this problem only start today?
Running low on ideas again, I decide that if I'm going to leave the problem 'as is' with a workaround that consistently works, then I ought to try and make the platform as ideal as possible. The NIC is an onboard Intel I217-V adapter, so I downloaded the latest updates from there, unzip and install them through Device Manager.
Since doing that, the problem appears to have completely disappeared, no amount of sleep / reboot / power-cycle makes any difference. However, why did it start today?
Anyway, if anyone has any network connectivity shenanigans with recent Win10 updates, it might be worth bearing this in mind.
Last edited:
Facebook
Twitter