New
#150
]I've selected Skippy a couple of times over the last few days and each time it reverts back to Fast after a few hours. I'll try again now... and again it is showing Fast. Just reverted to Skip and its thinking about it... and a couple of minutes later it is still thinking and just a spinning circle.
And its just reverted back to Fast. Again
From the Feedback Hub
Today we are moving the Fast ring forward to 20H1 and merging the small group of Insiders who opted-in to Skip Ahead back into the Fast ring with the release of Windows 10 Insider Preview Build20H1 Build 18875. That means Insiders in the Fast ring and those who opted-in to Skip Ahead will receive the same builds going forward.
.So we who opted for the Skip Ahead Ring should, once again, consider ourselfves the few, the proud, the gullible
For the first I've actually had to use the Registry Hack to revert a VM to the Fast Ring in order for the ISO setup to work - which it did flawlessly. This may be something that you guys might check.
I always just do the reghack to join skip ahead, it's the easiest way. However now skip/fast are the same.
Yes, all rather convoluted, that's why went back and posted this to him.
New Windows 10 Insider Preview Fast+Skip Build 18875 (20H1) - April 10 Insider - Page 15 - Windows 10 Forums
Running 18362.53 (Fast ring, got the Update to 18875, went through the whole process -- little over 30 minutes -- but when the desktop came back, I was still on 18632 and got a message about being unable to complete the update, but no indication as to why.
That was a few hours ago, so since I built the ISO for 18875 through UUPDump, am trying the update using that now.
Update: Upgrade from ISO file failed too; again, no indication why.
@chrisn -- looking back, just saw your post about doing the upgrade from 18362.30. So, I will try a restore from that image and see if the 18875 upgrade works. Thanks for posting that information.
UPDATE: Upgrade worked from 18362.30!
Last edited by Mark Phelps; 11 Apr 2019 at 20:25.
Guys, I disabled and stopped windows search and was able to upgrade from 18362.53. Not even kidding
I confirm that disabling windows search do the tricks.
But i needed to either run wureset.bat or clearing the Software Distribution folder....
Update failed during reboot. Not sure where as I was reading. Came back to check before I went to bed and I was back to 18362.53.
Is there a log file that can tell me what failed?
I looked at "C:\$WINDOWS.~BT\Sources\Panther\setupact.log" and "C:\$WINDOWS.~BT\Sources\Panther\setuperr.log" but I don't really understand what I'm reading. There are reported errors but they don't mean anything to me.
These are the log files in case anyone else can read them:
setupact.zip
setuperr.zip
Success! I used a Macrium image to go back to 18362.30. But before, I used UUPtoISO (thanks, Kari) to make a 18875 ISO. The last failed install luckily didn't delete the necessary files. Installation went smoothly.