Windows 10: Insider preview set in GPO, found the issue and corrected, now machines are saying to...

Good Afternoon,


I am a new technical coordinator at a school. There was a setting in the WSUS GPO that was set to allow Insider Preview, I didn't catch this until it was too late. Multiple machines have downloaded the preview and are now getting expiration notices. What are my options for correcting this?

:)

 

Windows Insider Preview on a multi-boot machine

Wow, no one from MS or an MVP can answer this? Is the windows 10 insider preview on the small partition blocking my ability to upgrade win 8.1 on the same machine? By the way, absolutely none of the forced upgrade suggestions have worked and neither
did the ISO. Failed at 33%, then 37%.

 

Cant get out of Insider Preview Versions

Hi Alan,

Thank you for your response.

I suggest you to follow the below steps and check if it helps you.

• Go to the following website Windows Insider Program
• Sign In using the credentials that you used to sign up.
• At the top of the page, click the Leave Program tab.
• Confirm that you want to leave.

Note: This will only remove your participation in the Insiders Program.

The Automatic Feedback can only be stopped by
uninstalling the Windows 10 Technical Preview.

• Restart the machine.
• Sign out from the Microsoft Account and sign in again and check if it persists.

Keep us posted to help you better.

 

Windows 10 Insider Preview Build has never updated

I want to add this for anyone in the future that may come across this post.

I followed the advice of @Ramhound and the links he provided in the comments and created a new VM in Azure from the downloaded image of Build 14295, which was the closest available ISO build. I followed all the steps to connect my MS account to the VM for insider preivew. I changed my insider preview settings to Fast track. I even used my MS account to sign into the VM.

I checked the registry settings as suggested by this article and ensured everything there was correct. Even after all this, I still did not receive the 14316 build.

I diligently checked my machine multiple times per day. I manually checked for updates. I restarted the machine several times. I changed my settings to developer mode. Even after following all these steps, I still did not receive the build.

Finally! Today, after a week of waiting, I logged into the VM, and the build was there. I do not believe any of this extra work I did helped....but I did learn some stuff from this, so it was not a complete waste of time. I think I would have received the build if I would have just left my VM as it was and kept waiting.

tldr - From my experience, I think the best advice is to just be patient and wait. If you have waited a significant amount of time (2 weeks), then maybe look into the other solutions.