Did Microsoft reveal Windows 10 21H1's release date accidentally?
Microsoft is working on the next feature update for its Windows 10 operating system. The company will release two feature updates in 2021 for the operating system, but plans to reverse the order in which these get released. In the previous two years, Microsoft released the main update of the year in the first half and a lighter follow-up update in the second half.
Starting in 2021, Microsoft will reverse the order and release a lighter update in the first half and the major update in the second half. The company has not revealed when the first update of 2021 will become available.
If you check the release month of the first feature update for Windows 10 of the past two years, you will notice that both were released in the month of May.
Windows 10 version 1903 was released on May 21, 2019, and Windows 10 version 2004 was released on May 28, 2020. Before that, the first updates of the year were released in the month of April.
Considering that there is a shift in the release order in 2021, some commenters assumed that Windows 10 version 21H1 could be released earlier than usual because of its minor status.
Our colleagues over at Windows Latest discovered a Chromium commit in which a Microsoft employee may have revealed the actual month of release.
According to that post, Windows 10 21H1 may be released in June 2021. The post appears to have been edited as the current version does not contain the release month anymore.
Windows Latest captured a screenshot of the message. The wording of the original message was the following according to that screen capture:
The Windows Release coming out this June 2021 has a new API that can disable KTM exploits.
The edited message does not mention a release month anymore:
An upcoming Windows Release has a new API that can disable KTM exploits.
A June 2021 release date is not out of the question, considering that it could very well mean an early June 2021 release date.
Now You: Do you keep track of Windows 10 updates?
@Anonymous
That’s funny. Do you do children’s parties?
Still haven’t finished the GUI after 20 years.
There are still icons from Windows NT
that will soon be irrelevant if everyone ends up with a revived and revised metro UI with the very latest Windows. Touch interfaces on Desktop, ouch.
MC hammer is coming back!
I’m always 2 releases behind, currently I have build 1909 18363.x and will be running this build until the wheels fall off.
Why you may ask?
As any experienced programmer will tell you, when any software is constantly being refactored and messed with you end up with code that’s is buggy.
Because it isn’t tested by experienced people and insider bug reports policies are dumb beyond all reasonable (an insider bug report no matter critical or not is ignored until enough people upvote the same bug report.
This rarely if ever happens, because users will make newer bug reports of poor quality (because it doesn’t contain any info that can be acted by support) and these are again ignored because they arent upvoted, so for a critical issue you have 1001 reports.
So then result is, newer Widows versions that are forced upon users will break crucial components often resulting in unusable machines.
Code maturity matters for stability and reliability.
The new release and upgrade policies will not improve this because now, unstable code will come all at once in one fell swoop.
Until Microsoft realizes that their bug report policies are equally as faulty as their code, nothing will improve, and you will see more broken crucial components.
So I have to wonder, since Windows is not Microsofts main revenue (Azure is) if they intend to however inadvertently to alienate everyone off their precious OS.
> “So then result is, newer Widows versions that are forced upon users will break crucial components often resulting in So then result is, newer Widows versions that are forced upon users will break crucial components often resulting in unusable machines. machines.”
Except that is not true. If it was, then most Windows 10 PCs that gets updates would be unusable, and that clearly is not the case.
But I’m glad you are behind with updates, as it makes it easier for us to hack your system.
@Black Whole Son
pwned was talking about “Widows”, not Windows.
often resulting in unusable machines. machines
its not the same most machines get unusable
Do you keep track of Windows 10 updates?
I only care if there are big issues with an update, otherwise I usually pause my updates a week or two after one is available.
As for this news, it seems like a silly waste of time to me.
Was this report written with some SEO in mind for “21H1”?
The commit message has been edited in patchset 3, but you can still see patchset 2:
https://crrev.com/c/2660562/2..3//COMMIT_MSG
Hard to imagine living in constant fear of a forced update destroying your install and potentially causing data loss. Good luck Windows 10 users.
Hard to imagine that you actually think that all you say is true. Good luck with your fear mongering agenda.
I see, replies deleted…
My message said something else entirely ;)
https://pasteboard.co/JMbBgQ2.png
Who cares?
Imagine your life’s time revolves around commenting on things you allegedly “don’t care” about.
Imagine making silly comments about other peoples’ comments where you assume all sorts of dopey things but you got it all wrong, as if you’re witty, but not at all.
not me
Windows scares, so I care.