Windows 7 came out on October 22, 2009, when Microsoft released it to general retail availability worldwide. That date is the answer most people want, but it sits at the end of a longer release process that began with a public beta in January 2009 and an RTM build in July 2009. The operating system reached end of support on January 14, 2020, after 10 years and roughly 3 months of servicing.

The staged release mechanism

A Windows launch is not a single event. It is a sequence of distinct milestones, each serving a different audience, and confusing them is the main reason people disagree about when Windows 7 "came out." The build had to be finished first, then manufactured, then distributed to channels that each had their own readiness requirements.

The engineering endpoint is RTM, or release to manufacturing. Microsoft signed off build 7600.16385 on July 22, 2009. At that moment the code was frozen and ISO images went to OEMs and disc pressing plants. Nothing about RTM is visible to a retail customer, which is why it rarely appears in casual answers.

General availability, or GA, is the date the product could be bought or downloaded by anyone. That was October 22, 2009. Microsoft staged launch events in New York that morning, and retail boxes and upgrade media appeared in stores the same day.

Between those poles sit the preview programs. A public beta shipped on January 9, 2009, and a release candidate, build 7100, arrived on May 5, 2009. These builds were free, time-limited, and explicitly not final, so they are footnotes rather than release dates.

The practical consequence is that a PC bought in late October 2009 might carry a build compiled in July. The customer experience and the engineering timeline are separated by roughly three months of manufacturing, imaging, and shipping. Plainly: the code was done in summer, but the product went on sale in fall.

Quantified context: build numbers and the version jump

Windows 7 reports itself as version 6.1 at the kernel level, not 7.0. Microsoft incremented the marketing name while keeping the kernel minor version close to Windows Vista's 6.0, a decision that preserved driver and application compatibility. This is why some diagnostic tools list Windows 7 machines as "NT 6.1."

The RTM build number, 7600, became a useful shorthand. Service Pack 1, released February 22, 2011, bumped the build to 7601. A machine still reporting 7600 in later years was either unpatched or running a slipstreamed image that had not taken the service pack.

Retail packaging came in several SKUs, from Starter through Ultimate. The mainstream consumer editions were Home Premium and Professional, with Ultimate above them and Enterprise sold only through volume licensing. Each SKU mapped to different memory ceilings and feature sets, which mattered because the 32-bit editions capped usable RAM at roughly 3.2 to 3.5 GB regardless of edition.

Milestone Date Build Audience
Public beta January 9, 2009 7000 Testers, enthusiasts
Release candidate May 5, 2009 7100 Testers, IT pilots
RTM July 22, 2009 7600.16385 OEMs, manufacturers
General availability October 22, 2009 7600 Retail, all customers
Service Pack 1 February 22, 2011 7601 All users via update
End of mainstream support January 13, 2015 7601 All users
End of extended support January 14, 2020 7601 All users

The gap between mainstream and extended support is worth noting. Mainstream support ended in January 2015, meaning no new features or non-security fixes after that point. Extended support continued security updates for another five years, which is why many organizations treated 2015 as a soft deadline and 2020 as the hard one.

The support clock and its two thresholds

Microsoft's lifecycle policy splits servicing into two phases, and each has its own end date. Mainstream support covers feature work, design changes, and warranty claims. Extended support covers security patches only. For Windows 7 the split fell on January 13, 2015, and the final cutoff was January 14, 2020.

The extended phase ran exactly 10 years from GA, a pattern Microsoft applied to several products of that era. After January 14, 2020, Microsoft stopped issuing security updates for the general public. That created a visible risk: any vulnerability discovered afterward would remain unpatched on any machine still running the OS.

There was one commercial escape hatch. Microsoft sold Extended Security Updates, or ESU, for Windows 7 through a per-device annual fee aimed at organizations. Pricing was tiered and rose each year, and the program was extended in stages, ultimately reaching a final cutoff in January 2023 for the last enrollment track. Consumers were not eligible.

Reconciling the thresholds is straightforward once you separate them: mainstream support ended January 13, 2015; free public security updates ended January 14, 2020; paid ESU coverage ran for a limited number of years after that for businesses only. A claim that "Windows 7 was supported until 2023" is technically true only for ESU customers, not for the public.

Timeline table: from code freeze to final patch

Date Event What changed for users
January 9, 2009 Public beta Free trial build, expires automatically
May 5, 2009 Release candidate Near-final build for pilots
July 22, 2009 RTM Code frozen; no public access
October 22, 2009 General availability Purchase and download open
February 22, 2011 Service Pack 1 Rollup of fixes; build 7601
October 31, 2013 Retail sales end Boxed copies discontinued
January 13, 2015 Mainstream support ends No new features
January 14, 2020 Extended support ends No free security updates

The retail sales cutoff in October 2013 is a separate date again. Microsoft stopped selling boxed licenses to consumers then, while OEMs could still ship machines with Windows 7 preinstalled for a period afterward. This is why someone could buy a new Windows 7 laptop in 2014 even though the software was no longer on store shelves.

Edge cases that shift the effective date

The date a given person "got" Windows 7 can differ from October 22, 2009, for several legitimate reasons. These are not trivia; they explain why support questions often get muddled answers.

Volume licensing and MSDN subscribers received access before retail. Organizations with Software Assurance could deploy the RTM build in the weeks between July and October, which means the enterprise "release" preceded the consumer one.

OEM preinstallation ran on its own schedule. Major manufacturers imaged machines throughout the fall of 2009, and some shipped units before the official launch under embargo agreements. A machine's build date in System Information can therefore predate the retail date.

Regional availability varied slightly. Most markets opened on or near October 22, 2009, but a few followed within days rather than the same hour. Time zones alone mean the launch happened on different calendar dates depending on where you stood.

Upgrade paths created a third wrinkle. Customers upgrading from Windows Vista could use upgrade media, while clean installs required full licenses. The upgrade experience, not the release date, is what many people actually remember.

A counterintuitive detail worth flagging: Windows 7 was never the internal codename Microsoft planned to ship. The product began life as "Blackcomb" and then "Vienna" before the company settled on the Windows 7 name in 2008. The version number 7 was a marketing reset after Vista's poor reception, not a strict count of prior releases — by kernel numbering it was 6.1.

Misconceptions and how to check them

Several persistent claims about the Windows 7 release date are wrong in specific, checkable ways.

"It launched in 2010." False. Retail availability began October 22, 2009; the 2010 date sometimes gets attached to Service Pack 1 planning or to the fiscal year Microsoft reported it in. "RTM and launch are the same day." False. RTM was July 22, 2009; GA was October 22, 2009, a three-month gap. "Support ended in 2015." Partly false. Mainstream support ended January 13, 2015, but security updates continued to January 14, 2020. "Windows 7 is version 7.0." False. The kernel reports 6.1; the retail name and the kernel version diverged deliberately. "You can still get free security updates." False for the public. Only paid ESU covered organizations, and that program has closed.

The professional caveat here is that build numbers and marketing names are separate systems, and support articles mix them constantly. When you read a claim about Windows 7, check which clock it is using: engineering, retail, or servicing. Most confusion dissolves once the clock is identified.

Practical actions: verifying a Windows 7 machine today

If you encounter a Windows 7 system and need to know its actual vintage, the operating system will tell you directly. These steps produce verifiable answers rather than recalled ones.

Press Windows key plus R, type winver, and press Enter. The dialog shows the full version and build number. A build of 7600 indicates RTM without Service Pack 1; 7601 indicates Service Pack 1 is installed.

Open System Information via msinfo32 to see the OS name, version, build, and install date. The install date is more useful than the build number for dating a specific machine's setup.

Check Windows Update history for the last successful update. A machine whose updates stop in early 2020 was running on the public support clock; one with later updates was likely on ESU or a third-party patch service.

Confirm the edition, because the support story and memory ceiling differ by SKU. Home Premium and Professional were the common consumer and small-business choices.

Treat any internet-connected Windows 7 machine as unpatched for vulnerabilities disclosed after January 14, 2020. That is the practical threshold: the software still runs, but it no longer receives free security fixes, so exposure grows over time.

For organizations, the concrete decision point was the ESU enrollment deadline, which has passed. Migration to a supported OS is now the only path to ongoing patches, and the effort scales with the number of machines and the age of their hardware.

Limitations: what the dates cannot tell you

Release and support dates describe Microsoft's commitments, not the state of any particular installation. A machine can run Windows 7 with later unofficial patches, with third-party security tools, or fully offline, and none of that changes the official timeline.

The ESU program's exact pricing and year-by-year structure varied by agreement type and customer size, and those figures are not reliably reconstructable today without the original contracts. What can be stated with confidence is the shape: paid, per-device, business-only, and time-limited.

Finally, secondhand accounts of "when Windows 7 came out" often reflect the day a person installed it, which could be months after GA on a new PC or an upgrade cycle. The authoritative date remains October 22, 2009 for general availability, with January 14, 2020 as the end of free public security servicing. Those two dates answer nearly every question the keyword implies.