Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Patch Tuesday brings some surprises, some early crashes, and a surreal solution

  • Please log in to reply
No replies to this topic

#1 JohnC_21


  • Members
  • 24,638 posts
  • Gender:Male
  • Local time:02:07 AM

Posted 12 April 2018 - 12:57 PM

Windows 7 and Server 2008R2 continue to get beaten into the ground, and the Win10 1709 patch prompts complaints, as the Windows security patching business gets even more complex.
As Dustin Childs notes on the Zero Day Initiative site, five of the critical bugs are variations on an old, tired theme: a “bad” font can take over your machine, if you’re running in admin mode. And it doesn’t matter where the font appears — on a web page, in a document, in an email. Don’t you just love it when fonts get rendered inside the Windows kernel?
Twilight Zone
That leaves us with two other significant bugs in the old Win7 patches. Microsoft describes them like this:
A new Ethernet Network Interface Card (NIC) that has default settings may replace the previously existing NIC, causing network issues after you apply this update. Any custom settings on the previous NIC persist in the registry, but are unused.
Static IP address settings are lost after you apply this update.
As of this moment, it looks as if the manual Win7 Security-only patch KB 4093108 fixes the phantom NIC bug and static IP zapping bug — but the Monthly Rollup, KB 4093118, does not. That puts us in a surreal situation where Microsoft recommends that those installing the (automatically pushed) Monthly Rollup first install the (manual download) Security-only patch.
In other news
Brad Sams reports that KB 4093112, the cumulative update to 1709, has messed up File Explorer — he can’t open File Explorer at all, even after two restarts.
We have reports that the same update is causing Windows to complain that it hasn’t been activated. Multiple reboots solved the problem.
And we have another report of a blue screen PAGE_FAULT_IN_NONPAGED_AREA error 0x800f0845 with the same patch.




BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users