New KB3025380 Update for Windows 10 FBL_AWESOME branch
-
Any chance that the next "upgrade" will be available on an ISO (instead of requiring the horrible in-place update garbage)?
Microsoft should dump the unreliable in-place update paradigm entirely.
The way they are forcing people to use it reminds me of their stubborn refusal to fix Metro's problems (during W8 testing and release).
You're forgetting that the only way they can fix the problems with this process is by actually getting beta testers to use it...
-
-
Any chance that the next "upgrade" will be available on an ISO (instead of requiring the horrible in-place update garbage)?
Microsoft should dump the unreliable in-place update paradigm entirely.
The way they are forcing people to use it reminds me of their stubborn refusal to fix Metro's problems (during W8 testing and release).
You're forgetting that the only way they can fix the problems with this process is by actually getting beta testers to use it...
Good point. . .never been able to figure out the big deal behind the need for a clean install. . .probably just me. . .
-
-
The majority of testers are using vm's so it's a little different animal
-
The majority of testers are using vm's so it's a little different animal

Where, exactly did you make up that statistic from?
In fact, according to Microsoft, only 36% of users are using a VM.
Checking in on the Windows Insider Program
-
-
Continuous Testing Version
Any chance that the next "upgrade" will be available on an ISO (instead of requiring the horrible in-place update garbage)?
Microsoft should dump the unreliable in-place update paradigm entirely.
The way they are forcing people to use it reminds me of their stubborn refusal to fix Metro's problems (during W8 testing and release).
You're forgetting that the only way they can fix the problems with this process is by actually getting beta testers to use it...
They've been testing this dodgy update system since W8 was released.
They've had a claimed 200M beta testers (oops ... users) working on it and they still can't make it work properly.
Even ordinary unfashionable updates are hit-and-miss and they've been using the same system for years.
Microsoft update blunders going out of control
Sending out an entire OS every few months is going to cause havoc.
What about people who have:
- Crappy Internet connections?
- Mobile devices with ridiculously small download limits?
What about business users?
How will they test updates before deployment?
Apple might be able to make such a system work, but only because every Mac is identical (i.e. won't run if the hardware is modified in any way).
For example:
Yosemite kills third-party SSD support | ZDNet
I have no confidence that MS will be able to fix this new system.
Forcing people to use fashionable new systems with a proven track record of failure is not going to win MS any plaudits.
To undo the damage the W8 series caused, MS needs to use proven rock-solid code.
MS would probably be better off releasing a separate Windows Testing distro with the bleeding edge technology and useless fashionista stuff in it (like Red Hat does with Fedora).
-
They've been testing this dodgy update system since W8 was released.
No, they haven't. The new system is very different, and is called "flighting".
They've had a claimed 200M beta testers (oops ... users) working on it and they still can't make it work properly.
It's still a very early alpha stage dude...
You're conflating bugs in the updated binaries with issues with the update process. They are two different things, and I suspect you know that. So why try and pretend they are at all similar?
Sending out an entire OS every few months is going to cause havoc.
What about people who have:
- Crappy Internet connections?
- Mobile devices with ridiculously small download limits?
As opposed to now, where we get Cumulative updates that are 500MB+ in size?
What about business users?
How will they test updates before deployment?
The same way they do now... they use WSUS to block updates until they are tested, then allow them.
I have no confidence that MS will be able to fix this new system.
Wait, so you understand that it's a new system? Yet you pretended it wasn't?
-
The majority of testers are using vm's so it's a little different animal

Where, exactly did you make up that statistic from?
In fact, according to Microsoft, only 36% of users are using a VM.
Checking in on the Windows Insider Program
Why would you say I made that up for ?
I can't open the News story posted by @Brink but it's now on page 8 in this section
Windows 10: 41% of testers installed the build on their...
-
They've had a claimed 200M beta testers (oops ... users) working on it and they still can't make it work properly.
It's still a very early alpha stage dude...
That was a reference to the W8 series (the OS that was released a couple of years ago).
What you are suggesting is that MS is planning to include a system, that will only have received a few months worth of testing, in a product that needs to work perfectly out-of-the-box (or at least as well as W7 did). 
W10 needs to replace the W8 series, the way W7 replaced Vista (in market performance terms).
You're conflating bugs in the updated binaries with issues with the update process. They are two different things, and I suspect you know that. So why try and pretend they are at all similar?
Why are you pretending that buggy code isn't a separate issue to corrupted downloads?
The bigger the download, the more chance it will be corrupted.
Apparently you are unaware of the large number of posts on SevenForums, EightForums and TenForums from people whose problems were caused by corrupted downloads (i.e. their problem was solved by a new download).
Sending out an entire OS every few months is going to cause havoc.
What about people who have:
- Crappy Internet connections?
- Mobile devices with ridiculously small download limits?
As opposed to now, where we get Cumulative updates that are 500MB+ in size?
Where is Service Pack 2 for W7 (SP1 was in 2011)?
As far as I'm aware, W8 had no Service Packs (or at least they weren't designated as such).
In my books, a 3 GB download is bigger than a 500 MB download.
What about business users?
How will they test updates before deployment?
The same way they do now... they use WSUS to block updates until they are tested, then allow them.
Under the current system, each individual update can be tested and any individual update that causes issues can be avoided.
If each update is an entire OS, how do you block the broken bits?
I have no confidence that MS will be able to fix this new system.
Wait, so you understand that it's a new system? Yet you pretended it wasn't?
"New" compared to the "Old" system (i.e. one update at a time).
As far as I can tell, Service Packs didn't replace the entire OS (even though it felt like it).
The majority of testers are using vm's so it's a little different animal

Where, exactly did you make up that statistic from?
In fact, according to Microsoft, only 36% of users are using a VM.
Checking in on the Windows Insider Program
Why would you say I made that up for ?
I can't open the News story posted by @
Brink but it's now on page 8 in this section
Windows 10: 41% of testers installed the build on their...
Here is the Windows Blog link, "Checking in on the Windows Insider Program (2014-10-13)":
Checking in on the Windows Insider Program
-
Why would you say I made that up for ?
I can't open the News story posted by @
Brink but it's now on page 8 in this section
Windows 10: 41% of testers installed the build on their...
Yeah, that's the same story I just linked to, and the 41% refers to users who installed over production systems. The link says that only 36% of users installed in a VM. So that's why I'm wondering where that figure came from, since it's not from any reliable source.