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

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

 

Satisfying feeling huh.

 

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

Tweet



— Twitter API (@user) date

 

ah thanks for that, will file a report tomorrow.

 

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 *sarc

 

Almost there!

 

@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.

 

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 *Biggrin

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.

 

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.

 

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

 

FWIW Windows 10 Education still says it the 1703 version.

 

Starting the upgrade of the physical machine - and its proceeding rapidly



It's now starting the downloading phase. Just saw an article posted here on so-called "bashware" which is malware infecting the WSL. This sucks badly. I suppose I can try installing a Linux AV and start a scan when the bash command is called. But I must study this further.

 

That was resolved with upgrade to next build, I guess repair install had done the same. Until the upgrade, I found no solution which forced me to unlink the Microsoft account in question from OneDrive. Checked a few times linking the account again, issue remained, unlinked again but after the upgrade it was then back to normal.

Skippy is still shown as 1703. it's the non-Skippy that was changed to 1709.

 

Having trouble setting up a printer.

 

Yes I noticed, it looks even worse on the monitor. Maybe because of 125% scaling ?