Softpedia >News >Microsoft >Windows
Softpedia Homepage   

The Good and Bad Parts of Microsoft’s Windows 10 Threshold 2 Blunder

Yep, as weird as it might sound, there’s a good part too

Nov 25, 2015 08:24 GMT  ·  By
The Windows 10 performance seems to be full of ups and downs these days
   The Windows 10 performance seems to be full of ups and downs these days

Microsoft removed Windows 10 Threshold 2 ISO download links during the weekend for no clear reason, and in a statement provided to us, the company has confirmed that such a decision was absolutely crucial because of a bug that affected privacy settings on Windows 10 devices.

Let’s start with Microsoft’s statement (emphasis is ours):

“Recently we learned of an issue that could have impacted an extremely small number of people who had already installed Windows 10 and applied the November update. Once these customers installed the November update, a few of their settings preferences may have inadvertently not been retained. For these customers, we will restore their settings over the coming days and we apologize for the inconvenience. We worked to resolve the issue as quickly as possible - it will not impact future installs of the November update, which is available today.”

The bad part

First of all, it’s pretty clear that the bad part is that such problems still take place. Microsoft promised to thoroughly test every single Windows 10 update before rolling it out, and given the fact that Threshold 2 is actually a pretty huge release, shipping it with bugs makes it twice as worse.

Then, there’s the privacy part. Not only had Threshold 2 a major bug that forced Microsoft to pull the ISOs completely, but it also impacted privacy settings, which have caused so much controversy since the release of Windows 10.

Microsoft has been accused of collecting users’ information after updating to Windows 10, and because of this bug, some settings that consumers changed on their PCs to prevent this from happening were automatically enabled to actually activate telemetry.

The good part

And yet, there’s a good part too. As weird as it might sound, Microsoft actually reacted really quickly this time and managed to fix the problem in approximately 48 hours, which is super-fast for the software giant, who usually needed one month to address a botched update.

Moreover, it offered an apology, which means that it’s very aware of the fact that users no longer admit such mistakes, and plans to fix the problems caused by the bug with future updates that will be specifically aimed at those running Threshold 2 already.

Obviously, this doesn’t necessarily mean that everyone should get over it and forget about Microsoft’s blunder. Redmond screwed things up once again, and it certainly deserves the criticism.