It was an opinion, and I am also not getting a good experience with UUP.
Perhaps "wimpy" is a stronger term of offence across the pond than over here, where generally it is a fairly good natured term for someone who is easily put off - if so, I apologise, but do not know a good alternative to replace it with.
Here's Thesaurus.com's take on it with all the possibly offensive synonyms expurgated:
Attachment 119586
SorrySorry, couldn't help :)
I don't mind being in the fast lane and testing stuff for free for Microsoft, however if I find a problem I will report it and if there is a work around like Wax-Off, I will do that. Now that I have 15025 installed I will go edit the registry to Wax-On again.
OK. Here's what happened after the upgrade to build 15025
1) NO install.esd. I use the Everything program and service to search.
2) SupportUUP and EnableUUPScan have both been reset to enabled "1".
If we want an install.esd we will probably have to create it ourselves. For myself I can wait for Microsoft to get around to releasing an ISO or if I'm desperate I hunt for a "warez"
UUP is apparently here to stay. IMHO it is a scheme to reduce the load on Microsoft's update servers. They really should be transparent about this.
I will say that disabling UUP with the registry hack resulted in a faster upgrade even if I didn't get the esd so I've disabled it again. After rebooting I'll check to see if the EnableUUPScan value is even there.
And yes after I've backed up the current image (quite fast since I backup to a HDD - (I use my external HDD for Windows Server 2016 backups.) I will do a disk cleanup to free up disk space.
So much for this update adventure. I'll get to the VMs when I get around to it.
Two days running I have not been able to get past the initialising stage, I shall shut down and try again tomorrow.
Same here. I think I'm giving up on this build. How can you test this build when you can't even get it installed? Hopefully the next build will be easier to install...
Very good advice. :)
I'm quoting the above because IMO it summarises the general feeling of users that are experiencing problems with UUP.
But if I may add some comment...
In the case of UUP, the data collected from those Insiders that fail to upgrade successfully is far more valuable to MS than data from machines like my own that update without a hitch. Regarding fixing the UUP delivery mechanism... it's been a little over 2 months notwithstanding the interruption of the holiday season. I'm prepared to give the devs just a little more time to meet their April deadlines.
Quote
