Announcing Windows 10 Insider Preview Build 15025 for PC Insider
-
Whoa! I just re-read the whole thread (first 38 pages through which I'd read yesterday, plus the 10 pages added since then). This has been the wildest ride on the Insider Preview express for quite a long while. I'd say we'd have to reach back to pre-1507 days to see this level of mystery and mayhem. If they still want to hit the 1704 time window for the upcoming next major release, it's clear they have a LOT of work to do.
After reading all the back'n'forth on UUP and how long somebody should be willing to wait for it to grind through to completion, here's my 2¢ worth on this subject. I've got two test machines. I'm willing to give 1 of them 6-8 hours to get through download and install, for the other no more than 2. My thinking is that anything that takes longer than 6-8 hours to install is an outright failure and I shouldn't have to devote the time necessary to keep checking on completion longer than that. Period. For the other machine, it's simply because 2 hours can slip into my working day without too much disruption, but having to ping-pong checking on 2 machines for longer than that *IS* a disruption, and I won't have it.
And there it is! I totally get Kari's insistence that some people stick it out to the bitter end, because MS needs the telemetry data. I guess if I had more VMs stood up for this kind of thing I could let them run ad infinitum. But I haven't done that yet, though now I suppose I probably should...
Thanks for all your input, observations, and ideas. Always a pleasure to see the community work things out. If only MS were as collegial with Insiders as we are with each other here!
Best,
--Ed--
Totally agree* I think UUP has deliberately its ups and downs. Just not sure if this last down was meant to be this deep.
And think that fahrfrd was the one*to point out importance of*sticking with UUP on... Beside all the gurus :)
-
-
I wonder why the difference. My ESD created ISO is the same as Ztruker, 3,345,962 KB.
Could it be 32 bit vs 64 bit?
-
Right click on the taskbar doesn't do anything for me. Anyone else seeing this?
Is this permanent (long lasting) or just a minute or even half long? I had that problem (short term) in previous build, sfc /scannow and repairing with DISM fixed it.
-
Whoa! I just re-read the whole thread (first 38 pages through which I'd read yesterday, plus the 10 pages added since then). This has been the wildest ride on the Insider Preview express for quite a long while. I'd say we'd have to reach back to pre-1507 days to see this level of mystery and mayhem. If they still want to hit the 1704 time window for the upcoming next major release, it's clear they have a LOT of work to do.
After reading all the back'n'forth on UUP and how long somebody should be willing to wait for it to grind through to completion, here's my 2¢ worth on this subject. I've got two test machines. I'm willing to give 1 of them 6-8 hours to get through download and install, for the other no more than 2. My thinking is that anything that takes longer than 6-8 hours to install is an outright failure and I shouldn't have to devote the time necessary to keep checking on completion longer than that. Period. For the other machine, it's simply because 2 hours can slip into my working day without too much disruption, but having to ping-pong checking on 2 machines for longer than that *IS* a disruption, and I won't have it.
And there it is! I totally get Kari's insistence that some people stick it out to the bitter end, because MS needs the telemetry data. I guess if I had more VMs stood up for this kind of thing I could let them run ad infinitum. But I haven't done that yet, though now I suppose I probably should...
Thanks for all your input, observations, and ideas. Always a pleasure to see the community work things out. If only MS were as collegial with Insiders as we are with each other here!
Best,
--Ed--
There is no way that UUP can be released to the general public with it's present performance. It will cause mayhem out there.
-
-
Totally agree*
I think UUP has deliberately its ups and downs. Just not sure if this last down was meant to be this deep.
And think that fahrfrd was the one*to point out importance of*sticking with UUP on... Beside all the gurus :)
Complaining here, feels good, but the only thing that will help is using the Feedback Hub, or the Twitter thingy they have set up.
And don't just complain! Send data, screenshots, and so on too.
Like a brigade commander I met, said to our unit once, about our SOP(standard operating procedure): "You can tell me something is screwed up or not going to work well, but you also need to tell me why, before I'll take it into account."
-
Could it be 32 bit vs 64 bit?
I believe that 32-bit installation doesn't work at all in this build via Windows Update. Not sure whether that's UUP or ESD or both or neither, but something doesn't work (and is mentioned in the original blog post).
I think that's part of why they released the ISOs yesterday.
So I'd be very surprised if those sizes quoted are 32-bit versions, except if it was an original ISO.
-
There is no way that UUP can be released to the general public with it's present performance. It will cause mayhem out there.
Yup, because it's already caused Mahem in here!
I will continue to let UUP be my first option with each new Insider Build release; however, if it doesn't work within a reasonable time, I'm off to the ESD races.
-
Is this permanent (long lasting) or just a minute or even half long? I had that problem (short term) in previous build, sfc /scannow and repairing with DISM fixed it.
It's permanent Andre. I'm just not sure whether this is an artifact caused by the dodgy VirtualBox display driver which works only on some releases.
-
Complaining here, feels good, but the only thing that will help is using the Feedback Hub, or the Twitter thingy they have set up.
And don't just complain! Send data, screenshots, and so on too.
Like a brigade commander I met, said to our unit once, about our SOP(standard operating procedure): "You can tell me something is screwed up or not going to work well, but you also need to tell me why, before I'll take it into account."
Methinks you're preaching to the choir, Cliff. I, for one, have already told Microsoft about UUP on my system, and upvoted every post I could find about it. Not much more I can do without being repetitive.
-
-
Complaining here, feels good, but the only thing that will help is using the Feedback Hub, or the Twitter thingy they have set up.
And don't just complain! Send data, screenshots, and so on too.
Like a brigade commander I met, said to our unit once, about our SOP(standard operating procedure): "You can tell me something is screwed up or not going to work well, but you also need to tell me why, before I'll take it into account."
Feedback sent as usual. Always do that :)
As far as screenshots... in case of UUP, MS has all the data needed. That's why I wrote that some ups and downs were expected ... From one point further, things are going to turn for the better. Hope we'll be there soon