Microsoft Already Created Its First Cumulative Update for Windows 10 Version 1703

Microsoft Already Created Its First Cumulative Update for Windows 10 Version 1703

Well, that didn’t take long: Though it won’t ship the Creators Update until April 11, Microsoft has already created the first cumulative update for that release.

Yes, I know. Time travel.

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.

To be fair, this has happened with every Windows 10 version, including the original. And we should be accepting of such things in the “Windows as a service” world. But I suspect that many of you view this with the same curious mix of humor and resentment that I do. The days of “we won’t ship it until it’s ready” are well past us, folks.

Here’s the Feedback Hub post:

In any event, Microsoft earlier today shipped KB4016250 for the final shipping version of Windows 10 version 1703, the Creators Update. As you can see above, it increments the build number to 15063.11 and fixes two bugs:

  • An issue where on Surface devices, Bluetooth radio fails to re-enumerate during hibernate/resume.
  • An issue with McAfee Enterprise to prevent a system crash when the product driver is installed on build 15060 configured with Device Guard.

Because Windows 10 version 1703 isn’t yet public (officially), this update headed out to Windows Insiders in both the Fast and Slow rings. And then Microsoft pulled it, quietly. Not sure why.

But I suspect we will see it appear again every soon. Stay tuned.

 

Share post

Please check our Community Guidelines before commenting

Conversation 30 comments

  • dmartin

    30 March, 2017 - 3:26 pm

    <p>Time doesn't stop between "RTM" and April 11. I'd be surprised, if there wasn't another cumulative update — unless Microsoft can figure out a way to prevent people from finding problems. :-)</p>

  • dstrauss

    30 March, 2017 - 3:30 pm

    <p>I understand it is a moving target and we can't expect perfection, but my god, they can't even get the initial release right for their own devices (Bluetooth fix) – that is extraordinarily stupid in my book.</p>

    • lvthunder

      Premium Member
      30 March, 2017 - 6:05 pm

      <blockquote><a href="#94351"><em>In reply to dstrauss:</em></a></blockquote><p>The inital release hasn't happened yet. That will happen on the 11th. </p>

  • bdollerup

    Premium Member
    30 March, 2017 - 3:38 pm

    <p>Methinks Paul forgets that Microsoft didn't call RTM on any particular build. They simply announced that Creators Update will start rolling out on April 11.</p><p><br></p><p>This is the benefit of Windows as a Service. ? Personally, I prefer they fix the issues they uncover instead of being beholden what we think an RTM is (even though they've stopped using the RTM moniker). </p>

  • straker135

    Premium Member
    30 March, 2017 - 3:45 pm

    <p>Paul minor edit in the second sentence, "Those it" should be "Though it". Cheers</p>

  • ChristopherCollins

    Premium Member
    30 March, 2017 - 3:52 pm

    <p>I don't understand why they don't just put this stuff in the build before it rolls out. In fact, ever since High Speed Internet came along, I have wondered why they don't issue a build with all patches in it every couple of months for the sake of new installs. I know it could have saved me a lot of time in my SBE with new machines/rebuilds on certain systems frequently.</p><p><br></p><p>Maybe one of you with more programming or inside knowledge could let me know if there is a reason that isn't done or if it is just laziness.</p>

    • will

      Premium Member
      31 March, 2017 - 11:40 am

      <blockquote><a href="#94359"><em>In reply to ChristopherCollins:</em></a></blockquote><p>I agree. There will ALWAYS be bugs and items to fix.</p>

  • wizarrc

    30 March, 2017 - 4:50 pm

    <p>I'm having more than just Bluetooth issues during hibernate/resume after upgrading to 15063.0 on my SB. I've had issues with the audio driver crashing repeatedly, the Movies &amp; TV app doesn't exit out of full screen mode, msn.com videos take forever to load, Netflix app now hides the mouse making it difficult to use in app controls, and videos on YouTube often stutter. Rolling back to Anniversary Update fixed all issues. Sounds like Microsoft still has a lot of learning to do with delivering these Hardware drivers on their own devices. They should hire some HP engineers to write some good stable drivers for them that can survive better between OS builds. I say HP because I also use HP laptops, and so far, they've gone several OS releases without a single issue.</p>

    • Mike Chace

      31 March, 2017 - 1:55 pm

      <blockquote><a href="#94366"><em>In reply to wizarrc:</em></a><em> If you haven't done so already, update the drivers/firmware/UEFI with the newest versions from Microsoft. I had similar issues and others (Hello was perpetually broken after Build 15048). Once I updated the firmware. The Surface Pro 4 was happy again, to the point where all of the issues that I previously experienced were gone. Or maybe I was just lucky!!!</em></blockquote><p><br></p>

  • Waethorn

    30 March, 2017 - 7:30 pm

    <p>So explain to me why these updates aren't just rolled into the build.</p>

    • johnbaxter

      30 March, 2017 - 8:10 pm

      <blockquote><a href="#94399"><em>In reply to Waethorn:</em></a></blockquote><ol><li>The build has gone to the OEM partners for whatever-they-do and installation.</li><li>The cumulative update process needs testing. (The pulling of the update suggests the process might need "adjustment".)</li></ol>

      • Waethorn

        30 March, 2017 - 9:20 pm

        <blockquote><em><a href="#94400">In reply to johnbaxter:</a></em></blockquote><p>I'm talking specifically about the build as it is on Windows Update.</p>

        • evox81

          Premium Member
          31 March, 2017 - 9:37 am

          <blockquote><a href="#94411"><em>In reply to Waethorn:</em></a></blockquote><p>I'm assuming that proper installation of the build is one thing that is extensively tested. The assumption that&nbsp;installations will function properly is based on the build remaining in a steady state.&nbsp;Rolling this update in to the build essentially created a new build, potentially invalidating that testing.</p>

          • Waethorn

            31 March, 2017 - 12:50 pm

            <blockquote><em><a href="#94511">In reply to evox81:</a></em></blockquote><p>The new build isn't even out yet. It won't be for a couple weeks. There should've been plenty of time to do this. Considering this is likely going to be a day-zero update, Microsoft already considers the build broken as-is, so slipstreaming it makes more sense than leaving it separate.</p>

        • Narg

          31 March, 2017 - 1:31 pm

          <blockquote><a href="#94411"><em>In reply to Waethorn:</em></a></blockquote><p>This is easy to understand. It's called rules of distribution. A key part of a well tenured development cycle. They set rules for how the software is distributed and updated. As changes are needed, they just follow the rules. That way nothing gets out of sync or misunderstood by the distribution chain.</p>

  • lordbaal1

    30 March, 2017 - 9:27 pm

    <p>the update haven't even shipped yet.</p><p>these are just bug fixes.</p>

  • Delmont

    31 March, 2017 - 7:45 am

    <p>OH please, patches are always a good thing.</p>

  • PhotM

    Premium Member
    31 March, 2017 - 12:00 pm

    <p>Paul,</p><p>Brandon LaBlanc(MS) admitted to Posting this to early, before the CU went live.</p><p>My questions are, Has the CU gone Live now? :confused: </p><p><br></p><p>Will the CU be available for RP Ring? </p><p><br></p><p>Best Regards,</p><p>Crysta</p>

    • Dan1986ist

      Premium Member
      31 March, 2017 - 2:54 pm

      <blockquote><a href="#94573"><em>In reply to PhotM:</em></a></blockquote><p>KB4016250 is now available for Insiders in the Slow, Fast, and Release Previews, plus those who upgraded from 14393.970 to 15063 via iso and are not part of Insiders. </p>

  • BoItmanLives

    31 March, 2017 - 12:32 pm

    <p>What a mess. "Ship it out buggy and fix it later.. " seems to be the new mantra. </p><p><br></p><p>I sure do miss the service pack days before they fired the QA team and let phone-obsessed millennials take over the windows shell team. </p>

  • DaddyBrownJr

    31 March, 2017 - 2:42 pm

    <p>This CU was very fast and painless.</p>

  • Ammy7587

    31 March, 2017 - 3:51 pm

    <p>!!!!hvh&lt;B&gt;&lt;p&gt;★★★…&lt;br&gt;</p><p>Most of us want to have good income but dont know how to do that on Internet there are a lot of methods to earn huge sum, but whenever Buddies try that they get trapped in a scam/fraud so I thought to share with you a genuine and guaranteed method for free to earn huge sum of money at home anyone of you interested should visit the page. I am more than sure that you will get best result.&lt;br&gt;</p><p>Best Of Luck for new Initiative!&lt;br&gt;</p><p><br></p><p>••••••••••••►!!!!!!!!!!!! http://goodhigh4.blogspot.com</p&gt;

  • Ammy7587

    31 March, 2017 - 3:52 pm

    <p><br></p><p>Most of us want to have good income but dont know how to do that on Internet there are a lot of methods to earn huge sum, but whenever Buddies try that they get trapped in a scam/fraud so I thought to share with you a genuine and guaranteed method for free to earn huge sum of money at home anyone of you interested should visit the page. I am more than sure that you will get best result.&lt;br&gt;</p><p>Best Of Luck for new Initiative!&lt;br&gt;</p><p><br></p><p>••••••••••••► http://www.Jobnews80.Com</p&gt;

  • FTWMikeC

    31 March, 2017 - 4:23 pm

    <p>It's reappeared, or at least it did for me.</p><p><img src=""><img src=""></p>

  • navarac

    31 March, 2017 - 5:38 pm

    <p>Inappropriate posts by Ammy7587. Go and infest another site, jerk.</p>

  • navarac

    01 April, 2017 - 3:44 am

    <p>Interestingly, the CU was accepted by a machine on 15063.0 and then taken off Insider Preview.</p>

  • hsushenon

    01 April, 2017 - 5:27 am

    <p>Its feel good to be on the other side of the comment tab :), loved your articles and talks, keep on the good work. <img src=""></p>

  • waverunning.geek

    01 April, 2017 - 10:22 am

    <p>THIS is why I don't install RTM's any more.&nbsp; I'll just wait until they push it to my PC's.&nbsp; And something tells me after that, I'll end up doing clean installs anyway.</p>

  • rvail317

    02 April, 2017 - 4:18 pm

    <p>On an Intel Z170 chipset system (Win10 build 15063, x64), USB Root Hub (USB 3.0) appears as a removable device. Did not have this error on earlier builds. Does also not appear on earlier Intel chipset systems. </p>

  • SteveSi

    04 April, 2017 - 6:40 am

    <p>What about the BIG change for Removable USB Flash drives?</p><p>Now you can have multiple partitions on UFDs! This is a big change!</p><p>Also, if you use the Format pop-up to format a new partition on a UFD, then diskmgmt.msc does not recognise the new formatted partition!</p><p>This is a major change for Removable UFDs (and looks like a bug to me?)</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