• Win10 1803 starts to roll out to Win10 users with “Semi-Annual Channel” and 180 day “feature update” deferral

    Home » Forums » Newsletter and Homepage topics » Win10 1803 starts to roll out to Win10 users with “Semi-Annual Channel” and 180 day “feature update” deferral

    Author
    Topic
    #312802

    If you have Win10 Pro update advanced options set for “Semi-Annual Channel” (which is to say, ready for business) and 180 days for “feature update” (w
    [See the full post at: Win10 1803 starts to roll out to Win10 users with “Semi-Annual Channel” and 180 day “feature update” deferral]

    6 users thanked author for this post.
    Viewing 7 reply threads
    Author
    Replies
    • #312878

      So between this post and your 1809 post, are you suggesting we update to 1809 to avoid 1803?  I am on 1709 with 360 days on the “feature update” deferral (on my alienware laptop).

      I ask because I initially upgraded it to 1803 earlier last year and found the brightness was stuck on full with no way to darken the screen.  So I restored back to 1709 waiting for a newer version that would work Ok with the brightness issue fixed.

      And I realize I am running out of time on my 1709 version…

      Cheers!!
      Willie McClure
      “We are trying to build a gentler, kinder society, and if we all pitch in just a little bit, we are going to get there.” Alex Trebek
      • #312936

        that’s right, EspressoWillie

        Microsoft will end support for Home & Pro editions of Windows 10 version 1709 on April 9, 2019. you have less than 3 months to decide from now whether to upgrade to either v1803 or v1809

        • #313126

          So the big question is 1803 that support ends 11/12/2019, or try 1809 that goes until 5/12/2020?  Woody’s comment that 1809 might be a good choice (since it had so many problems early on).

          Woody?

          Cheers!!
          Willie McClure
          “We are trying to build a gentler, kinder society, and if we all pitch in just a little bit, we are going to get there.” Alex Trebek
          • #313129

            See the article just below this one on the main blog page (and read the ComputerWorld article linked there).

          • #313191

            It’s still too early for me to give a blanket recommendation, particularly because Microsoft hasn’t yet declared that 1809 is ready for businesses. Hang tight.

            • #313193

              Is it still the case that Microsoft declares a specific Feature Release as “ready for business”?
              I was under the impression that when the new feature update is released, then it is ready for whatever purpose the user/administrator believes it is ready.

            • #313204

              Yes, they still do this.  what happened here is someone set the “semi annual” as the deferral and then set 180 days deferral.  It’s been 180 days since 1803 was declared semi-annual/CBB so the deferral period has passed.

              Susan Bradley Patch Lady/Prudent patcher

              1 user thanked author for this post.
      • #313203

        Personally I’m running 1803 with no issues.  1809 is just now rolling out so I’m not ready to be “stable” on that.

        Susan Bradley Patch Lady/Prudent patcher

        • #313247

          It is “stable enough”. But this largely depends on the purpose of the computer. 🙂

    • #312947

      I’m in the same boat with a lot of my users… and my current own primary work laptop. 1709 is the most common variant of W10 around here.

      The problem is, 1809 hasn’t looked all that good so far, but most of those were 1803->1809 … I wonder…

    • #312991

      Anecdotal data point:

      I updated two desktop hosts (one OEM Win 10 on 2016 Dell hardware and one upgraded to Win 10 on 2010 HP hardware) on 1/12/19 (not a “forced” update).  Both were running Win 10/1803 (Spring 2018) update.  The Dell host has an i7-7700 cpu with 4 cores and eight threads and plenty of installed memory, which was a very good performing host before Meltdown/Spectre mitigations.  I wasn’t born yesterday, so I made sure that I had plenty of time between starting and when I next really needed to use the host.  I also had fairly recent Windows 7 System Image Backups and very current Windows 7 File Backup files available, as well as Windows 10 Recovery Drives.

      I had no installation anomalies at all.  However, the download and install phase took between 90 and 180 minutes, of which nearly 60 minutes was download (and I have a fast connection so any delay there was due to Microsoft server congestion and/or metering).  Then, the process obediently paused to invite me to select a good restart time.  The restart and install completion took about another hour.

    • #313039

      Running 1803 on most of my clients workstations – been slowly allowing them to upgrade from 1703/1709 for the last two months or so.  So far no real issues here.

      Not ready to allow 1809 for several months, might skip it.  I’ve got test machines running it now, but it’s quirky.

      Interesting side note:  still have several older machines on build 1703 with CBB(usiness) release schedule plus 365 day feature deferral.  Sometime today they all started alerting that they needed updates. Clicking the check for updates button did not download or install anything – but the message persisted.  On one of these systems I changed the feature deferral to 180 days per Woody’s alert, and it immediately downloaded 1803 and began installing it.

      ~ Group "Weekend" ~

      • #313058

        Please elaborate on “quirky”?

        Because I sort of thought they all were, at least since 1703, for the first 6 months at least…

    • #313136

      I have 1803 on my Desktop and an HP ProBook laptop (Win 7 to W 10 in 2015 ) since Oct. 2018 and have had no problems. I will certainly wait for awhile before 1809 though unless MS cheats again.

      A note on this thread though, when I click on the original article on the AW Home page it say’s that I can’t post there. Was this a new opened thread?

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

      • #313145

        You should click on the “Comment in the AskWoody Lounge” link to make comments. Clicking on the blog post title messes things up.

        1 user thanked author for this post.
        • #313152

          That must be a change since I never had to do that before. But thanks for the heads up.

          Don't take yourself so seriously, no one else does 🙂
          All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

          • #314376

            Ah no, it is a fault that has remained since we had site problems back in Sept ’17, and we’re still waiting for a proper fix to that temporary, problematic fix!

            1 user thanked author for this post.
    • #313170

      I have 1709 set at 365 days feature update deferral so do I get more time before Microsoft bugs me about upgrading?  It’s been over 365 days since I set that in group policy.

      • #313174

        The 365 days don’t depend on when you on when you set it in Group Policy. It depends on when Microsoft declared it CBB/SAC (ready for business release). You are past the 365 days, so you need to be careful if you don’t want v1803 or v1809 yet. See this post

        1 user thanked author for this post.
    • #313243

      Hello,
      can you tell me please where can I choose these options shown in the screenshot? I cant find it, I use 1803, but some settings are done by my organisation (domain).

      Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

      HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

      PRUSA i3 MK3S+

      • #313330

        Those settings are in Seettings>Update & Security>Windows Update>Advanced Settings

        Whether or not you see those options depend on settings in Group Policy. There could be several places in GP that cause it – Windows Update settings, restrictions on your User ID, etc. There will be equivalent settings in the Registry.

    • #313529

      speaking of version 1803, MSDN & Visual Studio (VS) subscribers are even luckier as they get newly updated ISO images of 1803 that have the Jan. 2019 KB4480966 update (build 17134.523) slipstreamed onto them.

      examples of the updated v1803 ISOs with Jan. 2019 update from MSDN/VS:
      en_windows_10_consumer_editions_version_1803_updated_jan_2019_x64_dvd_93b1b9b7.iso
      en_windows_10_consumer_editions_version_1803_updated_jan_2019_x86_dvd_c8be264c.iso

      • #313565

        Oh bother.  I checked my MAPS subscription and it only lets me download 1809.

        Seems if you don’t catch it when it becomes available, it vanishes quickly.

        Looks like I can only download Windows Server 2019, Office Plus 2019 and SQL standard 2017 now from the partner site.

        Cheers!!
        Willie McClure
        “We are trying to build a gentler, kinder society, and if we all pitch in just a little bit, we are going to get there.” Alex Trebek
    Viewing 7 reply threads
    Reply To: Win10 1803 starts to roll out to Win10 users with “Semi-Annual Channel” and 180 day “feature update” deferral

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

    Your information: