1611 UPGRADE

Did we have 1611 upgrade? Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

Z wrote:

Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

1608 happened.

Andy Burns wrote:

1608 happened.

oops 1607

On 3/12/2016 1:15 AM, Z wrote:
Did we have 1611 upgrade? Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

Just when I was about to return to Windows 8?

"Z" wrote in message news
Did we have 1611 upgrade? Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

Windows 10 Releases, version and build
1507 (10240) RTM aka Initial Release, July 2015
1511 (10586), Nov. 2015
1607 (14393), July 2016 (available Aug 2nd 2016)


--
....winston
msft mvp

On Fri, 2 Dec 2016 13:43:51 -0700, "...winston"
wrote:

"Z" wrote in message news
Did we have 1611 upgrade? Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

Windows 10 Releases, version and build
1507 (10240) RTM aka Initial Release, July 2015
1511 (10586), Nov. 2015
1607 (14393), July 2016 (available Aug 2nd 2016)



I've long wondered where those release version numbers came from, but
looking at your post, it looks like they are year and month. And I
right?

On 02/12/2016 17:15, Z wrote:
Did we have 1611 upgrade? Last year we had 1511 & 1604 but I have not
seen anything about 1611. What happened?

You get upgrades when you get them. There is no point in getting
sleepless nights about them. They will come, if not this year then
next year.



--

If you want to filter all of my posts then please read this article:
https://support.mozilla.org/en-US/kb/organize-your-messages-using-filters
In step 7 select "Delete"

With over 400 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

"Ken Blake" wrote in message ...

On Fri, 2 Dec 2016 13:43:51 -0700, "...winston"
wrote:
Windows 10 Releases, version and build
1507 (10240) RTM aka Initial Release, July 2015
1511 (10586), Nov. 2015
1607 (14393), July 2016 (available Aug 2nd 2016)

I've long wondered where those release version numbers came from,
but looking at your post, it looks like they are year and month. Am I
right?

Yes. They are build and month. As you can see, availability may or may not be same month. Also, in the case of Windows Update
deployment on Win10 with major version being staged over time, availability in Windows Update can easily lag the 'published'
general availability date.

Initially, MSFT did not refer to the RTM as 1507
winver will report RTM as 10.0 (10240.x) where 10.0 is the version, 10240.x the build

Once 1511 arrived winver reported the version as 1511 and the build as 10586.x

Quite a few MSFT reference articles do not refer to RTM as 1507 thus not uniform across some current and previously released
articles and MSFT blogs.
e.g.
He
https://technet.microsoft.com/en-us/...mt679505.aspx?
But Not He
https://support.microsoft.com/en-us/...update-history

Of note for 1507, the final 60 day countdown for support starts in January 2017. Once the countdown expires 1507 will no longer be
capable of receiving updates.
- Only the two latest released versions(1511 and 1607) will continue to qualify for updates thus the last updates for 1507 will
occur in March 2017.
- i.e. ***Supporting current and prior version = 'Windows as a Service'***
Which coincidentally takes us back to 'the real meaning of the Win10 free upgrade term 'supported for the life of the device' -
it's not the useful life of the device, it's the support cycle for Win10 on the device!!! Win10 will still work on the device, but
in the case of 1507 no updates will be available. And in time, 1511 will have a countdown start date at some point in time after
the next Win10 major version(The Creators Update) is released next spring.
https://www.microsoft.com/en-us/wind...oming-features

--
....winston
msft mvp

On 03/12/2016 10:28, ...winston wrote:
Yes. They are build and month.

YEAR and month.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

Brian Gregory wrote:
On 03/12/2016 10:28, ...winston wrote:
Yes. They are build and month.

YEAR and month.


Thanks. Good catch. I'm confident Ken caught that too and understood
the intent.

--
....winston
msft mvp windows experience

On Sat, 3 Dec 2016 20:12:52 -0700, ...winston?
wrote:

Brian Gregory wrote:
On 03/12/2016 10:28, ...winston wrote:
Yes. They are build and month.

YEAR and month.


Thanks. Good catch. I'm confident Ken caught that too and understood
the intent.


Yes, I did, thanks. But I knew what you meant and didn't bother to
correct it.

It's funny that if you look carefully at the version number and think
about it for a moment, it's obvious what it is, but I never did so
before.

"Ken Blake" wrote in message ...

Yes, I did, thanks. But I knew what you meant and didn't
bother to correct it.

It's funny that if you look carefully at the version number and
think about it for a moment, it's obvious what it is, but I never
did so before.



Not too many people did. When Win10 was released it was rarely, if ever, referred to as 1507, not until 1511 was released and
MSFT started updating articles about Windows-as-a-service for Windows Updating options on the Enterprise side - Current Branch for
Business(CBB), Long Term Service Branch(LTSB) -- everyone just called it 10.0, RTM, or 10240.
We may as well get used to it Year/Month should be around for quite some time, plus it’s a whole lot easier calling the versions a
4 digit number than the marketing gobble names Anniversary Update or Creators Update