Creators Update Development Nears Its End

Creators Update Development Nears Its End

With the release last night of Windows 10 Insiders Preview build 15042, the development of the Creators Update nears completion.

We’ve been discussing the schedule of this third major update to Windows 10 since before Microsoft even announced it formally, in October 2016. But more recently we’ve seen a more specific schedule emerge. And this week’s steps toward completion seem to confirm what we had previously discovered.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

The specifics: As I first noted yesterday on Twitter, this latest Insider Preview build is the first to not include a desktop watermark indicating the build number and other related information. As notable, this build does not expire, as did previous Insider builds.

In an odd touch, this build also reverted to the 1607 versioning that Microsoft used for the Anniversary Update. Previous Insider builds displayed version 1703, which will ultimately be the version number for the Creators Update. That change I cannot explain, but as a Microsoft representative told me Friday, testing continues. And the other changes are of course exactly the types of things that Microsoft has done previously with big Windows 10 releases in the past.

(Note too that “nears completion” is not the same as “is complete.” There will almost certainly be one or more Insider builds before Microsoft actually finishes this release.)

Speaking of which, this winding down of Creators Update development—including the absence of major new features in recent builds followed by the slowing down of build releases—likewise matches previous Windows 10 updates.

As you may recall, the original word on the Creators Update schedule—which was codenamed Redstone 2—dates back to late Summer 2016. At that time, we discovered that Microsoft planned to ship this update in the “Spring 2017.” That’s a rough time frame which one could argue spans the literal Spring, or from late March through late June. But we likewise found out that it would ship earlier in that period, not later. I had my eyes on the actual beginning of Spring, or about March 20.

Eventually, however, things got a bit more precise. And our sources have told us that the Windows 10 Creators Update would in fact ship publicly in early April after being finalized in March. Looking at the calendar, it appears that Microsoft will be able to deliver the update, upgrading Windows 10 to build 1703, on that schedule.

This is a big update, no doubt about it: Just look at all the changes I’ve documented in Windows 10 Creators Update Preview if that’s not clear. But I’m most taken by how many new features have been added so late in the schedule. This seems to refute the very openness of Windows 10 development, and for all the testing, bug bashes, and feedback, I’m curious whether some big new features have even been tested well enough. (Yes, I’m looking at you, Dynamic Lock.) And other purported new features that were mentioned early on, like Groove Music Maker, are still nowhere to be found. Credit Microsoft for at least keeping it interesting.

Looking ahead, I’ll continue to document new Windows 10 features here on and to slipstream that new stuff into the Windows 10 Field Guide as well. It’s going to be a busy Spring. But then it’s going to be a busy year, too: The next major Windows 10 update, currently codenamed Redstone 3 and awaiting Microsoft’s next silly product name, is expected to appear by November.


Share post

Please check our Community Guidelines before commenting

Conversation 14 comments

  • jimchamplin

    Premium Member
    25 February, 2017 - 9:38 am

    <p>It installed overnight for me. Looking forward to digging in and playing today!</p>

  • note-book

    25 February, 2017 - 9:58 am

    <p>About version numbers, could it be that new previews are set to version 1607 so that they will be tracked as pre-final when the release 1703 version comes out? If this preview is not expiring there is probably a need to distinguish it from the final one. It makes sense for MS to track how many PCs are on any given release version or higher, and whoever keeps this version&nbsp;installed will be counted as not on release 1703.</p>

    • PeteB

      25 February, 2017 - 4:01 pm

      <blockquote><em><a href="#78990">In reply to note-book:</a></em></blockquote><p>Who cares</p>

    • evox81

      Premium Member
      28 February, 2017 - 3:13 pm

      <blockquote><a href="#78990"><em>In reply to note-book:</em></a></blockquote><p>There are version differentiators beyond the year/month number… Like the build number for example. They wouldn't need to change the year/month number to track what you're saying. In fact, because so many devices would already have 1607, it would be a meaningless number. </p>

  • Demileto

    25 February, 2017 - 10:26 am

    <p>The screen of death's color has also been blue again since 15031. :)</p>

  • ChesterChihuahua

    25 February, 2017 - 11:59 am

    <p>The next update will be called "Making Windows Great Again"</p>

    • hrlngrv

      Premium Member
      25 February, 2017 - 5:13 pm

      <p><a href="#79386"><em>In reply to ChesterChihuahua:</em></a></p><p>Windows for huge hands.</p>

    • Tony Barrett

      26 February, 2017 - 5:20 am

      <blockquote><em><a href="#79386">In reply to ChesterChihuahua:</a></em></blockquote><p>Maybe it needs to be called 'A Windows version actually for the benefit of the end user and not Microsoft'. Nah, I just can't see that one happening.</p>

  • CompUser

    25 February, 2017 - 1:45 pm

    <p>If only I could get the sound to work on the Insider builds, I'd probably make this build&nbsp;the default boot partition on my dual boot desktop.&nbsp;I just can't figure it out.&nbsp;Everything is identical with drivers, settings, etc., but the audio services just won't run when the computer is booted to the Insider partition, even though it works fine on the public release. And it's been this way&nbsp;at least&nbsp;since the first Creators Update Insider release.</p>

    • jongross

      Premium Member
      26 February, 2017 - 6:52 am

      <blockquote><a href="#79586"><em>In reply to CompUser:</em></a></blockquote><p>please post to feedback hub if you haven't already.</p>

  • SvenJ

    25 February, 2017 - 1:59 pm

    <p>Yea, Dynamic Lock does need some help. Played with it yesterday when both my Surface and L950 got the update and I was able to actually get to the appropriate settings without jumping through hoops. On/Off is not going to cut it in the Sign in options screen. I have a dozen BT items that may or may not be connected at any point in time, including the pen, mice, etc. I deleted all phones and paired only one, the 950. Didn't seem to react to my 'walking away' (turning off BT on the phone), but there is no indication anywhere what Dynamic Lock is looking for. No, registry editing is not the answer. Needs a line below The Dynamic Lock switch that tells you what it is tied to, and the option to change the device right there.</p><p>Update: OK, does seem to work, but took almost 45 seconds after turning of BT on the phone to lock. Some of the feedback comments note that it won't turn off if you, or someone else, hops on and uses the keyboard or mouse. </p>

  • navarac

    25 February, 2017 - 6:39 pm

    <p>Dynamic Lock not yet fit. This and the last build have cocked-up the bluetooth connection between PC and phone, so I cannot even test it.</p>

  • navarac

    26 February, 2017 - 9:44 am

    <p>All 150xx builds have shown Version 1607 in winver on my machines.</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2024 Thurrott LLC