Windows 10 was released to the general public on July 29, 2015. Microsoft opened the free upgrade to Windows 7 and Windows 8.1 users that day, and retail copies went on sale the same date. The July 29 date applies to the initial 1507 build; later versions arrived through the Windows-as-a-Service cadence.
The release mechanism: why July 29 was a phased rollout, not a single switch
Microsoft did not flip one global switch on July 29, 2015. The company pre-staged the upgrade payload on eligible Windows 7 and Windows 8.1 machines months earlier through the Get Windows 10 app. That app used a reservation system that queued devices for download in waves. The reason was bandwidth. Microsoft's delivery network had to push multi-gigabyte images to hundreds of millions of devices, so the company admitted machines in batches rather than all at once.
The technical pipeline worked in stages. Microsoft validated hardware against a compatibility database, then delivered the image through Windows Update or the Media Creation Tool. Devices with known driver conflicts got blocked from the automatic path and had to upgrade manually. This gating explains a common source of confusion: two people could both "have Windows 10 on launch day" while one waited days for the bits to arrive. The release date is a policy date, not a per-device delivery timestamp. In plain terms, Microsoft shipped the operating system once but delivered it many times over weeks.
Quantified context: the numbers behind the launch
Microsoft published adoption figures that show how unusual the launch was. Windows 10 reached 75 million devices within roughly four weeks of July 29, 2015, and 110 million within about ten weeks. Microsoft reported 200 million active devices by early January 2016, then 270 million by March 2016. The free upgrade offer ran for exactly one year, ending July 29, 2016, at which point the full license price was USD 119 for Windows 10 Home and USD 199 for Windows 10 Pro.
The launch build itself was version 1507, build 10240. Microsoft treated 10240 as the "final" RTM build for the 1507 release, which is a lower build number than many Insider previews that preceded it. That inversion confused testers who assumed higher build numbers meant newer code. The number reflects a release branch decision, not a chronological rank.
| Version | Marketing name | Release date | Build | Support end (as scheduled) |
|---|---|---|---|---|
| 1507 | Initial release | July 29, 2015 | 10240 | Ended |
| 1511 | November Update | November 2015 | 10586 | Ended |
| 1607 | Anniversary Update | August 2, 2016 | 14393 | Ended |
| 1709 | Fall Creators Update | October 17, 2017 | 16299 | Ended |
| 21H2 | November 2021 Update | November 16, 2021 | 19044 | Ended |
| 22H2 | 2022 Update | October 18, 2022 | 19045 | Final version |
Edge cases: builds, channels, and the versions people mistakenly call "launch"
Several edge cases break the simple "July 29, 2015" answer. Windows Insiders received preview builds starting October 1, 2014, so a small population ran Windows 10 code more than nine months before launch. Enterprises on Long-Term Servicing Channel builds got a different update clock than consumers. And the November 2015 update, version 1511, sometimes gets described as the "real" stable release because early 1507 devices had driver and privacy complaints.
The most consequential edge case is the support lifecycle. Microsoft ended mainstream support for Windows 10 on October 14, 2025, and stopped standard security updates for consumer devices on that date. Extended Security Updates were offered as a paid bridge, with consumer enrollment options and a limited free path tied to Microsoft account backup settings during the transition window. Treat any specific price or enrollment deadline as changeable and verify it against Microsoft's current documentation before relying on it.
Misconceptions: what the launch date does not tell you
The first misconception is that Windows 10 launched as a finished, frozen product. It did not. Microsoft moved to Windows-as-a-Service, meaning the OS received two feature updates per year in the early years, then a slower cadence later. The 1507 build that shipped on July 29, 2015, was superseded within months. Calling 2015 the "release year" is correct; calling it a fixed product version is not.
The second misconception is that the free upgrade ended for everyone on the same day. It ended for the general public on July 29, 2016, but Microsoft ran accessibility-oriented upgrade paths and later promotional exceptions that kept some upgrade routes open. Those exceptions changed over time and should not be assumed to exist now.
The third misconception is that version numbers track quality. Build 10240 shipped as the launch build, while later Insider builds carried higher numbers before public release. A counterintuitive professional caveat: the "newest" build number in a preview channel can be older in release-branch terms than the build Microsoft ships to consumers.
Practical actions: pinning down which Windows 10 you actually have
If you need to know whether a machine runs the launch-era release or a later version, check the build number directly. Run the winver command or open Settings, then System, then About. The version string (for example, 22H2) and the OS build (for example, 19045) identify the release precisely. Anyone diagnosing an old device should compare the build against Microsoft's release health dashboard rather than the marketing name.
Run winver to capture both version and build in one dialog. Check Settings, System, About for the OS build and installation date. Confirm support status against Microsoft's lifecycle page before planning upgrades. Verify any Extended Security Updates terms against current Microsoft documentation, not cached articles. Record the build number before reinstalling or imaging a device.
Limitations: what the date cannot settle
The launch date settles when Microsoft made Windows 10 generally available. It does not settle when a given device received it, how stable that device's drivers were, or whether a specific upgrade path remains open today. Adoption totals and support timelines are moving targets that Microsoft revises; treat any figure here as a historical marker rather than a current guarantee. For decisions about upgrading, licensing, or extended support on a specific machine, confirm details with Microsoft's official lifecycle documentation or a qualified IT professional.