• It’s official: The next version of Win10 will be version 1809

    Home » Forums » Newsletter and Homepage topics » It’s official: The next version of Win10 will be version 1809

    Author
    Topic
    #211456

    Yep, they’re continuing the numbering system. The latest beta build, 17741, lists Redstone 5 as version 1809. The only real question at this point is
    [See the full post at: It’s official: The next version of Win10 will be version 1809]

    3 users thanked author for this post.
    Viewing 9 reply threads
    Author
    Replies
    • #211495

      or WECU – We’re Endless Cumulative Updates

    • #211499

      This will actually be a reference version, very much like 1607 because it will have an LTSC release and also a full server with desktop experience release, Windows Server 2019.
      For those who are interested in upgrading less often, this is the one to get and stay with it for about 2 years, until the next LTSC release.

      3 users thanked author for this post.
      • #211517

        The real question is always about how to get LTSC. I would dearly love to get it for my home PC, but Microsoft would freak out otherwise at the prospect of no longer being able to spy on me.

      • #211627

        Also, Office 2019 will only run on Win 10 SAC and Win 10 Ent LTSC 2018 (Version 1809). Office 2019 will only be supported for 7 years, unlike Office 2016 or earlier which is supported for 10 years.
        https://www.theregister.co.uk/2018/02/02/no_windows_10_no_office_2019_says_microsoft/
        https://www.itassetmanagement.net/2018/02/02/microsoft-announce-changes-to-windows-10-office-365-and-office-2019/

        Another scheme by MS to milk more profit from her Enterprise cash cows and to push Win 7/8.1 users onto Win 10.

      • #211634

        For those who are interested in upgrading less often, this is the one to get and stay with it for about 2 years, until the next LTSC release.

        … and only get security updates and bug fixes for the first 18 months, but nothing for the last 6 months?

        • #211694

          Good point. It makes me think how much nicer it would be if Microsoft just allowed me to use the reference version and would add support until the next, with the ability to only get security updates by delaying feature updates until the next reference version. Once every two years to have to switch and no new features in the meantime, OS reinstall and messing with settings would be much better.

          Of course, it would mean having to hop on the new version as soon as the cake is baked instead of waiting a year like I can do right now, which is not the best idea IMHO. So, three years of security updates only instead of two please, so we can wait a year to switch to the one year old reference version. Now, that is better.

          While I am thinking about it, this looks way better, but it would even be better if instead of two years between reference versions, there would be three so I could switch only every three years. Great. But the really really best way would be to not have to switch until my PC dies and I buy a new one. They could maybe let me skip one or two or three reference versions while providing security updates. That would be a revolutionary idea.

          • #211696

            AlexEiffel: I am all for doing a little reductio ad absurdum and following your line of thinking all the way to  “and they did not upgrade the OS happily ever after.” Nothing would please me more, or perhaps please less Mr. Nadella and the likes of him.

            Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

            MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
            Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
            macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

      • #211736

        M$ releases new Versions of Win 10 SAC every 6 months, eg 1607, 1703, 1709, 1803 and 1809, and new Versions of Win 10 Ent LTSC every 2 years, eg LTSC 2016 and LTSC 2018.

        Ent LTSC is supported for 10 years while SAC is normally supported for 18 months.

        Companies can use Win 10 Ent LTSC 2016 for 10 years but if they also want to use Office 2019, they will need to pay M$ for the upgrade to Ent LTSC 2018.
        Similarly, the future Office 2022 will only run on Ent LTSC 2020 or later.

    • #211510

      on an unrelated note, this recent ZDNet article was posted-
      https://www.zdnet.com/article/windows-10-updates-expect-slimmed-down-full-quality-versions-says-microsoft/

      and this on GHacks.net-
      https://www.ghacks.net/2018/08/17/windows-10-and-server-2016-update-changes/

      not sure if that will happen with 1809

      1 user thanked author for this post.
    • #211524

      UGHHHH~! ENOUGH WITH THE CREATOR UPDATES! I am so sick and tired of them! Just let 1809 be the VERY last update!

    • #211551

      I’ve lost track of the numerous extant versions of Windows 10.  Does anyone remember Microsoft’s comment that Windows 10 will be the last version of Windows?  I wonder which version of Windows 10 they were referring to.

      This comedy of errors makes me long for the return of monolithic service packs. In retrospect it seems to me that service packs and the related updating methodology were light years ahead of today regarding quality and reliability.

      2 users thanked author for this post.
    • #211557

      “Or maybe WACU” ROFL

      Did you not mean ‘WACKO”?

      (‘cos that’s how Win 10 iterations appear to me. 🙂 )

      1 user thanked author for this post.
      • #211573

        I like yours better. I first read it as Whack You. Like being whacked over the head with another new version.

    • #211595

      Here I am *just* getting used to version 1803.

      Remember when new version releases were exciting and we looked forward to seeing the new tech?

      To be honest this is feeling more like dread than excitement. What won’t work that now works? What third party software will HAVE to be updated just to get what we already have working again?

      I’m imagining that if I put v1803 on my hardware and work through the issues I could then choose to sit out the next several in-place upgrades, effectively lengthening the cycle time, but there are influences outside Microsoft (e.g big, important 3rd party applications) that may demand the latest Windows version. Choosing to “take it slower” isn’t as easy as it sounds at first blush.

      I understand Microsoft’s need to move their software into the future, but if the OS is never stable how is anyone expected to develop software for it?

      This 6 month cycle time is ridiculous.

      -Noel

      10 users thanked author for this post.
      • #211598

        I would say, looking here in from the outside, that being so “upgraded” and so often, must be as pleasant and interesting as dropping bricks on a big toe, particularly when they are dropped by someone else and you have no say on when, or from how high, or how often.

        Changing OS (or “upgrading” it) tends to be a huge time-waster with an often long, in places also steep, and not very exciting learning curve and the possibility that some of your important applications no longer will run. I am comparatively blessed with Windows 7 and do not expect to ever allow myself to become cursed with the repeated imposition of someone else’s idea of what is the proper thing to run on my computer. My only preoccupation, at this time, is what will be the best way to exit MS’ Highway to the Nether Regions of the oximoronically named “Cloud”, all the way to its WaaS deepest Circle. Shall I go with the macOS on a Mac, or Linux and, if Linux, conveniently preinstalled in a Meerkat device or what?

        Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

        MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
        Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
        macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

        2 users thanked author for this post.
        • #211602

          Changing OS (or “upgrading” it)

          You make a good point… “Upgrading” isn’t really a viable approach. Windows has NEVER worked well when “in-place upgraded”. Folks in the know used to always install a new version as a clean install, then put in all their chosen tools and whatnot.

          The only way the 6 month cycle model works is when an “in-place upgrade” can be accomplished in a day or so and have the OS work perfectly after.

          The only way the OS has ever worked perfectly after an install is when a full, clean install is done, which takes a week to a month to get back into prime operating condition.

          Ergo… You just can’t get there from here.

          It’s like the Microsoft people forgot that the OS isn’t the end-all, but just a foundation on which a computing experience is built.

          -Noel

          9 users thanked author for this post.
          • #211605

            Agreed, Noel – we have an OS to run software, not to use the OS by itself!

            I was always advised that an OS upgrade was inadvisable as an in-place install, and always found the clean install route too time-consuming, therefore I waited until new hardware was necessary, before upgrading. Now, I’m just praying the current hardware holds together long enough that I can avoid the current lunacy of frequent forced (in-place) upgrades.

            4 users thanked author for this post.
            • #211617

              I still have not managed to get my Win 10 VM (host is my Core 2 Duo laptop, using Virtualbox on Linux Mint 19) to upgrade to 1803.  I’m intentionally restricting myself to the kinds of things a “regular” user would be able to do to get it upgraded, and thus far nothing has worked to get it off of 1507 (the original version).  Each upgrade attempt has ended in failure, and there have been a lot of them.

              I think that if MS would push another upgrade between 1507 and 1803, and from there go to 1803, it may well work, but since MS doesn’t make those older versions available, I’m not using them (I know they can be downloaded from third-party sites that are supposedly reputable and safe [and it’s in a VM anyway, so what better place to test things that might be risky?], but that’s not something a regular user would be likely to try).

              I haven’t been trying continuously.  I try for a bit, then when it fails, set it aside to see if MS releases a new intermediate fix (there was one a few weeks ago, but it didn’t help).  It’s been a while, so I think I will give it another shot now.

              On the VM end, I’ve tried everything people suggest as far as changing Virtualbox settings to get it to work, but so far no luck with any of it.

              I bet that if the updates still came one by one instead of massive in-place upgrades, my VM would be fully up-to-date now.

              Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
              XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
              Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

              1 user thanked author for this post.
            • #211649

              I’ve had two occasions now where the Win 10 setup I’ve been maintaining since the original pre-release has had to be fully re-installed from an ISO file.

              I don’t believe both were made necessary by my tweaks to the OS to bring it in line with my needs and desires. One maybe, but not both.

              And bear in mind that I have been keeping VM snapshots, and tried reverting to older snapshots before attempting to apply updates. The latest updates simply would not install on ANY older version at several times, hence the need to in-place upgrade from the latest CBB (or whatever it’s now called) ISO file.

              I guess I’m just not supposed to take Windows this seriously. I’m not supposed to have 13 different versions of Adobe Photoshop installed to test with (I develop Photoshop add-on software for a living). I’m not supposed to expect Windows to work and keep working for months on end, keeping my data safe.

              Trouble is, without these expectations my business model – in which I spend a majority of my time developing software to put bread on the table – doesn’t work.

              -Noel

            • #211803

              @Ascaris:

              There is the Windows ISO Download tool which can download nearly any Win10 ISO from MS, including older Win10 versions even the 1507 RTM release.

              1 user thanked author for this post.
    • #211652

      Can`t  wait for the next OS  comparisons.  W7  notches up.

    • #211959

      I just threw-up in my mouth a little…..

      Red Ruffnsore

    • #212056

      a recent ZDNet article describing about the upcoming 1809 release has been published yesterday:
      https://www.zdnet.com/article/windows-10s-next-big-feature-release-officially-named-build-1809/

      the BIG question is when will Microsoft actually release the 1809 version of Windows 10 to the masses? The recent ZDNet article suggests that the 1809 release may come sometime this October.

    Viewing 9 reply threads
    Reply To: It’s official: The next version of Win10 will be version 1809

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

    Your information: