Sarkar says the hack is "working for many" and also that "it's worked for lots of people in the office and in the community".
This "happened because an inadvertent deployment to the engineering system that controls which builds/which rings to push out to insiders", she said. For desktop users, the problem is merely an annoyance; the build, taken from a development branch named "RS_EDGE_CASE", appears to work, broadly speaking, but "may include issues that impact usability of your PC". Sarkar adds that the said builds only made their way to a "small portion of folks" out of the large 500 million users running Windows 10 at the moment.
Although specific figures aren't being given, Sarkar said only a "small portion" of Windows Insiders received the rogue builds of Windows. Also, it won't be releasing any new build this week. Let's just hope that whatever bugbear caused this doesn't see a repeat episode - as things could certainly have been a lot worse for PC users.
Donald Trump Clashes With World Leaders at G7 Summit
The two leaders also found common ground on terrorism, following the attack on a pop concert in Manchester that killed 22 people. Among the agenda items the Italian presidency has had to capitulate on is a substantial reference to tackling climate change.
Dona Sarkar, head of the Windows Insider program, sincerely confirmed the unwanted release of BUILD 16212 in a tweet and urged users to refrain from updating their PCs and phones. If you have not installed this build yet but downloaded you need to do a hard reset to get rid of it. Non-insiders may see this build but won't be able to install. Microsoft teased the release of some new previews in the near future, and then an unfinished build (16212) was accidentally pushed out to both PCs and smartphones (actually, several different builds were apparently released for mobiles).
"We apologize for this inconvenience and thank you for being a Windows Insider!". The accidental release of Windows 10 Build 16212 has created buzz among Windows Phone users as if you install the build on your phone, it will get stuck in a reboot loop and you will need to flash the phone. The fix involves using the Windows Device Recovery Tool and re-flashing your handset. Although it will be buggier than the builds Insiders in the Fast Ring normally receive, you can keep it installed on your system according to Microsoft and it will be updated once a newer build is released.