Win10 beta builds on hold for UUP

Topic

New Reply

The last beta build for the next version of Win10 (Creators Update/Redstone 2/version 1703 build 14971) was released on Nov. 17, and it was a real sno
[See the full post at: Win10 beta builds on hold for UUP]

Reply | Quote

Replies

Do you ever get the feeling that, within MS, the left hand does not know what the right hand is doing?

Reply | Quote

MS is a huge corporation. Many people inside the company hold opinions that are quite different from others.

In this case, I really don’t understand why UUP is such a big deal. But it is. There’s the data savings, which will reduce the load on Microsoft’s servers when the version update hits – but Microsoft’s already throttling the release of new versions.

There’s rumblings about moving update detection from the local machine into the cloud, which would be nice for Mobile (and would be GREAT for Windows 7), but I don’t see it making much difference in Win10.

If Microsoft were talking about a new approach that kicks in for every patch, it’d be a different story. Again, we’re talking about maybe two updates per year.

So all in all, I have no idea why UUP is so important – and I wonder if the UUP rollout is just a cover story for a bigger delay. (Note that a major delay may not be a bad omen! Depends on why they’re delaying.)

Reply | Quote

The initial delay had already been explained in the same announcement:

“We will not be releasing a PC build this week due to a blocking bug that could result in broken apps after updating to a new build.”

Reply | Quote

True.

Reply | Quote

I’d love a 2 to 3 year delay between major releases.

We can only dream of a return to rational behavior.

-Noel

Reply | Quote

It is a big deal because of what happens behind the scenes.
For the end user this should be transparent, but as we know, Microsoft has released 1607 for Windows 10 and Windows Server 2016 now under CBB and LTSB and still has not resolved the WSUS initial patching issue.
UUP should be the next iteration from BITS and Delivery Optimization and I hope they take their time to get it right the first time.

Reply | Quote

“Dona Sarkar says the changes are exciting”.
She needs to get out more.

Reply | Quote

The way I read it, this will further restrict choice in updating. Looks like the “service” will check your PC and determine what you “need” to download. Seems like a non-service to me – just a down-your-throat force feeding.

Maybe that will be the time for moving from Group B to Group w.

Reply | Quote

It’s not about reducing bits, it’s about MORE CONTROL.

Reply | Quote

… and I mistakenly attributed that to Dona when, in fact, Jen Gentleman said it. Jen’s been a tremendous help on Reddit….

Reply | Quote

LTSB

Reply | Quote

…or in the Cloud.
Based on a lot of posts here, I start thinking that Microsoft’s approach is the only rational one and they have the full backing of the industry. Apple does the same, Google does the same and Firefox is very close to using the same concept. Antivirus companies have done it for years.
This is a case of IT driving the business or business driving the IT and it will always create a conflict.
As a matter of principle, managers don’t like proactive approaches, because they cannot put anything on the table in front of their superiors if “nothing” happens and in some ways they are better off if systems don’t work well, to have a reason to justify their reason for being in a job.

Reply | Quote

Isn’t this about Windows 10?

Aren’t you talking about Windows 7?

Reply | Quote

@ ch100 ……. LTSB is only available to Win 10 Ent E5 users, which costs a bundle.

Reply | Quote

UUP is very similar to how Windows Update had worked efficiently in Win 7/8.1 prior to the Patchocalypse in Oct 2016, ie minimal download size, about 100MB or less, during the monthly Patch Tuesday. Similarly for Win XP/Vista.
……. In comparison, the cumulative monthly Patch Rollups for Win 7 is expected to be about 400MB in download file size in July 2017 n about 1.2GB in “crippling” size in Dec 2019. This is excluding security updates/rollups for .NET framework, IE 11 n Office. The new Patchocalypse for Win 7/8.1 is similar to how cumulative updates n upgrades r dished out to Win 10 cptrs since 29 July 2015.
.
The former method(b4 Oct 2016) had M$’s update servers scanning Win 7/8.1 cptrs b4 displaying the needed or missing updates for eventual download n install by the users.
……. The latter method has M$’s update servers dishing out the same huge cumulative updates/rollups to ALL the Win 10/8.1/7 cptrs n then letting the local machines/cptrs sort out which updates are needed to be installed.
.
Monthly cumulative updates for Win 10 did not reach a gargantuan file size bc new versions of Win 10 were released about every 6 months, ie version 1507 launched, v.1511 n v.1607. But every version or feature upgrade released thru Windows Update was about 3GB in size, ie they were practically like a clean reinstall of the OS.
.
Seems, M$ hv degraded Windows Update for Win 7/8.1 n r improving it for Win 10 with UUP, in order to push Win 7/8.1 users onto Win 10.

Reply | Quote

I suggest that SO many good 3rd party tools have been developed because professional level, long release cycle operating systems have been available to everyone, including the home entrepreneur.

The foundation can’t be chipped up and re poured every few months and expect people to build good buildings on top! It takes more than months to design and code a useful application. That’s because simple stuff like “Calculator” and “Weather” has already been done.

Windows is not an application, it’s an operating system. And it’s complex; it takes people a long time to figure out how to write things for it.

I believe nothing significant will be written to it until a rational release cycle, embodying a longer cycle, fully engineered APIs, and TESTING is re-embraced.

-Noel

Reply | Quote

Noel, I think the desktop operating systems as we have known them are in their last years. Microsoft is transitioning to server based computing and this is why they are gambling with Windows 10. There is little point to stick with a dying concept for too long although there will always be niche segments and use case scenarios for Windows 7 or XP or even Windows NT 4 for years to come.

Reply | Quote

Win 10 v.1607 was released on 02 Aug 2016 as the Anniversary Update or Test Build 14393.
.
Fyi, the recent Nov 2016 cumulative update for Win 10 v.1607 32bit (KB3200970) is about 500MB in size, ….
… n the Nov 2016 cumulative update for the Edge browser of Win 10 v.1607 32bit (KB3194798) is about 400MB in size.
……. Wow.!
.
The next version of Win 10 is scheduled to be released only in March 2017 or v.1703. Those with Data Caps or slow Internet plans will hv more problems by then, ie in Feb 2017.
……. Also, their Win 10 cptrs will need to work quite hard n long to download n install the huge cumulative updates.

Reply | Quote

+1

Reply | Quote

M$ shills were saying that the release of Win 10 was to save on support costs by getting rid of the many editioned Win 7, ie M$ would only hv to support the editionless Win 10.
……. Turns out, M$ r now supporting Win 10 RTM or version 1507, Win 10 v.1511 n Win 10 v.1607.

Reply | Quote

… but 1507 will only get updates for another three months, until March 14, 2017:

http://windowsitpro.com/windows-10/windows-10-anniversary-update-designated-current-branch-business-cbb

Reply | Quote

@ b ……. Thanks for the info.
.
By March 2017, the next version of Win 10 should hv been released as scheduled by M$, ie Win 10 Version 1703 = back to square one.
……. Also, in March 2017, M$ will still be supporting Win 10 LTSB, some of which will still be based on Version 1507.

Reply | Quote