Delivery of Windows 10 Insider Preview Builds “Paused” for Transition to UUP

Posted on December 3, 2016 by Paul Thurrott in Windows 10 with 15 Comments

Delivery of Windows 10 Insider Preview Builds "Paused" for Transition to UUP

Microsoft quietly revealed last night that it is pausing the delivery of Windows 10 Insider Preview builds for PCs so that it can transition to the new Unified Update Platform delivery system.

“We are getting ready to start releasing PC builds to Insiders using UUP,” a short update from Microsoft’s Dona Sarkar reads. “To prepare for this, we are going to pause all PC builds for both the Fast and Slow rings starting [last night, Friday December 2]. We will begin flighting the latest builds via UUP starting with our internal rings first then to Insiders based on each ring’s promotion criteria. We’re excited to be able to release builds for PC to Insiders using UUP.”

As you may recall, Microsoft announced its Unified Update Platform (UUP) technologies about a month ago with the of making the delivery of Windows updates more efficient, a key need in this age of Windows as a service. As described by Microsoft, UUP has three key benefits:

Reduction of update download size. Using differential technologies, Microsoft will be able to deliver only the changes needed on a device-by-device basis, rather than require a full build download. The firm estimates that users will see update download size reduced by 35 percent on major Windows updates, though the real impact won’t be felt until after the Creators Update ships in Spring 2017.

More efficient method for checking for new updates. Microsoft is also revamping how Windows 10 checks for updates. “We are reducing the update data sent to client devices as well as the amount of processing we are doing on devices,” Microsoft Director Bill Karagounis explained in November. Basically, the check will now occur in the cloud, not on the device, a change that will lead to faster checks for updates. Karagounis noted that Mobile will see a more dramatic performance benefit than PC.

Bring the best of PC to Mobile. With UUP, Mobile will be able to jump to the latest build in one “hop” just like PC does today. That is, Mobile users will no longer need to sometimes install prerequisite builds before they can move forward to the most recent build.

UUP flighting of builds rolled out to Mobile devices in the Insider program starting in November, and at that time Microsoft said it would rollout UUP in stages. So this pause represents the beginning of the second phase, where PC-based Insiders builds will also start to be delivered via UUP. Later, Windows 10 for IoT and HoloLens will be brought on board as well. And then the public shipping builds of Windows 10 will be transitioned to this new system later in 2017.


Join the discussion!


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

Comments (15)

15 responses to “Delivery of Windows 10 Insider Preview Builds “Paused” for Transition to UUP”

  1. 442

    OK, if Dona Sarkar had an announcement on this, how was it a "quietly announced" statement?  Is she not the spokes person for releases?  Sorry, just wondering....

    • 742

      In reply to Narg:

      It was quiet from the point of view that this announcement was tacked onto an existing blog post (as an update) about build 14977 going to Windows 10 Mobile devices. It wasn't a specific blog post about this topic.

  2. 2068

    Why do I have a feeling that UUP uses the Bittorrent protocol to check and deliver the updates.  

  3. 1775

    >...with the [goal] of making the delivery...

  4. 5530

    Will UUP reduce the time needed to install the update, though? My experience with the Anniversary Update was that it was that it took waaaay too long and was quite disruptive.

    • 3148

      In reply to FalseAgent:

      Okay, so here's how I think it works. The installastion process will STILL* be like before. That is, the OS will install by applying a new image and moving the old image in the Windows.old folder. But my guess is that rather than DOWNLOADING a full OS image each time, the new process will download the differences in existing version and new version and then *BUILD* a local image using files from existing install and the newly downloaded files and apply this image for install.

      I'll have to try out the new system to be sure that this is the case