Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile  

I disagree..
I love the "informal" approach..

- don't be fooled into thinking they don't care - of course they do..

HippsieGypsie said:

That's laying in on the line, Kari. All true. Do you think they'll get the message and listen? IMO they lost the balance between the technical importance and the rah-rah promotional stuff. Too young a management/leadership.

kado897 said:

Well said Kari.

I am extremely proud to have been awarded the Windows Insider MVP, I have volunteered to be an Insider and test Windows 10 for free, I am a relatively happy Windows 10 user and a Microsoft fanboy without shame, yet I would like to see us Insiders treated as adults and Insider program to focus in testing Windows instead of ninja cat jokes.

Their chosen motto says it all.

Tweet

— Twitter API (@user) View on Twitter

Upgrade process is so slow because a lot of work on the disk but low usage of CPU and RAM. It's also single threaded and multi core processors with a lot of RAM are prevalent nowadays. With so much changed during upgrade I don't think they can speeded it up considerably.

I had a clean install 16251 RS3 with virtually nothing tweaked or added, with the exception of my backup app MR. All cleaned. Then updated to 16257 RS3. From Check for Updates to Desktop was 37 minutes. That compares to a fairly well loaded 16251 RS3 (to simulate real world conditions) > 16257 RS3 of 1hr, 20mins. Both physicals, same machine. Apparently, the content of apps and data does make a big difference in time. Someone posted yesterday that they had Visual Studio on theirs, and it was a dog to update.

f14tomcat said:

I had a clean install 16251 RS3 with virtually nothing tweaked or added, with the exception of my backup app MR. All cleaned. Then updated to 16257 RS3. From Check for Updates to Desktop was 37 minutes. That compares to a fairly well loaded 16251 RS3 (to simulate real world conditions) > 16257 RS3 of 1hr, 20mins. Both physicals, same machine. Apparently, the content of apps and data does make a big difference in time. Someone posted yesterday that they had Visual Studio on theirs, and it was a dog to update.

I used to think that amount of stuff that was in the build was the determining factor in the speed/reliability of the upgrade until this build. On both my physical machine and all the VMs I was upgrading when I ran disk cleanup after the upgrade I was surprised to find they all clocked in at 23GB. So I'm not so sure now. The VMs had no non-Microsoft programs on them.

I think some people here are showing signs of suffering from "Insider fatigue"
in the real world one installs an OS and then just gets on with using it, out of the box..
we here, have been installing the same OS (Windows10) for the last few months,
so we are like to be getting just a wee bit "jaded" as a result..

it's still an amazing venture by Microsoft to put out such an advanced OS
worldwide, and it's remains a privilege to have been asked to take part in testing,
and even being allowed inside Redmond HQ in Live meetings with the insider crew

- for me, it has been an amazing journey, and I have nothing but praise
for the way that MS has been so friendly and accessible during the whole program

- three cheers for the Insider Team, I say..

BugMeister said:

I think some people here are showing signs of suffering from "Insider fatigue"
in the real world one installs an OS and then just gets on with using it, out of the box..
we here, have been installing the same OS (Windows10) for the last few months,
so we are like to be getting just a wee bit "jaded" as a result..

it's still an amazing venture by Microsoft to put out such an advanced OS
worldwide, and it's remains a privilege to have been asked to take part in testing,
and even being allowed inside Redmond HQ in Live meetings with the insider crew

- for me, it has been an amazing journey, and I have nothing but praise
for the way that MS has been so friendly and accessible during the whole program

- three cheers for the Insider Team, I say..

Yes me too, I have been at it since the second build. Kudos all that take the time to test Windows 10. It can get rough with 6 hour installs and such but there is light at the end on the tunnel.

martyfelker said:

I used to think that amount of stuff that was in the build was the determining factor in the speed/reliability of the upgrade until this build. On both my physical machine and all the VMs I was upgrading when I ran disk cleanup after the upgrade I was surprised to find they all clocked in at 23GB. So I'm not so sure now. The VMs had no non-Microsoft programs on them.

the 23GB was the MS stuff created to process the build and save the Windows files for previous. I'm referring to user added apps and data.

I understand. That's exactly why I said the amount of content in a build was a determining factor. However my recent experience updating the physical machine was different. This could very well be because I upgraded by running setup.exe on a mounted (virtual - using imdisk) 16257 ISO. Now as I posted while the setup promised to keep my data and apps that was only partially true. A few programs were completely deleted (e.g. Google Chrome Canary) and others needed to reconfigured from the beginning. The size of the Disk Cleanup was 23GB. There were over 60 non-Microsoft programs installed - fortunately Visual Studio was not one of them. I get to installing it on the Windows 10 system after I get out of the work I'm doing with Debian buster - my new favorite Linux distro.