Windows 10: Microsoft has pulled the Windows 10 November Update

They are responses to two different replies. Microsoft broke a promise (albeit inadvertently) concerning the Windows 10 giveaway. They have acted so as not to keep breaking it. The giveaway expires in July and so does the promise.

 

How has MS broken any promise? And how can you say that the rollback will not continue to work now or in the future? All that's occurred it MS has dropped one way of getting the update, direct download of the ISO. And I don't see how that would effect anything other than using an old WIn7/WIn8 key to activate the OS.

 

Microsoft promised that those who wanted to try Windows 10 via the Get Windows 10 giveaway program could revert to their old OS for 30 days. That is what Microsoft broke. The November Update changed the "previous Windows version" from their old OS to Windows 10 build 10240 thus preventing a reversion to the old OS regardless of how many days they had left to revert. The rollback works, but what the user is rolling back to has changed without the user having any warning. Because of the change to Windows Update as the only path for the November Update, new users have their 30 days to decide intact, but users who have already upgraded to the November Update and still had days left to decide to return to a legacy OS are out of luck. As far as the legacy product key is concerned, how can you leverage that when the only iso available for download doesn't support the feature? The feature doesn't come into play during the November Update download from Windows Update because that is an upgrade, not a clean install. Catch 22.

 

No they haven't. If you have the new build on you PC and you want to go back to 10240 what's stopping anyone? Seriously, you're overacting to this and you are not basing any of these statements on any facts posted my MS.

Just what's to stop someone from going from the new build(10586) back to 10240? Assuming they have the windows.old in tact and days left on the rollback?

 

Dude, you can revert back to your old OS any time you want, even after 30 days. The 30 days is just how long MS retains the Windows.old directory, for an automatic rollback. You can still re-install your old OS any time you want.

 

Builds are not version boundaries. There are dozens of builds in the same version. What triggered the concern was the change from Windows version 10 to Windows version 1511. 1511 is not a build. It is a version of Windows in the same way a new service pack changed Windows 7 to Windows 7 Sp1. Different versions. You can go back to 10240 from build 10576 without losing apps but you can't go back to 10240 from 10586 without losing apps because you have crossed a version boundary. The software won't let you. You are free to do it but your options have changed.

As far as the windows.old file is concerned, of course it would be 10240. But that is the problem. Prior to doing the November Update, the windows.old file wasn't for 10240 for users recently taking advantage of the Get Windows 10 offer. The windows.old file was for the legacy OS. And that is exactly the issue here. You have hit the nail on the head. The recent Windows 10 adopter has lost his chance to revert to the legacy OS. Of course he can use a system backup...if he made one.

 

We all have the iso's from every Build, we can rollback ourselves anytime! *Wink

 

Never mind..

 

Thank God for that! I use mine mostly for repair installs. The pre-10240 ones made great beer coasters. *Party

 

Well pulling it is plain stupid. The update through Windows Update failed for me. It would download successfully but wouldn't install - and with no error. The only ways I was able to update was with the media creation tool.

Smart thinking MS.