New
#290
Does anyone know why these latest builds have to go through the initialising process? I don't remember the dozens of earlier ones doing this.
Does anyone know why these latest builds have to go through the initialising process? I don't remember the dozens of earlier ones doing this.
Maybe Wynona, but I was initialising for about 4 hours yesterday.
- that's how I read it..
- it's how the final product impacts new users..
-*as Insiders we're always testing, so we are perhaps more prone to impatience..
- I guess the theory is, a new user would experience the "UUP-like" delay once only..
- thereafter,*with the platform in place, future updates will be quicker and more discrete..
OK Here's something interesting maybe has some relevance. After editing the registry to set the DWORD EnableUUPScan to "0" (as well as SupportsUUP) the key was DELETED. SupportsUUP is still "0". I am now preparing to update to what I hope will provide an ESD for 15025.
I would have to say that this UUP experiment was a disservice to Insider Testing. Yeah I found an 15019 ISO but would not even post where I got it since the last time I did I got my knuckles rapped. No doubt 15025 ISO have already appeared.
While researching UUP I entered the search term "EnableUUPScam" instead of "EnableUUPScan" and got some amusing if off-topic hits
Microsoft offer the insiders who can't stand the pace a standoff pause if they wish:
Why not take a sabbatical?
Microsoft want the problem gone as much as we do.
Why does anyone think they are being abused when they offer their services free of charge to do something hard, and for a time it doesn't get easier?
If you want a break, take it, but don't try to break the system that you signed up to, by circumventing the processes that MS are keenest to see working smoothly and effectively.
And don't accuse them of doing nothing, just because your pet peeve ain't fixed yet.