14 DAY TRIAL // Microsoft issued a new patch for Windows 10 build 9926 users that brings a lot of improvements on computers running this particular version of the Technical Preview, including bug fixes that were already confirmed by the Redmond-based software vendor itself.
But what's more interesting is that, after deploying this particular patch, users are offered Windows 10 build 9932 via Windows Update, which has made many people believe that the company is already ready to ship a new version of the operating system, as promised last week.
Unfortunately for all these users, it was all caused by a bug in the new patch, which, according to Microsoft, tried to ship the new Windows 10 build 9932 to all users. In fact, it was only supposed to be offered to Microsoft employees for testing purposes, it explains.
“Yep, looks like this is on us – we’re exposing some build offers that we shouldn’t – sorry, only MSFT can get…Yup, you’re right. the KB exposed this. Don’t change your branch or you could fall off accidentally and not get next flight,” the company says in a statement.
New build coming soon
More details were posted by Gabe Aul, head of the Windows Insider Program, on Twitter shortly after the release of the patch and confirmed that it was all just a problem that actually “exposed internal settings” that were supposed to be available exclusively to Microsoft employees.
“The KB exposed this. Don't change your branch or you could fall off accidentally and not get next flight,” Aul posted.
And yet, there is already a new Windows 10 version in the pipeline for Windows Insiders, and Microsoft has said that it's set to arrive “soon,” although the company has refused to provide any other specifics.
It appears that the new build could launch together with the new Windows 10 for Phones preview that should be made available in early February, so expect even more improvements in the coming weeks.
In the meantime, don't forget to install today's patch to fix some of the bugs that were confirmed to exist in build 9926.
@SlasherKG Yup, you're right. the KB exposed this. Don't change your branch or you could fall off accidentally and not get next flight.
— Gabriel Aul (@GabeAul) January 28, 2015
@Chris123NT @bdsams The KB we published at 4:00 exposed internal settings. Don't go DDOS the "Check Now" though - still MSFT only to install
— Gabriel Aul (@GabeAul) January 28, 2015