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

johngalt said:

I just clean installed 16299 and threw 17046 on top - I was prompted by the system after upgrade that OneDrive needs my attention (it needs to run the upgrade).

Since I did that whole process about 4 times in 2 weeks, and I saw it every time, that makes me wonder - were you clean installing the IP builds directly?

@johngalt
Yes, like I said, clean install...not update. It will not update here on either of my 17046 physical OS's. Rollback every time...over and over. Known problem in Feedback and at MS.

You're updating 16299 > 17046. That works fine, always did, OneDrive and all. My problem, and other people's, is going from 17046 > 17063.

Everything running smoothly apart from Bluetooth speakers....each time I sort it out it reoccurs on next start up.....keyboard, mouse are also Bluetooth yet are working perfectly.

To say its a bloody nuisance is an understatement.....there is no set way to get reconnected, apart from fiddling around such as reinstalling, removing USB, troubleshooting sound problems etc etc.

f14tomcat said:

@johngalt
Yes, like I said, clean install...not update. It will not update here on either of my 17046 physical OS's. Rollback every time...over and over. Known problem in Feedback and at MS.

You're updating 16299 > 17046. That works fine, always did, OneDrive and all. My problem, and other people's, is going from 17046 > 17063.

I clean installed 16299, then upgraded directly to 17046, and then upgrade from 17046 to 17063 which I am on now.

You, apparently, are clean installing 17046 directly and upgrading to 17063, or clean installing 17063 directly, correct?

Technically, Microsoft doesn't support clean direct installs of Fast ring builds, as mentioned by Kari in this tutorial: Windows Insider - Clean install latest Fast Ring build Installation Upgrade Tutorials

And that is why I am clean installing 16299 and then upgrading to Fast ring builds.

Have you tried clean installing 17025 and upgrading to 17063 and see if it works that way, instead of starting with 17046?

Fixed in nightly builds.

johngalt said:

I clean installed 16299, then upgraded directly to 17046, and then upgrade from 17046 to 17063 which I am on now.

You, apparently, are clean installing 17046 directly and upgrading to 17063, or clean installing 17063 directly, correct?

Technically, Microsoft doesn't support clean direct installs of Fast ring builds, as mentioned by Kari in this tutorial: Windows Insider - Clean install latest Fast Ring build Installation Upgrade Tutorials

And that is why I am clean installing 16299 and then upgrading to Fast ring builds.

Have you tried clean installing 17025 and upgrading to 17063 and see if it works that way, instead of starting with 17046?

No. I have not jumped back several builds to find which one will successfully migrate to the next, then to the next, etc. I'll keep it in mind, though. Thanks for the suggestion.

Has anyone else noticed something odd about 17063? This is on a clean install of 17063.

If you do a reagentc /info on it, you'll find the Recovery "partition" is pointing to the OS partition itself, not a separate one like the 450MB ones as usual. In fact, there is no separate Recovery partition. The "Recovery Partition" isn't a partition at all, it's a folder under C:.

Like this:



17046 is not like that, and I don't recall seeing it before.

In a VM I successfully upgraded from 17046 > 17063, the same "Recovery " partition is under C:, but the reagentc /info still points to the original 450MB Recovery partition that was already there for 17046.

Any ideas?