News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Microsoft acknowledges bug in Win8.1 March Monthly Rollup KB 4489881, fixes it in Monthly Rollup Preview

    Posted on April 3rd, 2019 at 14:17 woody Comment on the AskWoody Lounge

    I’ve seen a couple of reports where Server 2012 R2 (Win8.1) users who installed this month’s Monthly Rollup, KB 4489881, are hitting unexpected reboots and BSODs.

    Microsoft recently acknowledged the problem:

    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 fix is to install the preview of next month’s Win 8.1/Server 2012 R2 Monthly Rollup, KB 4489893:

    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.

    I guess we have to get used to the fact that Microsoft’s going to fix bugs in Win7 and 8.1 Monthly Rollups by slipping them into the preview of the next month’s Monthly Rollup.

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Microsoft acknowledges bug in Win8.1 March Monthly Rollup KB 4489881, fixes it in Monthly Rollup Preview

    This topic contains 25 replies, has 15 voices, and was last updated by

     PKCano 1 week ago.

    • Author
      Posts
    • #348476 Reply

      woody
      Da Boss

      I’ve seen a couple of reports where Server 2012 R2 (Win8.1) users who installed this month’s Monthly Rollup, KB 4489881, are hitting unexpected reboot
      [See the full post at: Microsoft acknowledges bug in Win8.1 March Monthly Rollup KB 4489881, fixes it in Monthly Rollup Preview]

      2 users thanked author for this post.
    • #348487 Reply

      mlmarshal
      AskWoody Plus

      I’ve been having what appear to be similar problems with my 1809 (17763.379) installation. Can’t tell if it’s WinX, hardware or software based!

      [In photography,]
      Amateurs worry about gear;
      professionals worry about money;
      masters worry about light.

    • #348512 Reply

      anonymous

      I can testify… Had a user on 8.1 Pro kept BSOD’ing she rebooted 4x and by the time I came to work her machine would BSOD before the login screen, nothing but a reformat would fix it, couldn’t get it to a point of installing the preview.

    • #348517 Reply

      DrBonzo
      AskWoody Lounger

      How does one tell if a computer has a winsock kernel client? I’m assuming one can tell if Skype for Business or Lync Server Edge Transport is present by snooping through Windows\Program Files, etc.

    • #348547 Reply

      DAVe3283
      AskWoody Plus

      This bug is listed for the March security-only patch as well. Is there any indication the April security-only patch will provide the resolution? I suppose we will have to wait and see, but this kind of situation always makes me nervous that they will hold stability over the heads of the security-only group.

      Though, to Microsoft’s credit, they have for the most part resolved this kind of thing in a security-only patch or sometimes a dedicated hotfix. Here’s hoping that trend holds.

      • #348564 Reply

        WildBill
        AskWoody Plus

        This bug is listed for the March security-only patch as well. Is there any indication the April security-only patch will provide the resolution?

        Now somebody tells me! I just installed updates today, including KB4489883 from the Microsoft Catalog. (Security-only, Group B). No BSOD’s yet; I have Skype, but not Skype for Business or Lync. If it starts happening, I can restore from backup, then reapply all updates except the KB from the catalog, then wait for a hotfix or the April Security-only patch.

        Windows 8.1, 64-bit, now in Group B!
        Wild Bill Rides Again...

    • #348598 Reply

      mn–
      AskWoody Lounger

      … Would it make sense to note this in the Master Patch List? Please?

      Because that currently shows 4489881 and 4489883 as “safe to install: yes”

    • #348626 Reply

      Klaas Vaak
      AskWoody Lounger

      And I thought Win 8.1 was relatively safe from this kind of [nonsense]. Has M$ changed its ways? Has it learned anything from the mess it caused during the past 2 years? Perhaps it learned that plenty of home users will stick with Windows no matter what, so there is no need to change its ways.

      1x Linux Mint 19.1 | 1x Linux antiX

      1 user thanked author for this post.
      • #348839 Reply

        Hopper15
        AskWoody Lounger

        And I thought Win 8.1 was relatively safe from this kind of [nonsense]. Has M$ changed its ways? Has it learned anything from the mess it caused during the past 2 years? Perhaps it learned that plenty of home users will stick with Windows no matter what, so there is no need to change its ways.

        Microsoft didn’t learn anything.

    • #348915 Reply

      anonymous

      What I do not care for much is the new MS protocol of packaging bug fixes in the next month preview quality rollup update. This puts users in a difficult situation if the bug afflicts their system, namely living with the problem if possible or becoming an unpaid beta tester for the upcoming month preview. Every month the updates have had problems and I have not installed either February or March updates, letting the attack surface of my system to widen while waiting for a clean month to get caught up. This is clearly the downside of cumulative updates regardless of the party line from Redmond.

    • #349229 Reply

      Bruce.S.Jaffe
      AskWoody Plus

      DrBonzo earlier posted the question: “How does one tell if a computer has a winsock kernel client? ”

      I, too, would be interested in the answer to that question.

      Before applying KB4489881, it would be nice to be able to determine the possibility that this patch could potentially cause some grief, in which case it might be advisable to hold off until a fix is available, e.g., until the April follow-up has been proven.

      1 user thanked author for this post.
      • #349280 Reply

        DrBonzo
        AskWoody Lounger

        Yes, exactly. It would be extremely useful to know if this is something a “typical” home user needs to worry about, or whether it’s something only corporate users of network applications need to worry about, or,…

        I found some Microsoft pages about winsock kernels, but other than the fact that it has something to do with networks (and, I think, how data is moved around a network), I just don’t have the technical background to make much, if any, sense out of it.

        I realize there’s a fix for the bug, but it’s in the March 19 preview, and I never install previews. If the solution in the preview makes it into the April Rollup which in turn has another bug that’s fixed in a preview, then 8.1 users will be sent up a creek.

        I’d appreciate any enlightenment folks can provide.

        • #349281 Reply

          PKCano
          Da Boss

          Just some information on how Monthly Rollups and Preview Rollups work.

          The Monthly Rollup/CU (Patch Tues Update) is composed of three parts: security patches, non-security patches and the IE11 Cumulative Update. It is classified as a Security Update, checked important in Win7/8.1 and delivered through Windows Update automatically in Win10.

          The Preview Rollups/CUs are composed of four parts: security patches, non-security patches, the IE11 Cumulative Update. and the non-security updates for the coming month. They are classified as Non-security. As such, they are unchecked optionals in Win7/8.1. In Win10, depending on your settings, you need to be a “seeker,” with no restrictions or deferrals, to get them, and then sometimes you still don’t see them through Windows Update.

          The Preview Rollups/CUs are often bug fixes for previous issues, sometimes non-security changes. They are meant primarily for testing in the corporate environment and by those technically savvy. They are not meant for general consumer distribution. That is why they are unchecked optionals and “seeker” fodder.

          1 user thanked author for this post.
          • #349386 Reply

            DrBonzo
            AskWoody Lounger

            @pkcano – Thanks. I think I understand – and understood – your description of the various kinds of updates. And yet I sense that you have detected a flaw in my deduction about Win 8.1 users possible being up a creek. Please let me know if I’m in error about my conclusion!

            • #349390 Reply

              PKCano
              Da Boss

              The fix will be included in the May Rollup.
              It depends on how the issue affects you whether or not you want to uninstall KB4489881 (if you installed it) or risk the Preview Rollup if you feel the necessity.

            • #349628 Reply

              DrBonzo
              AskWoody Lounger

              I’m trying to get a handle on how likely a Win 8.1 computer is to go BSOD given the current winsock issue. But that’s just about impossible to do without knowledge of what a winsock is, and unfortunately for me all the descriptions I’ve come across are above my pay grade.

              I’m wondering things like: Are all 8.1 machines likely to get hit? Is there something about the machines that have been hit that makes them susceptible? Is a machine more likely to get hit if it’s connecting to a particular type of server? Or connecting and then using a particular type of application?, etc., etc, etc.

              Even the BSOD Win 7 fiasco from Summer of 2017 eventually yielded to some clues about which machines were more likely to get hit.

            • #349631 Reply

              PKCano
              Da Boss

              I have updated four (4) Win8.1 machines without a problem.

              2 users thanked author for this post.
            • #349737 Reply

              Microfix
              Da Boss

              Updated 2 x64 and 1 x86 W8.1 devices, also no problems.

              | W8.1 Pro x64 | Linux x64 Hybrids | W7 Pro x86 | XP Pro O/L
              1 user thanked author for this post.
            • #349969 Reply

              Bruce.S.Jaffe
              AskWoody Plus

              I thought I followed your explanation of monthly vs preview rollups, but I’m a bit confused over the timing.  According to Woody, the Winsock BSOD problem caused by the March monthly rollup 4489881 is fixed by the preview rollup 4489893 which was released on March 19.   Given the March release date, I assumed that this was a preview of the following month’s rollup (i.e., the April monthly rollup), but you indicated that the fix will not actually be available until the May monthly rollup.  Does this imply that preview rollups are actually two months in advance rather than one, or am I missing something?  Thanks.

            • #349971 Reply

              PKCano
              Da Boss

              If it’s fixed in the Preview, it should be included in the next month’s Rollup (Patch Tues immediately following). So, the 2019-03 Preview should be included in the 2019-04 Rollup.

              “Should” both times.

              1 user thanked author for this post.
    • #349329 Reply

      NightOwl
      AskWoody Lounger

      @ DrBonzo

      I found some Microsoft pages about winsock kernels, but other than the fact that it has something to do with networks (and, I think, how data is moved around a network), I just don’t have the technical background to make much, if any, sense out of it.

      I too did a search on *winsock kernels* and found the same *technical* websites at Microsoft. Definitely one or two pay grades above my skill set. But, I got the impression that if Windows accesses a network connection, then the winsock kernel is probably involved in some way. So, my guess is that if you have a hookup to the internet, then you are probably using the winsock kernel. I don’t think it just refers to a *home network* vs a *business network*–probably *all* networks.

      Having said all that, I installed the monthly rollup KB4489881 to my Win8.1 system, and have been running it for the last day, or so. Multiple re-boots for testing and various other tasks–so far, no problems. I will report back if that changes … well, I guess if I have a BSOD–maybe I won’t be able to report back! (Just kidding–I have other options–restore a system image that’s prior to updating my Win8.1, or boot to Win7–have a multi-boot setup!)

      NightOwl

      No question is stupid ... but, possibly the answers are 😉 !

      1 user thanked author for this post.
    • #349387 Reply

      DrBonzo
      AskWoody Lounger

      @nightowl – Thanks for your take on winsock kernals; it does make sense. I’ve got the good old system image and a factory reset flash drive, but I’m not fond about using them. Let us know how things progress for you. Not to be a downer but I’ve read somewhere that the BSODs start a day or so after the patch install.

      Good Luck!

    • #349697 Reply

      bruce.chaser
      AskWoody Lounger

      I to must report that my Win8.1 machine had problems.
      The system froze after a few minutes into boot.

      I havent seen the Win8.1 freeze for years, and I’m not exaggerating.

      I manage about 160 client workstations since 2012, all Win7 except 2 Win8.1.

      Go figure.

    • #349983 Reply

      EP
      AskWoody_MVP

      I have installed KB4489881 a few weeks ago and no BSOD problems on my dad’s Toshiba C55Dt-A laptop with pre-installed Win8.1.

    • #350675 Reply

      anonymous

      FYI, I was one of those home users affected by kb4489881 on 8.1- the BSODs started about a day after installing updates.  I was lucky, only got one error a day – some people had it happen much more frequently.  The error messages/logs indicated an NVIDIA video driver was involved so I updated to the latest driver version.  Still got the daily BSOD but with a different message about IRQs.  Finally tracked it to the update and uninstalled it – so far so good.   Today the April patches came up in Windows Update – am wondering if anyone can verify that the problem is indeed fixed in them.  So far I can only verify that last months ‘rollup preview’ was fixed.  I’d assume the fix is in this months update but I’ve learned to ‘never assume’ with Windows Updates.  Thanks!

      • #350687 Reply

        PKCano
        Da Boss

        The March Preview is contained in the April Monthly Rollup. So that issue has been fixed.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Microsoft acknowledges bug in Win8.1 March Monthly Rollup KB 4489881, fixes it in Monthly Rollup Preview

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: