Clover Trail and Windows 10 revisited

Wanna hear the honest truth? That information came from Microsoft on assumption and there was nothing they could really do to really prevent from updating; whether that is installing feature updates or cumulative updates.

The issue with clovertrail processors was discovered late in development and the advisory to stick with Windows 10 1607 seem to have been more cautionary than mandatory.

Its not mandatory, so if you end up in an issue with 1703 or 1709 not working properly, you can't say they didn't tell you so.

I haven't seen anything from MS about those specific clovertrail devices going past 1607.

MS update is supposed to block updates to hardware / CPU's that do not "qualify" for new versions. I would have expected they had done that for those orphaned CPU's. Maybe they "forgot"?

You could submit a Feedback to MS. They probably won't reply directly, but they may fix the problem.

.
............******************************
***************** Feedback *****************
.............******************************
.
Send Bug Reports and Feature Requests (and even Rants <G>) to MS Developers and Managers using the Feedback Hub:
.
LAUNCHjavascript:; FEEDBACK HUB VIA <WIN><F> Shortcut
.
“Official” MS does not pay much attention to this forum. However, you now can send your complaints, bug reports and feature requests directly to MS developers and managers using the “Feedback” process described in this link:
.
https://answers.microsoft.com/en-us/windows/for...
.
Please post a share link to your feedback, back here, so other people who find your question will be able to vote for it and add their comments to it.
.
How do I give feedback on Microsoft Office?:
.
https://support.office.com/en-us/article/how-do...
.
This is MS "official" documentation with links to appropriate UserVoice and "Answers" forums.
.
********
.
Feedback is a quality control SUPPLEMENT to MS "telemetry" (aka spyware) which MS use to reduce impact of update problems.
.
<snip https://www.zdnet.com/article/windows-10-how-mi... >
.
But Microsoft insists its combination of telemetry data and artificial intelligence (AI) actually made this update both "safe and fast", allowing it to identify problems early and block updates to hardware it will cause problems for.
...
Our AI approach has enabled us to quickly spot issues during deployment of a feature update
,,,
We immediately blocked all PCs that could be impacted by this issue from being updated, and communicated to customers within 24 hours, including an initial work around.
....
</snip>
.
.............********************************............
**************** End Feedback ****************
.............********************************............
.

Re my first point, the "these specific devices running the Windows 10 Anniversary Update" line relative to 2023 does make it sound like only machines on 1607 will go to 2023. I guess we'll find out after April 2019, when 1709 goes EOL. Those running 1703 will find out sooner: October of this year.

Re my second point, isn't it routine for MS to block feature updates from appearing in WU on certain systems?  I'm pretty sure that I've heard this before, especially in the weeks following a release, when problems start to crop up. They'll let it go on models with proven success, and hide it from ones that have been problematic. Eventually, a few CUs later, they'll let it go even on the problematic models, assuming the issues have been corrected.

It seems to me they could permanently put Clover Trail on the same blacklist used in the above scenario for 1803 and beyond (the builds that are hardcoded not to actually install anyway). It's easy enough for a user to block these updates twice a year, but that's far from optimal, and plenty don't know how.

I haven't seen anything from MS about those specific clovertrail devices going past 1607.

MS update is supposed to block updates to hardware / CPU's that do not "qualify" for new versions. I would have expected they had done that for those orphaned CPU's. Maybe they "forgot"?

You could submit a Feedback to MS. They probably won't reply directly, but they may fix the problem.
.

Yes, I'll do that once learning more.

It is possible that Clovertrail systems still on 1607 will never see later feature updates. Maybe it's the case, like it was here, that you'll only see the update if on 1703 or 1709. In which case, that may or may not be intentional on MS's part. If it is intentional, it doesn't quite make sense anymore given that 1803 will not install.

Since you've raised the question, I am interested if MS will extend support for those clovertrail devices if they have gone beyond 1607.

Actually, you may want to try asking Susan Bradley your question. She is a columnist who does have contacts inside of MS. Or she can publicly ask the embarassing question, like she did here:

2018 07 30- AN OPEN LETTER TO MICROSOFT MANAGEMENT RE: WINDOWS UPDATING
https://www.computerworld.com/article/3293440/m...

Here is original source, and a place you can ask your question:

https://www.askwoody.com/2018/an-open-letter-to...

PS: if you ever do get a good answer, please post back here, I'm curious too.