New Windows 10 Insider Preview Fast+Skip Build 18917 (20H1) - June 12 Insider

Hi folks

Via UUP and update from a 1903 system took around 15 mins once I'd got the ISO created-- the download was brutally fast --that depends on your Internet --I have over 1 Gb/s so no prob there.

HP envy laptop -- 8GB RAM, 256 GB SSD, Intel Core duo i5 processor, Intel Graphics -- decent machine but not blazingly fast.

I really recommend the UUPDUMP method - especially if you have more than 1 machine to update - whether physical or virtual machines.

Cheers
jimbo

kado897 said:

Using UUPDUMP doesn't help MS improve the upgrade process. I will use it but only if WU has failed.

Hi there

That's a good answer of course however I'm not enrolled in the insider program but like checking these builds on an "ad hoc" basis -- the reason I want this one is to test to destruction the WSL2 system.

Cheers
jimbo

I have been unable to update Insider from build 18912 to 18917 using Windows Update. So I downloaded the files from UUPDump and mounted the ISO. But again the install failed at the last boot. The error messages don't given me enough info to know what has caused the failure, they're too vague or generic.
Perhaps my component changes have a bearing on this. I have just upgraded my desktop with new mobo, CPU, RAM and Video card (details in my system 1 specs.)
I dual boot W10 1903 (on a 250 GB NVMe card, in socket M2_1) and Insider (on a 500 GB NVMe card, in socket M2_2.) Both these cards, and my other drives are carry-overs from the previous installation.
Windows boot manager defaults to "Insider" on start up. But since installing the new components, often the boot fails with a message that "A required device isn't connected or can't be accessed" Error 0x000000e.
While there is normally no identification of what caused the failure, I have seen 'Winload.efi' listed as the offending file. Several copies of this file exist, including one in C:\Windows\System32\Boot
Using Esc to get out of that error screen, (which auto opens the BIOS page) then closing BIOS without making any changes results in a normal boot.
Do I need to repair the MBR?
The 250 GB NVMe card has an "EFI System" partition. The 500 GB NVMe card does not have an "EFI System" partition. This screen grab from Disk Management shows how the drives are partitioned. I have not attempted to alter how Windows set up the drives.


Attachment 237021Invalid attachment ????
Are these partitions correct? Does the fact that the larger (Insider) drive does not have an "EFI System" partition have any bearing?
Any and all suggestions on how to get "Insider" to update to build 18917 will be appreciated. I know a clean install may be the best solution, but I have many apps so a fix other than a clean install has its attractions

Went to use it today and it was broke, wouldn't even fire up, couldn't get to anything to see why. So a reinstall and try again today.

Just installed within the last hour or so. It seemed quick through the getting things ready stages and also installing although ultimately it was after lunch when I finally checked the end result. All seems OK up to now.