Warning: technical post with rant.
Because I’m a baby geek, I have my Windows Updates set to notify but not install. This gives me the chance to look at all the updates and decide which ones to install and which ones to ‘hide’.
Because of ‘known issues’ such as this one:
There is an issue with Windows and a third-party software that is related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working.
Not ‘may stop working’ but ‘will stop working’. Ut oh.
Note: a ‘known issue’ is a problem introduced into the system by the update that the Microsoft developers couldn’t fix in time for that update. The problem with the ‘network interface controller’ [lovingly known as NIC] not working is that your internet connection stops working too.
Most of these ‘known issues’ get fixed as part of the next round of updates, so it pays not to be an early adopter. Sometimes, however, a ‘known issue’ comes with a workaround, or a fix. The fix for the ‘known issue’ with the NIC is this:
To locate the network device, launch devmgmt.msc; it may appear under Other Devices.
To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
a. Alternatively, install the drivers for the network device by right-clicking the device and choosing Update. Then choose Search automatically for updated driver software or Browse my computer for driver software.
I’m not a complete n00b when it comes to my computer, and I do know how to install drivers, but it seems to me that something is missing from step 1. Where am I supposed to launch ‘devmgmt.msc’ from? I suspect it’s the Run command line but I’m not sure.
The alternative might be easier as I think I know where to find the device listing, but if the old driver has been corrupted during the ‘problem’, I have no idea what driver the pc will re-install.
Will I have to dig out the very old motherboard setup disk which I may or may not be able to find?
Or will I have to carry my pc down to the repair shop to get someone more knowledgeable to ‘fix’ the update problem for me?
For all these reasons, I have not installed that particular update, but Microsoft continues to sneak it in under each successive optional ‘quality rollup’. It’s become so ridiculous that I just have to look at the size of the update – 229.2 MB – to know what’s in it.
When I first started ignoring this nasty update, I did so because I expected Microsoft to resolve this ‘known issue’ in much the same way as they resolve most other ‘known issues’. Better late than never, right?
Unfortunately, Microsoft has no intention of resolving this particuler issue. Or perhaps they can’t. Just for fun, I followed the link to More Information today and followed the trail of updates back as far as March 13, 2018 before I gave up. The issue with the NIC, and it’s nasty fix, were repeated in each and every update.
So now I’m wondering what happened to other Windows 7 users out there. Did they all install the original nasty update, fix their pc’s and move on? Or was there a tsunami of outrage that I missed?
I’m never going to install this update until Microsoft resolves the issue because this is a problem of their own making, and no company is so big that it should be allowed to get away with such obvious cheating.