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

Is this what others are seeing?
I'm attempting to install the update in a Hyper V VM. I setup the VM a week or so ago. (First time to use a VM.) I installed Build 16288, changed the registry, and 16362 downloaded and installed. Windows isn't activated. Today I started the update process to 17004 in the VM, It failed. The 2nd attempt was successful to the "Restart" phase. I created an ISO. then clicked the "Restart" button. It came back to 16362 (no restoring previous version message.) Opened update, the Restart button still there, as well as the message about restarting. Repeated that exercise 3 times with the same result. Mounted the ISO and ran setup there, I now have 17004 running in the VM.
Because I have no experience with a VM, I'm not sure if the time it takes to respond is normal, but it is slow. I allocated 4 GB RAM and 250GB on a spinner when creating the VM.

I had to reinstall W10 PRO x64 EN-US on a Hyper-V virtual machine due several reasons. Used the latest Skippy ISO I had for EN-US, build 16362. Booted from ISO, removed all existing partitions and clean installed.

When on desktop, switched to a Microsoft account (I always install using a local account to get user profile named as I prefer). Opened Settings >WU, was somewhat surprised to see WU had already started downloading 17004.

Checking registry and Insider settings, the VM was set to Skippy builds without any interaction from my side. Skippy Fast. No registry tweaks required, no changing from the usual default Slow ring.

I am not sure if this is because the install media I used was Skippy ISO, or if the settings were retained based on machine's hardware signature and digital license (this VM was and remains activated).

Really positively surprised!

Kari

I had a lot of strange behavior during upgrade in Hyper-V.

First attempt failed with corrupt or missing files. I suspect my Modem was just about to crash. (Which it did 30min later)

Second attempt just logged out from my system even though I hit Reboot button.

Third attempt (just hitting Reboot button) went smoothly though.

Kari said:

I had to reinstall W10 PRO x64 EN-US on a Hyper-V virtual machine due several reasons. Used the latest Skippy ISO I had for EN-US, build 16362. Booted from ISO, removed all existing partitions and clean installed.

When on desktop, switched to a Microsoft account (I always install using a local account to get user profile named as I prefer). Opened Settings >WU, was somewhat surprised to see WU had already started downloading 17004.

Checking registry and Insider settings, the VM was set to Skippy builds without any interaction from my side. Skippy Fast. No registry tweaks required, no changing from the usual default Slow ring.

I am not sure if this is because the install media I used was Skippy ISO, or if the settings were retained based on machine's hardware signature and digital license (this VM was and remains activated).

Really positively surprised!

Kari

Yeah - I found same happened last time I clean built. Fast Ring reset to Slow, Skippy retained setting.

If you think about it, MS would have to ensure Skippy kept its setting, because of the limited quota of subscribers. They would lose all Skippy subscribers in one go -LOL.

We should not forget our registry hack is not official and relatively few Skippyists will know how to do that.

This build came in last night half unexpectedly. It downloaded and installed while I was snoozing. No problems making ISO either. Remembered to turn off WD and ISO was finished within few minutes. That M.2 Samsung SSD did good job on it.
Just going thru it to check out new things. Found one problem in Settings, Storage part starts but closes whole settings. Problem with CD/DVD also persists. But for now, so far, so good. For me at least it was important to catch up with important updates non-Skippy got. I will probably go for clean install when build becomes official.
For some reason, Fluent Design is not as pronounced as it looks for others.

Kari said:

Checking registry and Insider settings, the VM was set to Skippy builds without any interaction from my side. Skippy Fast. No registry tweaks required, no changing from the usual default Slow ring.

I am not sure if this is because the install media I used was Skippy ISO, or if the settings were retained based on machine's hardware signature and digital license (this VM was and remains activated).

Really positively surprised!

Kari

cereberus said:

Yeah - I found same happened last time I clean built. Fast Ring reset to Slow, Skippy retained setting.

If you think about it, MS would have to ensure Skippy kept its setting, because of the limited quota of subscribers. They would lose all Skippy subscribers in one go -LOL.

We should not forget our registry hack is not official and relatively few Skippyists will know how to do that.

No mystery really. Skippy was born Fast Ring by default. Only choice available, and unchangeable.

sfc /scannow can't fix some errors it found.

f14tomcat said:

No mystery really. Skippy was born Fast Ring by default. Only choice available, and unchangeable.

A misunderstanding here, I see.

By default, when you clean install Windows 10 Insider version, you will be in Slow Ring. You have to manually switch to Fast Ring, and will then be on Fast Ring > The Next version of Windows (not Skippy). In no case will you be set by default on a clean install to Fast Ring > Skippy.

Except, that was what happened to me this morning on that VM.

Went to bed while 17004 was upgrading. All there this morning. Don't know how long it took.