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 explains the confusion over .NET 1809 update KB 4481031

    Posted on January 24th, 2019 at 09:45 woody Comment on the AskWoody Lounge

    This is refreshing. Not the bugs, but the fact that we got a full explanation.

    (See Susan Bradley’s “Bring it on” post below.)

    You’ll recall my puzzlement over the .NET patch for Win10 1809, KB 4481031, released two days ago:

    • The patch was identified as a “Preview”
    • It was being sent out to seekers, and
    • It was also being sent out over Windows Update

    Which is a bizarre set of circumstances. At the time I guessed it was a big mess-up in the documentation. In fact, there was a little bit more happening.

    Per a new .NET blog post:

    The term “Preview” was removed from non-security Cumulative .NET updates for Window 10 version 1809 and Windows Server 2019.

    That explains the incorrect documentation. But there’s more.

    Per the updated KB 4481031 article:

    For 24 hours, this Jan 22, 2019 Cumulative Update for .NET Framework 3.5 and 4.7.2 (KB4481031) was made available broadly on Windows Update as an automatic update. As of January 23, 2019, this update is no longer offered on Windows Update as an automatic update, but rather only to “seekers” who go to Settings > Update & Security > Windows Update, and then select Check for updates, as is expected.

    I take great umbrage at that “as is expected” stinger. I would guess that 99.99% of all the folks who click Check for updates don’t realize that they’re going to get all of the patches currently waiting in the queue – without a chance to review or accept them.

    Anyway, it appears as if everything is now working the way it’s meant to work. Seekers and all.

    Thanks to Francis, posting anonymously.

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

    Home Forums Microsoft explains the confusion over .NET 1809 update KB 4481031

    Tagged: 

    This topic contains 9 replies, has 8 voices, and was last updated by  anonymous 2 months, 3 weeks ago.

    • Author
      Posts
    • #316089 Reply

      woody
      Da Boss

      This is refreshing. Not the bugs, but the fact that we got a full explanation. (See Susan Bradley’s “Bring it on” post below.) You’ll recall my puzzle
      [See the full post at: Microsoft explains the confusion over .NET 1809 update KB 4481031]

      7 users thanked author for this post.
    • #316106 Reply

      b
      AskWoody Plus

      I take great umbrage at that “as is expected” stinger. I would guess that 99.99% of all the folks who click Check for updates don’t realize that they’re going to get all of the patches currently waiting in the queue – without a chance to review or accept them.

      Has it ever been any different in the last four years?

      Will you still express surprise in another four years?

      You can rely on Automatic Update (turned on for all Technical Preview users) to eventually get the latest versions installed on your machine, but it wouldn’t hurt to prod manually as the bug you’re experiencing may already be solved. To run a manual update, click or tap Start –> PC Settings (on the left side of the Start Menu, remember?) –> Windows Update, then click or tap Check Now.
      Windows 10 tip 2: Update

      Cannon fodder Chump Daft glutton Idiot Sucker More intrepid Crazy/ignorant Toxic drinker Saluted blockhead "Finger sharpener" (Group ASAP) WX1903

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

        admin
        Da Boss

        Brilliant!

        That was for the original Win10 Tech Preview – four and a half years go.

        How times change!

        (And I’m flattered that you remembered.)

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

          Cybertooth
          AskWoody Lounger

          The problem is that users of previous Windows versions–XP, Vista, and Windows 7 and 8.x–were (reasonably) used to thinking that “check for updates” means exactly what it says: check for updates, period. Let’s see what’s available. Not “check for updates and then install them.” Now in Windows 10, they had no reason to expect the behavior to change when the phrasing didn’t.

          When users move over to Windows 10, is there a clear, prominent, and persistent notification in the UI that Microsoft has reinterpreted the plain meaning of “check for updates” to “check for updates and install them”?

           

          6 users thanked author for this post.
    • #316121 Reply

      anonymous

      This update got pushed to my work machine and killed my network connection. I uninstalled the update yesterday and after a few hours of trying, got my connection back. Last night it installs again, and now I’m back where I started. I’m no patch or network expert, and can’t find anyone else having this issue. Any chance you guys could help me sort it out? Apollo, I’m on mobile…

      • #316153 Reply

        PKCano
        Da Boss

        Can you please verify the KB number(s) of the update(s) that were installed on your computer in the last two days? There are two possibilities on v1809, a Cumulative Update for Windows KB4476976, and a .NET update KB4481031. It is important we know which one you are referring to.
        Thanks.

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

      Joulia.S
      AskWoody Plus

      The bugs must be really buggy  this month Woody

      as we’re still on MS – DEFCON – 2

      Waiting for the all clear from you,won’t update otherwise.

      Regards

      Joulia

      Windows 7,Home Premium 64 bit - Lenovo laptop
      Group A - Intel (R)Core i7 Processors -

    • #316393 Reply

      abbodi86
      AskWoody_MVP

      Soo “Seeker” apply to all updates, not just LCU and Feature Update
      that’s bad 🙂

    • #316428 Reply

      anonymous

      I never realised that “seeker” was official MS terminology.

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

    Reply To: Microsoft explains the confusion over .NET 1809 update KB 4481031

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

    Your information: