Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC Insider

Rocky · 20 Dec 2017

EdTittel said:

Whoa! This one took over THREE HOURS to download, initialize and install on my Dell Venue Pro 11 7139 (i5 4210Y CPU, 8 GB RAM, 256 GB SSD, HD3000? GPU). That's more than three times longer than it ever took for the prior round of Insider Preview flights for Win10 Pro. Wonder what's up here? Anybody know?
Thanks,
--Ed--

Same here. It usually takes me 20 minutes to download and install and initialize the typical Insider build but this one took one hour. That is 3X the amount of time for me as well.

LEOPEVA64 · 20 Dec 2017

It seems that "Sets" is activated via server and can appear at any time after the build is installed, so this function could appear later to those who don't have it yet... or not, I think this also confirms that it can't be enabled by changing some entries in the registry as could be done to enter Skip Ahead.

Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC-148.jpg

martyfelker · 21 Dec 2017

linw said:

Thanks for headsup on network type. Mine was set to Public. Wonder why MS does this??

Care to share what post you were replying to?

kado897 · 21 Dec 2017

kado897 said:

Just discovered it switched my network to public. Might be worth people checking.

linw said:

Thanks for headsup on network type. Mine was set to Public. Wonder why MS does this??

martyfelker said:

Care to share what post you were replying to?

This one Marty.

slicendice · 21 Dec 2017

They've been busy @ MS. A lot of interesting stuff to test. Grabbing this one now!

rseiler · 21 Dec 2017

Firefox situation from a Windows Audio guy at MS: "Not only can you not expect a patch for 17063, I am not 100% convinced the fix will be in the first January flight... but we'll see."

Kari · 21 Dec 2017

Geeks, has anyone managed to upgrade Enterprise edition?

cereberus · 21 Dec 2017

Is Skipahead stone dead now?

martyfelker · 21 Dec 2017

kado897 said:

This one Marty.

Thank you.

martyfelker · 21 Dec 2017

I'm not sure Microsoft should stick with this text which I was able to capture during the upgrade of my Windows 10 nested in a virtual ESXi 6.5 server. I think this is new with this build but I could certainly be wrong.