Jump to content

Recommended Posts

Posted
I have seen people confirm it's the same iso as the one added to MSDN today so it does appear to be valid.

The ISOs are definitely identical to the ones found on MSDN.

 

[b]Win10_1511_EnglishInternational_x64.iso[/b] [color="#FF0000"][b]=[/b][/color] [b]en-gb_windows_10_multiple_editions_version_1511_x64_dvd_7223718.iso[/b]
SHA-1: 250F8FF043CEB395F95CEE6120EFC323F69E7F8D

 

[b]Win10_1511_EnglishInternational_x32.iso[/b] [color="#FF0000"][b]=[/b][/color] [b]en-gb_windows_10_multiple_editions_version_1511_x86_dvd_7223719.iso[/b]
SHA-1: 9171EE8D0AA16BB50C57C45CE24F3EFE75D3DB8B

 

[b]Win10_1511_English_x64.iso[/b] [color="#FF0000"][b]=[/b][/color] [b]en_windows_10_multiple_editions_version_1511_x64_dvd_7223712.iso[/b]
SHA-1: 875EC108288B9F581E5D8099CF0EDB79F0F3E483

 

[b]Win10_1511_English_x32.iso[/b] [color="#FF0000"][b]=[/b][/color] [b]en_windows_10_multiple_editions_version_1511_x86_dvd_7223716.iso[/b]
SHA-1: 5D406D89656F8548FD0F410BD66DE59BE05B081B

 

Left = Tech bench / Right = MSDN

  • Thanks 1
Posted
The Media Creation Tool has also been updated. It will download ISOs of build 10586.

Not any more! :rolleyes:

 

Microsoft suddenly decides not to offer Windows 10 November update via Media Creation Tool

 

Things got very confusing today, as Microsoft suddenly - without warning or explanation - appeared to pull the Windows 10 'November update' that it released just over a week ago.

 

As a result, the Media Creation Tool, which had allowed users to download ISOs of the update (known also as Version 1511/Build 10586), suddenly stopped offering the new version, instead reverting to installations of build 10240 - the original public release of Windows 10, which came out back in July. The company also updated its notes for the Tool, stating that "these downloads cannot be used to update Windows 10 PCs to the November update (Version 1511)".

 

Bizarrely, despite Microsoft previously recommending the Tool to users who wished to install version 1511, it now says that that will no longer be an option.

 

Only after ZDNet's Ed Bott approached the company to ask for some sort of explanation did it offer the following statement:

 

The November update was originally available via the MCT tool, but we've decided that future installs should be through Windows Update. People can still download Windows 10 using the MCT tool if they wish. The November update will be delivered via Windows Update.

 

At least the ISOs are still available via the Tech Bench webpage (for the time being at least).

Posted
At least the ISOs are still available via the Tech Bench webpage (for the time being at least).

 

I have heard they are gone now too. Something is going on.

Posted
Quite annoying. Downloaded the tool and the whole ISO through it last night trying to fix an issue with a laptop, only to then notice this change. The staged updates going out will lead to some confusion and dissatisfaction anyway. Glad I haven't deployed it at all yet!
Posted (edited)
Downloaded the tool and the whole ISO through it last night trying to fix an issue with a laptop, only to then notice this change.

If you have previously downloaded the Media Creation Tool between 12th and 20th November it is still possible to download build 10586 (1511) ISOs with the tool. The SHA-1 checksum of the EXE is: 58F4C0735E23F318C8CADE916BCE44D254088E80.

 

I just tried it myself since I have a copy in my Downloads folder and the ISO was definitely the latest.

Edited by Arthur
Posted

Grrrrr

 

Bought an SSD to upgrade my son's laptop a couple of weeks ago. Thought I'd wait until the update so I could do a nice clean install. Downloaded from the media creation tool last night at 10pm.

 

Thanks for that Microsoft.

Posted
Something is going on.

There might be a bug in the installer. Hopefully Microsoft can fix it and make new ISOs available again?

 

http://vgy.me/BODoY8.png

 

Installing build 10240 and then downloading a 3GB+ update through Windows Update isn't going to be a much fun.

Posted

The ISOs are back!

 

Windows 10 November update was pulled for forgetting privacy settings; it’s now back

 

The mystery behind the removal of the Windows 10 November Update, version 1511, has been revealed. Last week Microsoft received reports that, when upgrading from the Windows 10 July release to the November update, four privacy-related settings were getting reset to their default values. Concerned that there might be a significant problem, Microsoft removed the November Update from Windows Update for existing Windows 10 users and also removed the updated Media Creation Tool used to create install media.

 

When upgrading from the initial Windows 10 release to the new version, four settings (whether to allow apps to use a unique advertiser ID, which apps are allowed to run in the background, whether Smartscreen Web filtering is enabled, and whether settings sync between devices) were reverted to their defaults, as if a fresh Windows installation had been performed. While for most users this made no difference, for those who'd disabled those features previously, the upgrade would silently revert those choices.

 

Oddly, upgrading from Windows 7 or 8 to Windows 10 wasn't affected, and the November Update was still being rolled out over Windows Update to people upgrading from those operating systems. Only those already on Windows 10 were affected.

 

Microsoft has now fixed the upgrade/installation process to properly preserve these settings, and the November Update has once more been made available to Windows 10 users through Windows Update. The updated Media Creation Tool has also been restored, re-enabling clean installs of version 1511. The company has also published a knowledge-base article describing the issue and which settings are affected, so any Windows 10 users who have already installed the November Update can double-check their settings and re-establish their preference if necessary.

 

In light of some of the other bugs that have been found in the November update, it seems a little surprising that Microsoft would pull it for something that seems so minor. However, the company has been under fire for privacy issues around Windows 10; this kind of vigorous reaction to even a minor privacy concern feels like an attempt to try to restore some of the lost trust and demonstrate that the company really does care about privacy.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...