Announcing Windows 10 Insider Preview Skip Ahead Build 16362 for PC Insider

swarfega · 13 Sep 2017

fjk61011 said:

Went out to a meeting and when I came home 16362 was installed .

Satisfying feeling huh.

LEOPEVA64 · 13 Sep 2017

swarfega said:

I got that background as well. I thought it was because I was in VM.

Some thought it was the new installation screen on Skip Ahead but no, it's a bug:

Tweet
— Twitter API (@user) View on Twitter

swarfega · 13 Sep 2017

ah thanks for that, will file a report tomorrow.

LEOPEVA64 · 13 Sep 2017

I was editing my comment with Jason Howard's tweet when I had my first BSOD in this build, it's funny, but I've never seen a GSOD in my insider builds, only BSOD

Kari · 13 Sep 2017

Almost there!

Announcing Windows 10 Insider Preview Skip Ahead Build 16362 for PC-image.png

f14tomcat · 13 Sep 2017

@Kari , did you ever resolve the problem with OneDrive continuously downloading files? The on-demand part seems to have broken after I restored an image. I thought I remembered you had something similar. I can't get it fixed.

Tony K · 13 Sep 2017

Just got home. Upgrade went well for me.

3:05 Start/Initializing – 2 minutes
3:07 Prep – 5 minutes
3:12 Download – 5 minutes
3:17 Installing – 17 minutes
3:34 Restart request
3:34 to 3:42 Make ISO – 8 minutes
3:42 Reboot
4:07 To desktop 25 minutes
4:08 to 5:15 Senior nap

Without ISO time 54 minutes. Not bad I guess. It's getting better with each build. I let it churn while napping. It went to sleep. Set that for 45 minutes.

rseiler · 13 Sep 2017

LEOPEVA64 said:

I was editing my comment with Jason Howard's tweet when I had my first BSOD in this build, it's funny, but I've never seen a GSOD in my insider builds, only BSOD

Can you elaborate? During install? I mentioned one up the thread, too. I'm looking for a way past it.

Via WU it's 0x80070643 (Kernel Security Check Failure).

Via ISO it's "0xC1900101 - 0x30018. The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation."

Both ways fail in the same spot, at 33% after the first boot (not counting the initial boot out of Windows). This error is said to mean "A device driver has stopped responding to setup.exe during the upgrade process." Thing is, there are no new 3rd-party device drivers installed since 16353.

LEOPEVA64 · 13 Sep 2017

rseiler said:

Can you elaborate? During install?

No, I had already installed the build and was using it and suddenly the BSOD appeared.

martyfelker · 14 Sep 2017

FWIW Windows 10 Education still says it the 1703 version.