[Update: It's fixed]Microsoft accidentally removes some Insiders from Skip Ahead Ring
2 min. read
Updated on
Read our disclosure page to find out how can you help MSPoweruser sustain the editorial team Read more
Update: Microsoft WIP head Dona Sarkar just confirmed that the issue is now resolved and Windows Insiders shouldn’t face issues with Skip Ahead.
Yes, we fixed the rings issue on our side. If anyone is still seeing the "You've been removed from Skip Ahead" message, please ping me. There have been NO changes to your rings. https://t.co/NYjp1rcOcI
— Dona Sarkar (@donasarkar) December 8, 2017
Original Story: Back in August Microsoft introduced a new ring for Windows Insiders who wanted to test new but unstable features coming to next major release. Dubbed as “Skip Ahead”, the new ring allowed Windows Insiders to skip the current development branch and test the features of the next update. Everything was going as per the plan until yesterdat when Microsoft accidentally removed some Winows Insiders from Skip Ahead Ring.
Many Windows Insiders are now getting a notification saying their Windows Insider content settings was reverted and they have been downgraded to Windows Insider Fast Ring. Microsoft has acknowledged the issue and WDG head Dona Sarkar confirmed that the team is working hard to fix the issue.
#WindowsInsiders who are getting a strange “reverted Insiders settings” notification: I’m looking into it. Back with news soon. ??
— Dona Sarkar (@donasarkar) December 7, 2017
Meanwhile the official Windows Insiders Twitter account tweeted that they have found the issue and the fix is been coded by the team.
And good news! Root cause identified and a quick fix is actively being coded. Will keep everyone posted!
— Windows Insider Program (@windowsinsider) December 7, 2017
Windows Insiders should expect a quick fix soon which will fix the issue and let them switch back to “Skip Ahead”. Currently the team hasn’t shared why this issue happened and if there’s any temporary workaround for the same but we hope that Microsoft will push out a fix soon. Until then, let us know if you’re facing this issue in the comments section below.
User forum
0 messages