How to get the latest version of Win10 Fall Creators Update, version 1709, build 16299.19

Topic

New Reply

The terminology is daunting, but appears to be a step in the right direction. I’m facing problem that many of you have asked about. I have two real, n
[See the full post at: How to get the latest version of Win10 Fall Creators Update, version 1709, build 16299.19]

Reply | Quote

Replies

I joined the Windows Insider program in the first week of its existence. Three years in, I just could not care less what they call the categories, what each one is for, or what versions of Windows 10 my being in one group or the other will serve up to me. It has become absurdly complicated, and I just don’t care enough any more to sort it all out in my mind.

My perspective probably has been affected by the fact that my next work PC (which is currently on its way to the office) will sport Linux. For me, there will come a point when not only Windows 10, but Windows generally and indeed all of Microsoft become irrelevant. I’ve had enough of their shenanigans and incompetence.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

3 users thanked author for this post.

HiFlyer, Elly, Noel Carboni

Reply | Quote

Woody, I understand but don’t necessarily agree with your terminology:

You wrote:

In the new order, beta testers (“Windows Insiders”) have…

In my mind the “Windows Insiders” are more akin to “alpha testers”, receiving new builds hot off the Engineers’ desks daily or weekly. “Beta testers” are those testing the “RTM” or “released” code, i.e., with a chosen build number where only the point revisions increase, before it becomes stable enough for whatever today’s rendition of CBB is (which would be a reasonable definition of “release”).

Regarding whatever you call it testing…

To be honest, like Cybertooth above I – a lifelong Windows aficionado and geek – have grown so tired of trying to keep up with unfinished systems and terminology redefinition that I just can’t bring myself to care what Microsoft is doing any more.

Can someone please tell me, in executive summary terms (and knowing that things may change again) how to identify the time when Windows v1709 “Fall Creators Update” reaches the state formerly known as CBB – i.e., when it’s “done and good enough to use”?

My plan currently is to watch Woody’s and others’ posts here and try to derive when it is time to create a system for my own product testing.

I no longer care to even try alpha or beta Windows versions for my own business use… I wasted so much time with v1703 – more than any prior version – only just now achieving a working test system configuration, that I have no interest in testing v1709 before it’s “done and good enough to use”. It will almost certainly not be worthy of the “Pro” moniker until nearly 6 months after “RTM” or whatever THAT is now called.

-Noel

3 users thanked author for this post.

HiFlyer, Elly, Cybertooth

Reply | Quote

Check at https://technet.microsoft.com/en-us/windows/release-info.aspx for when a build of the Windows version you’re interested in contains “Semi-Annual Channel ” in the “Servicing option” column.

Reply | Quote

Noel Carboni wrote:

Can someone please tell me, in executive summary terms (and knowing that things may change again) how to identify the time when Windows v1709 “Fall Creators Update” reaches the state formerly known as CBB

Nobody knows. The last time it happened – when 1703 switched from Current Branch to Semi-Annual Channel and Microsoft simultaneously got rid of the “Current Branch for Business” terminology, the only real change, aside from a glancing mention in a blog post is the “Microsoft recommends” tag on the right side of the Win10 Release Information page.

Details here.

Reply | Quote

That’s what I was afraid of.

Usually late in the game (e.g., build number xxxxx.5xx) a whole bunch of bugfixes get integrated into the system. Maybe we’ll be able to tell when that happens.

Not yet having adopted Win 10 for my everyday business use, I still wonder about one very practical concern…

If I were to bring my daily driver system up to, say, for example v1703 now that it’s up to 15063.674: How long could I reasonably run that and refuse to update to their subsequent big 6 month “releases”, presuming that future versions fail to meet my needs.

Put another way, not unlike past versions of Windows: Could a person reasonably adopt a particular Windows 10 “version” release when it’s mature (remember service pack 1?), get it all cleanly set up and working smoothly, and use it. Then in 3 years or so, get back on the bandwagon and get the next one. This presumes one could continue to get whatever patches are available and avoid the big version releases, and of course that one finds no real value in whatever they’re doing lately…

• When will security updates cease for an older Win 10 release?
  
• When will it be necessary to shut off all online Windows Update Service updates and just use the catalog?
  
• If one were to fully go “off grid”, will the system just “expire” at some future date and become unusable?

When “perpetual beta testing as a service” is unacceptable, these things have to be considered.

-Noel

Reply | Quote

We’re not talking LTSB (LTSC, whatever) here. We’re talking Pro (non-Enterprise).

I believe the life cycle is 18 months from the git-go. So you sit out 4-5 months till things become stable. 18 months is EOL. Well, you can do the math…..

1 user thanked author for this post.

woody

Reply | Quote

I keep trying to find where I’ve gone wrong with that math. I just can’t believe an OS version really has to go past its ripeness that quickly.

A year of usable life is simply too short, not to mention too much of a gamble that Microsoft will still support a big hardware investment a few versions out (I buy big engineering development systems that will be amazing to use for 5 years; not everyone can use a little, portable computer – some jobs are bigger).

-Noel

Reply | Quote

Exactly- by the time things have settled down and are stable, you’re fighting off another OS upgrade. Like I’ve said in other posts, I’d rather deal with a limited amount of issues up front and have smooth sailing to look forward to (migrating to Linux), than constantly deal with the pain and aggravation of staying stable and in somewhat acceptable happiness (bothering with Win10).

It’s just not worth it anymore. It’s time for me to go back to dual booting Ubuntu MATE and 7, and when the well has dried up in 2020, I won’t use Windows for anything other than the Steam games that haven’t been ported yet to Ubuntu.

1 user thanked author for this post.

Cybertooth

Reply | Quote

18 months from release to EOL is correct. See Understanding The Windows 10 Servicing Timeline.

Reply | Quote

Noel Carboni wrote:

When “perpetual beta testing as a service” is unacceptable, these things have to be considered.

People thought “Windows as a service” meant that the customers would be the ones receiving the service from Microsoft.  They never imagined that they would be the ones providing the service to Microsoft.

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)

3 users thanked author for this post.

HiFlyer, Noel Carboni, Elly

Reply | Quote

Speaking of Alpha testers (not as in alpha male/female)…..
I updated my 1709 16299.15 Insider Preview this morning (Active development of Windows / Fast. since Skip ahead to the next Windows release was still “not available.”

First thing I did was go to the Store to update the UWP CrApps and, surprise!!!

Reply | Quote

My Store is OK on 16299.19 and 17017.

You should report this one to the Feedback hub.

Reply | Quote

The store was OK in my 16299.15 as well.
Maybe whatever is broken will be fixed in Tuesday’s dump.
I sent them a screenshot, but wasn’t interested enough to look around and see if anyone else was experiencing the same thing.

Reply | Quote

Does this look familiar?

https://twitter.com/teroalhonen/status/918467119234404352

Reply | Quote