Jump to content

Windows Update KB4489881 Causing BSODs, Fix Included in KB4489893 Preview


The AchieVer

Recommended Posts

The AchieVer

Windows Update KB4489881 Causing BSODs, Fix Included in KB4489893 Preview 

We’re only a few hours away from the moment Microsoft will push the green light for a new batch of Patch Tuesday security updates, but in the meantime, Windows 8.1 users might have to deal with issues introduced by an older release.

 

We’re only a few hours away from the moment Microsoft will push the green light for a new batch of Patch Tuesday security updates, but in the meantime, Windows 8.1 users might have to deal with issues introduced by an older release.

The Windows 8.1 March monthly rollup, labeled as KB4489881, is causing BSODs on a number of devices. Some users say their PCs also reboot all of a sudden, as per AskWoody.

Microsoft has already acknowledged the bug, and explained in a short update on the official KB page what exactly goes wrong on impacted devices.

“After installing this update, devices with a winsock kernel client may receive D1, FC, and other errors. Additionally, systems that run the Skype for Business or Lync Server Edge Transport role may be affected by this issue,” the company notes.Fix already availableMeanwhile, Microsoft has published a preview of the April 2019 Patch Tuesday rollout which allows users to try out the new monthly rollup in advance.

Listed as KB4489893, this new update resolves the BSODs mentioned above, with the last line of the changelog explaining the following:

“Addresses an issue in which devices with a winsock kernel client may receive D1, FC, and other errors and affect systems that run the Skype for Business or Lync Server Edge Transport role.”

While the fix is only part of a monthly rollup preview update, it will be included in the next update for Windows 8.1 devices this week. In other words, if you’re hitting errors like the ones mentioned above, including BSODs, you should definitely install the new monthly rollup going live tomorrow to resolve it.

For the time being, these issues don’t seem to impact other Windows versions, like Windows 7, but on the other hand, devices running Windows Server 2012 R2 could see similar errors too.
 
 
 
 

 

Link to comment
Share on other sites


  • Replies 0
  • Views 609
  • Created
  • Last Reply

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...