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

Posted on March 30, 2017 by Paul Thurrott in Windows 10 with 30 Comments

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.

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.

 

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (30)

30 responses to “Microsoft Already Created Its First Cumulative Update for Windows 10 Version 1703”

  1. dmartin

    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. :-)

  2. Delmont

    OH please, patches are always a good thing.

  3. rvail317

    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.

  4. waverunning.geek

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

  5. hsushenon

    Its feel good to be on the other side of the comment tab :), loved your articles and talks, keep on the good work.

  6. navarac

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

  7. navarac

    Inappropriate posts by Ammy7587. Go and infest another site, jerk.

  8. FTWMikeC

    It's reappeared, or at least it did for me.

  9. Ammy7587


    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.<br>

    Best Of Luck for new Initiative!<br>


    ••••••••••••► http://www.Jobnews80.Com

  10. Ammy7587

    !!!!hvh<B><p>★★★…<br>

    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.<br>

    Best Of Luck for new Initiative!<br>


    ••••••••••••►!!!!!!!!!!!! http://goodhigh4.blogspot.com

  11. DaddyBrownJr

    This CU was very fast and painless.

  12. BoItmanLives

    What a mess. "Ship it out buggy and fix it later.. " seems to be the new mantra.


    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.

  13. PhotM

    Paul,

    Brandon LaBlanc(MS) admitted to Posting this to early, before the CU went live.

    My questions are, Has the CU gone Live now? :confused:


    Will the CU be available for RP Ring?


    Best Regards,

    Crysta

  14. lordbaal1

    the update haven't even shipped yet.

    these are just bug fixes.

  15. dstrauss

    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.

  16. Waethorn

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

    • johnbaxter

      In reply to Waethorn:
      1. The build has gone to the OEM partners for whatever-they-do and installation.
      2. The cumulative update process needs testing. (The pulling of the update suggests the process might need "adjustment".)
      • Waethorn

        In reply to johnbaxter:

        I'm talking specifically about the build as it is on Windows Update.

        • Narg

          In reply to Waethorn:

          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.

        • evox81

          In reply to Waethorn:

          I'm assuming that proper installation of the build is one thing that is extensively tested. The assumption that installations will function properly is based on the build remaining in a steady state. Rolling this update in to the build essentially created a new build, potentially invalidating that testing.

          • Waethorn

            In reply to evox81:

            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.

  17. wizarrc

    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 & 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.

    • Mike Chace

      In reply to wizarrc: 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!!!


  18. ChristopherCollins

    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.


    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.

  19. straker135

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

  20. bdollerup

    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.


    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).

  21. SteveSi

    What about the BIG change for Removable USB Flash drives?

    Now you can have multiple partitions on UFDs! This is a big change!

    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!

    This is a major change for Removable UFDs (and looks like a bug to me?)

Leave a Reply