New
#1
I got lucky! I checked for new Builds all day and was told I was up to date! Whew!
A note about the unintentional release of builds June 1st, 2017
-
-
-
-
New #4
Glad I was too busy to pay attention yesterday. Never even thought about checking on my two test PCs. Dell Venue Pro 11 still at 16199, and so is the test desktop, too. Whew! Dodged a bullet?
Thanks for the heads-up, Brink!
--Ed--
-
New #5
my tablet which is running the stable build received an update with a strange name but refused to install (file not signed)
I wonder if it is this.
-
-
New #7
Kept trying to install on my 32bit Dell last night & still this morning. I'm on Release Preview ....
-
New #8
Update:
For those still being offered the update, this hack is working for many.
turn off wifi, set the time to 40 years in future & lmk what happensTweet
— Twitter API (@user) View on Twitter
Tweet
— Twitter API (@user) View on Twitter
-
-
New #9
This has plagued me today. Offered to clean install Ten on friends notebook and kept getting this error.
Strange Feature Update keeps appearing in x86 version. - Windows 10 Forums
This 'hack' should stop it on my main set up. Curiously all these systems were x86 installations. Its frustrating because it has all been time wasted wondering what the heck is going on.
(it strengthens the case that more user flexibility is needed over updates imo)
A note about the unintentional release of builds June 1st, 2017
Last Updated: 02 Jun 2017 at 21:51
Hello Windows Insiders!
Many of you discovered that earlier this afternoon, builds from some of our internal branches were accidentally released for PC and Mobile. This happened because an inadvertent deployment to the engineering system that controls which builds/which rings to push out to insiders. The team was quick to revert the deployment and put blocks in place to stop these builds from going out to more people. Our analysis shows only a small portion of folks got these builds. For those of you who received one of these builds on your devices – please read the following:
If you received this build (from RS_EDGE_CASE) on your PC: Please be aware that this build was never intended to go out to Windows Insiders and may include issues that impact usability of your PC – more so than the normal builds we give you. You can either sit tight and wait for us to publish a newer build to you or you can roll-back to the previous build via Settings > Update & security > Recovery. And check your Windows Insider Program settings.
NOTE: You have up to 10 days to roll-back and this will only work if you did not do Disk Cleanup to remove your previous Windows installation.
How to Go Back to Previous Version of Windows in Windows 10
If you received this build (from RS_IoT) on Mobile: This build will *not* install on your device. If you installed this build, your device will be stuck in a reboot loop and the only way to recover is to use the Windows Device Recovery Tool and re-flash. After re-flashing, you can join the Windows Insider Program again on your device and choose your ring and be back on the right update path.
If your device has downloaded this build but has not installed the build (you see either a “Install” or “Restart now” button under Phone update) – you will have to do a device reset via Settings > System > About (Do a backup via Settings > Update & security > Backup FIRST) and then check your Windows Insider Program settings to ensure you’re on the right ring.
If you are not a Windows Insider, your device may have seen one of these builds offered. However, these builds will not install on devices that are not joined to the Windows Insider Program (a.k.a. “retail”).
We apologize for this inconvenience and thank you for being a Windows Insider! We will keep you updated on when we plan to release new builds to you next week. We will not be releasing new builds to any of the rings this week.
Dona
Source: A note about the unintentional release of builds today - Windows Experience Blog
Quote
Related Discussions
