/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Microsoft says it will now roll out twice yearly updates for Windows and Office in March and September, starting with “Redstone 3”

Mary Jo Foley / ZDNet :

ZDNet Mary Jo Foley

Context & Ripple Effects

Microsoft's Redstone updates had been slipping against their own targets — the company pushed Redstone 2 back to Spring 2017 to line up with a new device wave, after first sketching the branch as a 2016 Windows 10 update. Committing publicly to March and September slots starting with Redstone 3 converts that ad-hoc scheduling into a published servicing calendar.

The move matters because it makes update timing a contract with enterprise IT rather than an announcement-by-blog-post, and it prefigures how Microsoft later standardized the same twice-yearly rhythm across its business applications before recalibrating again in 2022.

First-order effects

  • Enterprise IT teams get fixed March and September windows for planning validation and deployment of Windows and Office feature updates, replacing the slip-prone Redstone schedule that pushed Redstone 2 out by months.
  • Microsoft's own device and partner planning now anchors to two known ship dates a year, formalizing the device-wave alignment it pursued ad hoc with Redstone 2.

Second-order effects

  • The cadence template spreads across Microsoft's portfolio: the company soon applied the same two-updates-a-year model to Dynamics 365, giving IT pros a sandbox environment to validate each release before rollout.
  • Third-party software vendors and management toolmakers building around Windows gain a predictable test-and-certify cycle, shifting compatibility work from reactive patching to scheduled release windows.

Third-order effects

  • A published cadence turns Windows from episodic big-bang releases into a continuously serviced platform — but the dial keeps moving: by 2022 Microsoft reportedly moved major Windows versions to a three-year cycle while shipping new features to the current version up to four times a year, decoupling feature delivery from version numbering.
  • If the servicing model holds, competitive pressure shifts toward update reliability and manageability tooling, making an OS vendor's cadence discipline itself a selling point to enterprise buyers.

The trend: Microsoft is converting Windows and Office from milestone-driven releases into a serviced platform on a published, tunable update cadence that it extends across its product lines and revises as deployment realities demand.