Windows 10 Fall Creators Update coming October 17th 2017

DavidY said:

That's not the published info from Microsoft (unless you have one of those Clover Trail processors which can't get past 1607, in which case Microsoft said there will be security updates up to 2023 "for these specific devices"). It's not clear how this would work, or whether any other devices could get 1607 updates or whether it means an extension for CU support.

But for everyone else, it's "tentatively" March 2018 end date for AU and Sept 2018 for CU.
So AU and CU could both be out of support in less than a year's time. (And 1511 dies next week!)

From here: https://support.microsoft.com/en-us/...cle-fact-sheet

That is not what I read earlier but as we know MS has a habit of changing their minds. I will never use the FCU. as @magilla said , I am not going to turn off and on my machine when I leave for twenty minutes. Microsoft needs to get with the Climate change faction. Just about every other company is trying to save energy. I also do not leave my TV on when I leave...

DavidY said:

I saw earlier in this thread you mentioned a problem with Sleep - it might be a driver problem (or perhaps FCU is picking the wrong driver) rather than code in FCU itself.
I've noticed FCU is picking up a wrong driver on my old machine so I had to manually install the correct driver - nothing to do with Sleep in my case but it could be similar.
I'm no expert though - have you started another thread on it? Also use Feedback Hub of course.

I did and I use the same drivers that I did on 15063 and sleep works just fine. I am NOT the only one with this problem and as for the life cycle: The Feedback hub has Over 50 reports from me on this and they wanted my email. I have yet to hear from anyone at THe Hub.

https://www.computerworld.com/articl...s-support.html

DavidY said:

That's old information and contains a big loophole:


My reading of this phrase is, if the hardware supplier doesn't keep supplying Microsoft with new drivers every time they create a new Win10 OS version, it's no longer within the "supported lifetime of the device", so your machine could goes out of support well before 2025.

The Clover Trail thing is an example of this - Intel aren't supplying MS with new drivers which work with Creators Update (which has presumably changed something about how it interacts with the processor) and these processors won't work with CU or presumably any later versions.

MS have said they will support these Clover Trail devices until 2023 (which you will note is not the 2025 mentioned in that old computerworld article) as an exception. But I imagine they won't do this for every piece of hardware where the OS changes break the drivers.

Note the Windows 10 footnote against that 2025 date on the Lifecycle page which includes this:


So you could be out of luck of they don't fix it.

Well my PC does not seem to support the latest update so they have a flaw in their Life cycle or maybe not-could be intentional.

DavidY said:

That's old information and contains a big loophole:


My reading of this phrase is, if the hardware supplier doesn't keep supplying Microsoft with new drivers every time they create a new Win10 OS version, it's no longer within the "supported lifetime of the device", so your machine could goes out of support well before 2025.

The Clover Trail thing is an example of this - Intel aren't supplying MS with new drivers which work with Creators Update (which has presumably changed something about how it interacts with the processor) and these processors won't work with CU or presumably any later versions.

MS have said they will support these Clover Trail devices until 2023 (which you will note is not the 2025 mentioned in that old computerworld article) as an exception. But I imagine they won't do this for every piece of hardware where the OS changes break the drivers.

Note the Windows 10 footnote against that 2025 date on the Lifecycle page which includes this:


So you could be out of luck of they don't fix it.

Josey Wales said:

Well my PC does not seem to support the latest update so they have a flaw in their Life cycle or maybe not-could be intentional.

This is one of the reasons I keep a Linux(usually Ubuntu) virtual machine, to stay up to date on and changes, and to stay in practice.

Linux is good about keep kernel drivers and microcode upto date, even if someone has to create them themselves and open source them.

They even have Cyrix drivers

http://www.tldp.org/HOWTO/Hardware-H...pu.html#AEN414

2.1.Â*Supported Hardware

Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. This section merely outlines the basics. 2.1.2.1. CPU


Nearly all x86-based (IA-32) processors still in use in personal computers are supported. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon.
However, Ubuntu xenial will not run on 586 (Pentium) or earlier processors. Support for i586 and lower processors, as well as for i686 processors without the cmov instruction, was dropped in Ubuntu 10.10. Most i686 and later processors are still supported. The Intel Quark is not supported, due to hardware errata.

Cliff S said:

This is one of the reasons I keep a Linux(usually Ubuntu) virtual machine, to stay up to date on and changes, and to stay in practice.

Linux is good about keep kernel drivers and microcode upto date, even if someone has to create them themselves and open source them.

They even have Cyrix drivers

http://www.tldp.org/HOWTO/Hardware-H...pu.html#AEN414

2.1.Â*Supported Hardware

I am going to install either PClinuxOS or Mint , I have used both in the past or I may install both of them.:)