Microsoft: There Is No Such Thing as Autumn Creators Update, It Was a Mistranslation
Microsoft has spent most of this week doing damage control. Two major news reports (depending on your obsession with the company) earlier this week confirmed that Microsoft is going to call its Windows 10 Fall Creators Update as Autumn Creators Update in some countries and that Atom's Clover Trail PCs are unable to install the current Creators Update.
As shared with our readers last night, Microsoft confirmed to Wccftech that it will extend security support for the affected Intel machines until 2023, however, they won't be tasting any new Windows 10 versions, ever. Not too bad, considering we were thinking these poor machines will stop getting any kind of support by early 2018.
Coming to the second disaster of giving one Windows 10 version two different names - what were you thinking, Microsoft?
Naming problems for Windows 10 Version 1709
Microsoft's thinking process hasn't always been clear, but it was stupid - to say it in the least brutal way - to give one version two names. Confusion, confusion, confusion.
The company has now confirmed that there won't be any Autumn Creators Update after all, as the upcoming version of its desktop OS will be called Windows 10 Fall Creators Update, regardless of what people call this season locally. Microsoft has claimed that the name appeared "in some countries" due to a mistranslation (ummm...) and the update will remain as the Windows 10 Fall Creators Update globally.
It isn't a good sort of damage control, however. Giving it a completely different name would be the easiest and simplest way to go, instead of following seasons. Even if we forget the fact that Fall is known as Autumn in some countries, when the Windows 10 Fall Creators Update is released in September this year, it won't even be Fall in some regions anymore.
Since Microsoft is on an ongoing spree of controlling damage, why not get rid of Fall Creators Update completely and give it a new name? Short on names? All the company needs to do is send one tweet and crowdsource it. Who really cares about a name as long as it doesn't make some regions (Southern, this time) feel unhappy about getting a Fall update in Spring. Or, as the folks at ArsTechnica have suggested, get rid of these names and just stick to the numerical version that Microsoft uses internally and in the update changelogs.