On July 13, 2009, Microsoft will sign off on the final release to manufacturing (RTM) build of Windows 7, effectively wrapping up development of its next-generation operating system. The date, along with a detailed schedule of the final stages, comes from a leaked roadmap published by Russian leaker WZOR, a source with a track record of accurate internal Microsoft timelines. According to the roadmap, the final build will be selected on July 10, with the official signing ceremony taking place three days later.
This isn't just an internal milestone. RTM means Windows 7 is done. The code that gets signed on July 13 will be the same code that ships on new PCs starting October 22. For users, businesses, and developers, it's a signal to start preparing.
Inside the Final Roadmap: From Escrow to Sign-Off
The leaked roadmap, first reported by Hedrush, outlines four distinct phases in June and July that take Windows 7 from near-final status to the official gold master.
| Phase | Dates | What Happens |
|---|---|---|
| RTM Escrow building | June 1 – June 19 | Multiple candidate builds are compiled and placed into an "escrow" holding phase. WZOR notes that this step was already complete as of the leak. |
| RTM Recall | June 22 – July 10 | Engineers test the escrow candidates, hunt for showstopper bugs, and select the one that will become the final RTM build. |
| Final Build Target | July 10 | The chosen build is officially compiled as the "gold code." This is the day the ultimate RTM build is built. |
| RTM Sign-Off | July 13 | The final build is signed by Microsoft's management, officially releasing it to manufacturing. After this, it heads to OEMs and partners. |
This process is standard for Microsoft operating systems. The RTM escrow is a safety net: instead of testing just one final build, the team creates a small set of near-final builds and then picks the best one. The two-week recall period from June 22 to July 10 is a buffer to catch any last-minute issues. If a critical bug appears, the team can fall back to another escrow candidate or create a fix without derailing the entire schedule.
The July 10 target for building the gold code is particularly notable. It gives the team a weekend before the Monday sign-off to double-check everything. Once the build is signed, any further fixes would have to ship as post-RTM updates.
What RTM Means for You
The impact of RTM depends on who you are. Let's break it down.
For Home Users and Enthusiasts
If you're running Windows Vista or XP, July 13 doesn't change your daily life—yet. But it marks the point where you can start reading hands-on reviews based on the final code. Tech outlets will likely get access to the RTM build soon after sign-off, and their impressions will tell you exactly what you'll be getting on October 22.
A word of caution: unofficial copies of the RTM build will almost certainly leak onto file-sharing sites within hours of sign-off. Avoid them. Early leaked builds often contain malware, and running an unactivated copy of Windows can be more trouble than it's worth. Microsoft typically provides official evaluation copies through TechNet and MSDN, and a public trial may follow. Patience pays off.
If you've been testing the Release Candidate (build 7100), your time is limited. The RC will expire in March 2010, with bi-hourly shutdowns starting in June 2010. You'll need to migrate to the RTM build before then, either by purchasing a license or reinstalling another operating system.
For IT Professionals and System Administrators
July 13 is your starting gun. The RTM build is what you'll eventually deploy, so now is the time to begin serious validation. Download the RTM build from your Microsoft volume licensing portal or MSDN/TechNet subscription as soon as it's available—typically within a week of sign-off.
Key actions to take:
- Deploy the RTM build in a test lab immediately. Check compatibility with your line-of-business applications.
- Verify that your Group Policy settings, VPN clients, and security software work correctly.
- If you haven't already, start planning your deployment strategy. Windows 7 can be installed as an in-place upgrade from Vista SP1 or later, but a clean install is often recommended.
- Assess hardware readiness. Windows 7's system requirements are modest—1 GHz processor, 1 GB RAM (32-bit) or 2 GB (64-bit)—but older machines may still need upgrades.
- Begin crafting user training materials. While Windows 7's interface is familiar to Vista users, XP users will face a steeper learning curve.
Volume license customers with Software Assurance should note that Windows 7 RTM typically becomes available to them before general availability. Historically, that window opens in late July or August. If you qualify, you could start packaging and testing enterprise images much sooner than October.
For Developers and ISVs
RTM means the application programming interfaces (APIs) are locked. If your software works on the Release Candidate, it should work on the final build, but don't assume. Download the RTM build as soon as you can and run your full test suites. Pay special attention to driver compatibility, especially for hardware that interacts directly with the kernel.
The Windows 7 logo certification program will open soon after RTM. If you plan to certify your application, now is the time to review the requirements and begin testing.
How We Got Here: The Long Road to Windows 7
Windows 7 didn't appear out of thin air. Its roots go back to the troubled launch of Windows Vista in 2007. After widespread criticism of Vista's hardware requirements, driver issues, and User Account Control prompts, Microsoft knew it needed a redemption story.
The development of Windows 7 began in earnest with Milestone 1 (M1) builds in early 2008. These early builds were almost indistinguishable from Vista, but they laid the groundwork for performance and compatibility improvements. By the time Microsoft showed off Windows 7 publicly at the Professional Developers Conference (PDC) in October 2008, the operating system had already evolved significantly. Build 6801, demonstrably stable and fast, won over many skeptics.
The public beta, Build 7000, arrived in January 2009 and was notable for the first appearance of features like the improved taskbar (Superbar), Jump Lists, and Aero Peek. The beta was met with overwhelmingly positive reviews, and many users installed it as their daily driver—a testament to its stability even at that early stage.
Then came the Release Candidate, Build 7100, in May 2009. It refined the beta's rough edges and served as the last public preview. Microsoft used feedback from millions of RC users to squash bugs and polish the experience.
Now, just two months after the RC, we're at the doorstep of RTM. The speed of this final phase underscores how solid Windows 7 already was. The relatively short RTM recall window suggests that few—if any—critical bugs remained.
What You Should Do Before July 13
For most users, there's no immediate action required. But a little preparation now can smooth your transition to Windows 7 later.
If you plan to buy a new PC: Wait for models that come with Windows 7 preloaded. They'll start appearing in late October. Buying a Vista machine now and upgrading later works, but you'll avoid the hassle by waiting.
If you plan to upgrade an existing PC: Run the Windows 7 Upgrade Advisor (available as a free download from Microsoft's site when it's updated for RTM) to check for hardware and software compatibility. Clean out old files and back up important data now so you're ready for a fresh install.
If you're an IT admin: Start your testing plan. Download the RC if you haven't already to familiarize yourself with the OS, but remember that the RTM build will be the one you deploy. Begin auditing your installed applications and hardware inventory. Identify which machines can run Windows 7 and which need replacement.
If you're a developer: Get your development environment ready. Make sure you have the final Windows SDK and tools. Test your code against the RC now to catch issues early.
After the Sign-Off: What Comes Next
Once the ink dries on July 13, Windows 7 enters the distribution phase. Microsoft will begin shipping the code to original equipment manufacturers (OEMs) like Dell, HP, and Lenovo. They'll use the RTM build to create factory images for new PCs. Over the following weeks, those images will be tested and loaded onto assembly lines.
Volume license customers with active Software Assurance agreements will get access to Windows 7 RTM through the Volume Licensing Service Center, likely in late July or early August. This allows large organizations to start building and testing corporate images months before the general public gets the OS.
The broader availability for IT professionals and developers through TechNet and MSDN usually follows within a week of sign-off. Students and hobbyists may get access through programs like DreamSpark (now Microsoft Imagine) around the same time.
For everyone else, the date to circle on your calendar remains October 22, 2009. That's when Windows 7 goes on sale at retail and starts showing up on new PCs in stores. Microsoft has already confirmed that date, and the RTM roadmap aligns perfectly with that timeline.
Between RTM and general availability, expect a steady drip of news: performance benchmarks, compatibility reports, and reviews. Microsoft may also release a "post-RTM" update, often called an "RTM GDR" (General Distribution Release), to address any minor issues discovered during the OEM process.
The WZOR roadmap doesn't say anything about Service Pack 1, but if history is any guide, we'll see one within a year of release. For now, though, the focus is on getting Windows 7 out the door. The final push is underway.