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
  • And now we know why the Win10 version 1809 updates got blocked

    Posted on February 5th, 2019 at 08:12 woody Comment on the AskWoody Lounge

    Last night, Microsoft officially announced the reason why its Win10 version 1809 cumulative updates were having problems. Remember the Update Servers having hiccups? Yeah, that’s the bug.

    Here’s the official reason:

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

    Home Forums And now we know why the Win10 version 1809 updates got blocked

    This topic contains 11 replies, has 8 voices, and was last updated by

     abbodi86 1 week, 4 days ago.

    • Author
      Posts
    • #321530 Reply

      woody
      Da Boss

      Last night, Microsoft officially announced the reason why its Win10 version 1809 cumulative updates were having problems. Remember the Update Servers
      [See the full post at: And now we know why the Win10 version 1809 updates got blocked]

      4 users thanked author for this post.
    • #321531 Reply

      b
      AskWoody Plus

      on January 29, 2019. The issue was resolved on the same day

      That’s a stretch when all the complaints started rolling in on January 30 and 31.

      Why was it just 1809, or even just Windows 10 though? (Perhaps we’ll never know.)

      (Woody commented as I was typing this afterthought.)

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

      • This reply was modified 1 week, 4 days ago by
         b.
      • This reply was modified 1 week, 4 days ago by
         b.
      1 user thanked author for this post.
      • #321538 Reply

        woody
        Da Boss

        Yep, and the explanation apparently only applies to Win10 1809 cumulative updates. The complaints covered all Windows versions – and Office versions – everything through Windows Update, if I recall….

        • #321600 Reply

          Susan Bradley
          AskWoody MVP

          I didn’t see it on my 1803 laptop at home.  At the office I’m behind WSUS and didn’t see it.  One vendor caused issues with Azure/Windows update and what else?

          Susan Bradley Patch Lady

      • #321560 Reply

        Arvy
        AskWoody Lounger

        on January 29, 2019. The issue was resolved on the same day

        That’s a stretch when all the complaints started rolling in on January 30 and 31.

        Not necessarily a big stretch depending on how one defines “resolved”.  The problem with the “external DNS service provider” may have been fixed within 24 hours, but any corrections for DNS issues can take considerably longer to propagate throughout the system.

        As for a DNS issue being limited to a single W10 release, it would be a bit of a stretch to imagine how that situation would occur.   More likely, I think, that we current version users just get preferential explanations. 😉

         

        Asus ROG Maximus XI Code board; Intel i9-9900K CPU; 32 GB DDR4-3600 RAM; Nvidia GTX1080 GPU; 2x512 GB Samsung 970 Pro M.2 NVMe; 2x2 TB Samsung 860 Pro SSDs; Windows 10.1809; Linux Mint 19.1; Terabyte Backup & Recovery
        • This reply was modified 1 week, 4 days ago by
           Arvy.
        • This reply was modified 1 week, 4 days ago by
           Arvy.
        • This reply was modified 1 week, 4 days ago by
           Arvy.
    • #321570 Reply

      NetDef
      AskWoody_MVP

      DNS changes, regardless of each zone entries time to live, can take anywhere from near instant up to 48 hours to propagate from the root name-server to all the public DNS servers around the world.  And it’s not consistent even on the same systems day to day.  (Which is why I try hard to make DNS changes on a Friday evening for businesses.)

      Regardless of all that, this seemed to take longer than that.  Bad caches?  Glitch in the propagation systems?

      DNS Flag day = my suspicion that a lot of providers applied last minute updates to their systems . . .

       

      And yes, this seemed to hit all consumer WU services, not just for 1809.  Oddly I did not see any sign that it hit WSUS – at least not on my servers.

      ~ Group "Weekend" ~

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

        Arvy
        AskWoody Lounger

        Regardless of all that, this seemed to take longer than that. Bad caches? Glitch in the propagation systems?

        Very likely.  The backbone is not usually a problem, but various service provider connections thereto use all kinds of caching and other “neat tricks” for conserving their own bandwidth.  And, as you say, at least some of them were probably in the midst of “flag day” revisions to their systems.

        Asus ROG Maximus XI Code board; Intel i9-9900K CPU; 32 GB DDR4-3600 RAM; Nvidia GTX1080 GPU; 2x512 GB Samsung 970 Pro M.2 NVMe; 2x2 TB Samsung 860 Pro SSDs; Windows 10.1809; Linux Mint 19.1; Terabyte Backup & Recovery
        1 user thanked author for this post.
    • #321592 Reply

      b
      AskWoody Plus

      It took a full week for some in the UK to get WU back via BT:

      Re: Windows update problems

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

      • #321601 Reply

        Arvy
        AskWoody Lounger

        Surprising that British Telecom’s DNS servers would be that slow to update, but UK DNS reliability in general varies quite widely.  A few of their systems (see here) are rated less that 60% reliable.

        Asus ROG Maximus XI Code board; Intel i9-9900K CPU; 32 GB DDR4-3600 RAM; Nvidia GTX1080 GPU; 2x512 GB Samsung 970 Pro M.2 NVMe; 2x2 TB Samsung 860 Pro SSDs; Windows 10.1809; Linux Mint 19.1; Terabyte Backup & Recovery
    • #321598 Reply

      gborn
      AskWoody_MVP

      @woody: Concerning your question, if only Win 10 V1809 was affected. According to my blog post Windows Update Service globally disturbed? (01/31/2019) I had trouble reaching Windows update service from Windows 7 SP1 and Windows 10 V1809 clients.

    • #321650 Reply

      Rick Corbett
      AskWoody_MVP

      I must admit that I don’t understand why the “external DNS service provider” for this particular incident is not being named (so, perhaps, we could choose to avoid in future… even though glitches could strike elsewhere). Seems rather coy…

      Just a thought…

    • #321985 Reply

      abbodi86
      AskWoody_MVP

      They only try to be transparent with 1809, so they added the note to its page, specially that it affect Feature Update Upgrade

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

    Reply To: And now we know why the Win10 version 1809 updates got blocked

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

    Your information: