KB4457139 – Windows Server 2008 NIC Issues
We have over the last week or so had problems with Windows Server 2008 servers where, although they seem to be connecting through the network without any problems, like filestores, the servers could not be remoted onto and when running an ipconfig would return no data.
You can see the number of Microsoft Updates that have been problematic for Windows users that have been released over the last few months by looking through our articles here.
A lot of the recent issues have been either network card or wireless related and it does seem very strange that this just seems to keep happening. Are Microsoft trying to push everyone onto Windows 10 and Server 2016? Surely they wouldn’t do that, would they?
KB4457139 – (Preview of Monthly Rollup)
So the update you should be looking out for now is KB4457139. This is a preview of monthly rollup for Windows operating systems. Below is directly from the updates KB page explaining exactly what the problems are in relation to this latest release.
Note that Microsoft have very kindly included a “workaround” – would be nice if they didn’t screw it up in the first place though wouldn’t it?!
Known issues in this update
|After you apply this update, the network interface controller may stop working on some client software configurations. This occurs because of an issue related to a missing file, oem<number>.inf. The exact problematic configurations are currently unknown.|
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.
We have just rebooted the servers with this update and they do seem to be fine after that, so not as bad as recent updates.
If you are still experiencing any weird issues with your machines, take a stab at removing this dodgy update and see if it helps.
How to Remove Problem Updates
If you need some guidance on what to do to remove these or any other updates, be it on a single machine or mass corporation remove, take a look at this post as we have added some instructions towards the end of the post that you may find helpful.
Who knows, in the future far, far away, we may be able to go a week without Microsoft releasing a dodgy update!