Windows 10 Insider Preview Fast Build 19635.1 (mn_release) - May 28 Insider

Downloading on a physical machine. More advanced on Hyper-V VM. Manually started download to VMware 20H2 VM. I have some work to do on the VMs - needed to remote into the Hyper-V machine and see about turning off enhanced view permanently - it is only a blur. . Then there is the question of activating the VMs. On the Linux side I've installed Redcore Linux KDE which is based on Gentoo. It has some interesting features - need to setup GRUB since it didn't setup dual boot by default.

Looks like this release is more or less just cleaning up a few items that I have not noticed - marking time until the fe_release in a month I guess. Guess they will move mn-release to the slow ring around that time. I don't guess anybody really feels like an "insider" - any word on future presentations from the team??
-

49 minutes to the desktop , no bounces.

Installed without a hitch.

Getting it now...

After installing this latest build I did a check for uodates and once again got the two .NET Framework updates for the third time in three weeks

DooGie said:

After installing this latest build I did a check for uodates and once again got the two .NET Framework updates for the third time in three weeks

Likewise, DooGie.

linw said:

85 min to desktop.

Wondering how some of you get it done in well under an hour? Just curious what factors are involved.

Fast internet, fast disks and /or simpler system setups requiring less changes and less to backup ? I for instancehave pretty simple insider windows setup with little to change or save on an SSD but at this time of evening my internet tends to be slow (about only 6-8mbps so download time was over 90% of whole setup.
Even with an SSD, during setup stage it's load was most of that time at or close to 100%, one could only imagine how long would that part take on a slow HDD like of which can be found in laptops.

Restarting both VMs. Physical machine restart awaits. I'd be surprised if there are any problems but I guess you never know. After restarting the physical I will check for spurious .Net Framework CU.