Why Microsoft pulled the Windows 10 v 1511 Threshold 2 release from its download page

Topic

New Reply

Looks like they’re making stuff up as they go along.Again.InfoWorld Woody on Windows.
[See the full post at: Why Microsoft pulled the Windows 10 v 1511 Threshold 2 release from its download page]

Reply | Quote

Replies

I think the Bitlocker snafu is a more likely cause: http://www.neowin.net/news/issues-in-windows-10-november-update-prevent-bitlocker-encryption-from-being-enabled

The Home to Pro with a Windows 8 key would be fairly rare and has an easy workaround (Windows 10 Pro default key to upgrade, then Windows 8 Pro key to activate).

But with clean install of 10586 now gone, hasn’t clean install with Windows 7/8 keys also gone away again?

Reply | Quote

Microsoft is assuming that thw Windows Update route always works. I tried three times, unsuccessfully, to install Threshold 2. It would always stop at about 40-50%. I didn’t have an SD card installed on my laptop so the main work around didn’t even apply. The only way I got it to install was to use the MCT.

Reply | Quote

You’re kidding, right? I didn’t think so. On a previous thread I said I was thinking about making the leap to Apple. Well … Change ‘thinking about’ to ‘planning’. There’s plenty of time to get it right. I guess Windows 7 will be around for a while. I will allow no more updates from Microsoft while I spend a few years getting all my application ducks lined up for the switch. So long Microsoft – and good luck!

Reply | Quote

@b –

Very good question. I don’t have an answer

Reply | Quote

If I had to guess at the truth of the matter, I’d be more inclined to think that MS was losing control with the Win7/Win8 key validation thing and there was a possibility on not-so-genuine “genuine” copies. By pushing the Media Creation Tool back to Build 10240 Release, the validation in done on the computer before the User can upgrade to the current usable Build.

Reply | Quote

I had a Media Creation Tool (MCT) that I downloaded in July and was curious what build I would get. I can’t tell from the ISO file. It turns out the MCT not only downloaded the ISO file but also over 6 Gb of files placed in the $Windows.~WS (hidden) and $WINDOWS.~BT folders.I’ve not seen mention of that anywhere. Setup build is 10240 in the $Windows.~WS folder.

Reply | Quote

@Tom –

They’re two independent actions. When you downloaded the MCT, you created a USB, yes? Right-click on Setup, choose Properties, and take a look at the version number.

Reply | Quote

@Woody –

I didn’t create a USB. The MCT gave me the option to save an ISO file, and I saved the ISO file to the hard disk. In the end, I had a 3+ Gb ISO file and the folders that I mentioned above.

I have no intention of installing Windows 10 on my Windows 7 system. I got rid of everything the MCT downloaded and ran a system restore just in case there were other changes. Call me paranoid. 😉

Reply | Quote

Possible scenario — the download servers are maybe being overloaded with people jumping the upgrade gun on the planned staged rollout?

Traffic control would be a plausible and non-malicious explanation. Microsoft may not want to let people know its servers are this vulnerable to overload in the event of a DDoS attack or a big MS rollup update which might also need to be staged to prevent such overloads?

Possibly also another reason MS wants everyone to use the Torrent-style Windows 10 Networked Updates scheme.

Just a thought — probably could be confirmed or denied through MS back channels if one were so inclined.

Reply | Quote

@woody: Looks like Microsoft reversed course and recently restored the Windows 10 v1511 TH2 downloads. See this ZDNet article:
http://www.zdnet.com/article/microsoft-reverses-course-restores-downloads-of-windows-10-november-update/

Users can now use the Media Creation Tool to create the Win10 v1511 ISO images again.

Reply | Quote

Update to my most recent Comment here:

I may have hit the nail on the head, but Microsoft seems to want us to believe differently:

http://www.zdnet.com/article/microsoft-reverses-course-restores-downloads-of-windows-10-november-update/#ftag=YHFb1d24ec

“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.”

In other words, privacy and other Settings may have been getting changed by the Fall Update.

Anyone actually see those changes after installing the Update through the MCT or ISO method?

Reply | Quote

I would have had the 1511 build before they pulled it, but the media would not install from the USB stick or from the hard drive. I checked back the following weekend to download the ISO, and the update had been pulled.

I have capped data on Verizon and downloaded the 1511 build elsewhere on my nine-year-old Dell Inspiron with 2GB of RAM via the Upgrade Now link. Build 1511 cuts the basline RAM usage to 500 Mb where it was up to 1.4 Gb of 2 Gb on the RTM build. The machine runs better on Windows 10 1511 than it did on Vista, Win 7 or Win 8.1.

I still do not buy Microsft’s explanation that four privacy settings got changed and they were then forced to pull the upgrade. I think activation issues, BitLocker and installation failures were among the causes of the build being pulled from circulation.

Reply | Quote

@Tom If you downloaded the ISO and not created the USB installation media, you can either mount the ISO on Windows 10 which I think is possible and look inside or use a third-party tool like 7-zip to open the ISO and look at the date of the files.
If the date of most files is 30 October, then you have 1511, otherwise for a date around July you have 10240 installation files.

Reply | Quote

@Tom,

Here’s how to determine the version of your Windows .ISO file:

http://www.waynezim.com/2012/10/how-to-determine-the-version-of-your-windows-iso-file

Reply | Quote

I wouldn’t doubt for a second that they are!!!!

Reply | Quote

This is of interest. The download for Windows 10 version 1551 is back online http://www.computerworld.com/article/3008070/microsoft-windows/windows-10-1511-mct-download-itbwcw.html

Reply | Quote

1. First MS said that they pulled the MCT because there was Windows 8 embedded keys and people were getting Home even when they were entitled to Pro.

2. Next, they said they pulled it because the company had decided to deliver 1511 only through Windows Update.

3. Next they said they pulled it because it was resetting some people’s privacy settings (but it has been doing this to me with EVERY new build since Oct 2014).

OK, which story do YOU believe?. 1, 2, 3, none of the above

Reply | Quote

@PKCano –

Sounds like grist for a good article on Monday….

Reply | Quote

Hi Woody, Was using 8.1 had a message stating upgrade was ready so upgraded (although had intended to wait until next year) on 14-11-15 No problems with download and now have win 10 1511 10586.14 after a further update. Info on Version etc: can be found in win 10 -Settings-System-About.

Reply | Quote

@ch100, @Jim – the files were from July, so definitely not the 1511 build.

Reply | Quote

As of sometime this evening while I was at dinner (1715-1754) this appeared on my computer
” Upgrade to Windows 10 Home, version 1511, 10586″
The metered connection is still working because I got a message that the update could not be completed.
Is this the same thing they pulled earlier in the month?

Reply | Quote

I don’t know which story to believe. Hmm.

Reply | Quote

@Jim –

The patch has since been re-released. Not enough results in yet on the new version, but so far it looks pretty clean.

Reply | Quote