A WindowsForum.com user ignited a flurry of speculation this week by posting what they claimed could be the release schedule for an upcoming version of Windows. The post, by user mehrlicht, asked simply: "Anyone can confirm these dates? Release Candidate in April? Release To Manufacturor in July? OEM in October? Retail On Christmas Season?"
No official source, no leaked memo — just a question. Yet it’s the kind of question that spreads fast because it hits on the four milestones every Windows release is measured by. Before you start circling dates on your calendar, let’s walk through what each of those terms means, how realistic this timeline looks, and what you should do — and not do — while the unconfirmed schedule hangs in the air.
The rumored timeline, by the numbers
The supposed schedule breaks down like this: a release candidate (RC) in April, release to manufacturing (RTM) in July, OEM availability in October, and full retail launch around Christmas. No specific year was mentioned, and no Windows version number was attached to the claim. That lack of detail alone is a major red flag. Still, the structure matches a classic Windows development cadence, which gives it a veneer of plausibility.
Microsoft has not acknowledged this timeline. No insider, leaker, or analyst has publicly backed it. At press time, it remains a single, unverified forum post. But because the post surfaced during a period when Microsoft has been quiet about its next major Windows update, the dates quickly became a Rorschach test for what people want to believe about the platform’s future.
Decoding the acronyms: what RC, RTM, OEM, and retail mean for you
The alphabet soup of Windows milestones isn’t just insider jargon — each stage has a distinct impact depending on whether you’re a home user, an IT pro, a developer, or someone who buys a new PC. Here’s the breakdown.
Release Candidate (RC)
When Microsoft compiles a release candidate, the company is signaling that it believes the build is feature-complete and stable enough to ship to the public after one final round of testing. Historically, RCs have been made available to Windows Insider Program participants, giving enthusiasts a preview of what’s coming. If an RC arrives in April, Insiders on the Dev or Beta channels would be the first to install it.
A release candidate is not a final product. Bugs can — and often do — delay the next milestone. For example, Windows 7 went through a build 7100 RC in May 2009 and didn’t hit RTM until July. The gap between RC and RTM is typically 2–3 months.
Release to Manufacturing (RTM)
RTM is the build that Microsoft signs off on and delivers to PC manufacturers (like Dell, HP, Lenovo) so they can pre-install it on new machines. After RTM, the core development work is done. Only critical patches and last-minute fixes get added before the general public sees the code.
For IT departments, RTM is the trigger to begin final compatibility testing. For everyone else, it’s a behind-the-scenes milestone — you won’t download anything on RTM day. But if this rumored July RTM were real, it would suggest a final public release roughly 3–4 months later, which aligns with the proposed October OEM and Christmas retail targets.
OEM availability
OEM (original equipment manufacturer) availability means new PCs start shipping with the new Windows version pre-installed. For consumers, this is often the easiest way to get the latest OS. If OEMs begin rolling out devices in October, you’d see them on store shelves just before the holiday shopping season.
This stage also matters for anyone planning to buy a new laptop or desktop. If you’re eyeing a purchase in late summer, waiting a few weeks could mean getting the newer OS without needing to upgrade manually.
Retail launch
A Christmas-season retail launch would cover two things: the ability to buy a physical or digital license from Microsoft or retailers, and the broader availability of the OS as a free upgrade for existing Windows users (assuming Microsoft continues its current practice). Prior Windows versions have often launched in the fall — Windows 10 in July 2015, Windows 11 in October 2021 — so a holiday window isn’t unprecedented.
A retail launch also kicks off the 10-year support lifecycle for most editions. The clock starts ticking on security updates, so knowing the exact date matters for long-term planning.
How we got here: a brief history of Windows release cadences
Windows release schedules have never followed a rigid formula, but patterns emerge. Windows 7’s RC arrived in May 2009, RTM in July, OEM in October, and retail later that month. Windows 8’s schedule was similar, with an RC (called Release Preview) in May 2012, RTM in August, and general availability in late October. Windows 10 essentially abandoned the old milestone names by moving to a continuous servicing model, though major feature updates still follow a rough spring/fall rhythm. Windows 11 returned to a more traditional annual feature update cadence, with the original release in October 2021.
The rumored April RC → July RTM → October OEM → Christmas retail pipeline fits these historical patterns reasonably well. That might explain why the forum post felt credible enough to spark conversation. But without a named Windows version or any corroborating evidence, it’s impossible to separate an educated guess from an actual leak.
One critical difference today: Microsoft now relies heavily on the Windows Insider Program for testing. A “release candidate” in the modern sense might just be a Beta Channel build that Microsoft marks as the final version for hardware partners. The public might not see a formal “RC” label anymore.
What to do now: steps for believers, skeptics, and pragmatists
If you’re a home user: treat this timeline as entertainment, not a plan. Do not schedule a new PC purchase, a family IT project, or an upgrade window around unconfirmed dates. Instead, keep your current Windows installation updated and enroll in the Windows Insider Program if you want early, official previews.
If you’re an IT administrator: you already know better than to trust a single forum post. But if you’re mapping out deployment roadmaps, use the rumored milestones as a rough hypothetical. Begin cyclical testing now, watch for official Microsoft blogs or the Windows release health dashboard, and have a communication draft ready for your organization — but don’t circulate anything until Microsoft confirms.
If you’re a developer: pay attention to SDK and API changes that accompany release candidate builds. When Microsoft does drop an official RC or early release, the accompanying developer tools will matter more than the OS date itself. Test your apps against Insider builds now so you’re not scrambling later.
Across all audiences: the safest way to track Windows release milestones is through Microsoft’s official channels — the Windows Insider Blog, the Microsoft 365 roadmap for enterprise features, and the Windows release health hub. Third-party leaks are entertaining, but they’re not actionable.
Outlook
The forum thread doesn’t provide any source, and until a credible leaker or Microsoft itself echoes the dates, the whole thing remains a shot in the dark. Keep an eye on the Windows Insider Dev Channel. If a release candidate is truly coming in April, build numbers should start climbing in April, and Microsoft will likely publish a blog post outlining what’s final. The same goes for an RTM in July: you’ll see signs in the Beta Channel and in partner testing builds long before any official announcement.
For now, the most newsworthy element isn’t the dates themselves — it’s the community’s hunger for a clear Windows roadmap. “If you have concrete info, please share with a source,” mehrlicht later replied in the thread. That request still stands. And until someone answers it, the calendar stays blank.