Microsoft’s Windows 10 Anniversary Update had barely reached users when the company quietly telegraphed its most consequential shift yet: two more feature updates were slated for 2017. In an August 2016 TechNet post aimed at IT professionals, Microsoft program manager Nathan Mercer stated, “This will be our last feature update for 2016, with two additional feature updates expected in 2017.” That single line, reported first by The Verge, confirmed months of insider chatter and set the stage for a relentless twice-yearly release cadence that would reshape enterprise planning, consumer expectations, and the very identity of Windows.

The codenames soon surfaced: Redstone 2 (RS2) and Redstone 3 (RS3). Together they formed the backbone of what Microsoft called Windows as a Service—a model where the OS would evolve continuously through major feature deliveries, tested publicly via the Windows Insider Program and deployed in measured, telemetry-guided waves. This wasn’t a rumor; it was a published roadmap, and it landed with all the subtlety of a GPO push.

What Microsoft said (and what those words meant)

Microsoft’s TechNet guidance was operational, not aspirational. By telling enterprise migration planners that 2016 would end with the Anniversary Update (version 1607) and that two more feature updates would arrive in 2017, the company gave IT teams a clear timeline to budget, test, and deploy. The post explicitly referenced feedback from organizations moving to Windows 10—a signal that the twice-yearly rhythm was influenced by real-world migration patterns.

Reporting at the time linked the roadmap to the Redstone codenames. Redstone 1 had just shipped as version 1607. Redstone 2 would follow in the first half of 2017, and Redstone 3 would land in the second half. Microsoft committed to testing these updates through its Insider rings (Fast, Slow, and Release Preview) before a phased public rollout. The strategy leaned heavily on telemetry to gauge adoption health and throttle distribution, reducing the risk of widespread breakdowns.

From codenames to cut-downs: The feature updates that actually arrived

Redstone 2—Creators Update (version 1703)

Released on April 11, 2017, the Creators Update pivoted Windows toward content creation, gaming, and mixed reality. Key additions included:

  • Paint 3D and integrated 3D model support across stock apps.
  • Windows Mixed Reality platform enablement for upcoming headsets.
  • Game Mode, Beam broadcasting, and a dedicated Game bar.
  • Edge and Cortana refinements, alongside security hardening.
  • OneDrive Files On-Demand (re-introduced later via a quality update).

Version 1703 wasn’t just a feature pack—it was a statement. Microsoft wanted Windows to be the canvas for creators and the hub for emerging immersive technologies. The update also exposed a fresh set of APIs that hardware partners and ISVs could target, reinforcing the platform play.

Redstone 3—Fall Creators Update (version 1709)

Launched broadly in October 2017, RS3 deepened the creative theme and introduced a new design language. Highlights:

  • Fluent Design System (then still called Project Neon) painted shells and inbox apps with light, depth, and motion.
  • Story Remix in Photos brought AI-powered media composition.
  • Cross-device continuity via Microsoft Graph started appearing, albeit in a staggered fashion.
  • Narrator gained image descriptions, and security controls tightened further.

Not everything demoed at Build shipped in one wave. Timeline, a marquee cross-device feature teased alongside RS3, arrived later via incremental updates. That pattern—announcing grand visions and then metering features across releases—became a hallmark of the era, frustrating power users who expected immediacy but delighting IT pros who preferred gradual change.

Why two updates per year mattered: The new operational reality

The twice-yearly cadence wasn’t just a scheduling quirk; it fundamentally altered the relationship between Microsoft and its ecosystem.

For consumers, it meant a steady drip of innovation. New gaming features, VR support, and creative tools appeared without waiting for a new OS box. For OEMs, it created predictable waves to anchor hardware refreshes—Surface devices, mixed-reality headsets, and gaming rigs all synced with feature drops.

For enterprise IT, the shift was tectonic. Gone were the days of monolithic migration projects every few years. In their place arrived continuous delivery: feature updates that, while free for Windows 10 license holders, demanded constant validation. Teams had to build pilot rings, automate application compatibility testing, master update deferral policies, and integrate tools like WSUS, SCCM, or Intune into a rhythm that respected change advisory boards. The benefit? Faster access to platform improvements. The cost? A permanent state of update-readiness.

Benefits and unintended consequences

The model delivered real wins. A predictable schedule let organizations plan maintenance windows. The Insider Program turned millions of enthusiasts into an early-warning system, catching driver conflicts and regressions before mass deployment. And platform plumbing for mixed reality and improved game streaming gave Windows a competitive edge in adjacent markets.

But risks multiplied. Twice-yearly feature updates increased the surface area for breaking changes. Despite staged rollouts, forums of the era were littered with reports of post-update driver failures, app incompatibilities, and rollback nightmares. Enterprise shops with strict regulatory controls struggled to align testing cadences; some simply deferred updates as long as allowed, undermining the whole point of continuous improvement.

Perception also diverged from reality. Microsoft’s keynote demos suggested instant feature parity, but staggered releases meant that promised capabilities like Timeline trickled out over months. That gap fed a narrative of overpromising and underdelivering—a perception that would haunt later releases.

The “free update” promise and its limits

Throughout this period, Microsoft maintained that feature updates came at no extra cost for Windows 10 users. The operating system had already adopted a Windows as a Service licensing model: you paid once (or via subscription for enterprise) and received ongoing upgrades. Industry commentary treated that as a continuation of existing policy, and indeed, no additional license fees were charged for RS2 or RS3.

However, free didn’t mean frictionless. Enterprises still needed to budget for deployment labor, tooling, and potential hardware refreshes to meet new feature requirements. More importantly, the 2016 promise of “Windows 10 forever” proved to be a snapshot of that moment’s strategy, not an eternal contract. In 2021, Microsoft reversed course and launched Windows 11, demonstrating that product naming and lifecycle commitments can change. The lesson: treat public roadmaps as directional, not irrevocable.

A retrospective critique: Did the twice-yearly model work?

From a product velocity standpoint, the cadence succeeded. It kept Windows competitive during a period when mobile and cloud platforms were accelerating. Creators got Paint 3D; gamers got Game Mode; developers got UWP enhancements. The ecosystem adjusted.

But the model also exposed deep fractures in IT preparedness. Organizations with mature DevOps-style practices—automated testing, ringed deployments, zero-touch provisioning—thrived. Those clinging to manual, gold-image-based processes found each feature update a mini-migration, complete with regression testing and user disruption. In effect, Microsoft shifted the burden of compatibility assurance onto its customers, armed with telemetry and Insider feedback as safety nets.

For Microsoft, the trade-off was defensible: faster innovation cycles outweighed the pain of some enterprise inertia. For many IT shops, however, the mandatory march toward continuous delivery forced either modernization or a costly extension of older Windows 10 versions through paid support programs. The very updates meant to keep everyone current often pushed laggards further behind.

Practical takeaways for IT pros (then and now)

The Redstone era left behind a playbook that remains relevant in the age of Windows 11 annual updates:

  • Build deployment rings: Insider Preview → pilot group → broad deployment, with defined success metrics.
  • Automate compatibility testing: Leverage tools like Microsoft’s own Test Base or third-party suites to smoke-test line-of-business apps against incoming builds.
  • Maintain rollback readiness: A known-good image, automated system restore, or cloud-provisioned backup can save hours of downtime.
  • Monitor release health dashboards and known-issue lists as part of a pre-deployment checklist.
  • Align driver and firmware updates with feature releases, especially for specialized hardware like mixed-reality headsets.
  • Use co-management (SCCM + Intune) to enforce update deferral policies that respect business cycles.

These steps are not optional; they are the minimum viable upgrade posture for any organization clinging to the twice-yearly discipline.

Legacy and echo: From Redstone to Windows 11

The 2017 roadmap accurately predicted the next two feature updates: Creators Update in April, Fall Creators Update in October. It also codified a rhythm that persisted, with minor variations, until Microsoft shifted Windows 10 to an annual update cycle in 2021 and released Windows 11. The Insider Program, phased rollouts, and telemetry-driven throttling all matured during this period and remain pillars of today’s update strategy.

But the most enduring legacy may be the mindset Microsoft embedded in the ecosystem: Windows is never finished. It’s a stream of updates, each a potential disruption. The onus is on users—especially organizations—to stay current without breaking production. The Redstone era proved that such a model can deliver rapid innovation, but only for those who invest in the tooling and processes to absorb it.

For Windows enthusiasts and IT architects looking back, the two-updates-2017 moment was more than a schedule confirmation. It was the point when Windows as a Service stopped being a slogan and turned into a daily operational reality. Whether that reality was liberating or burdensome depended entirely on which side of the deployment pipeline you stood.