Unable to download 1511 10586

[Bluetooth]

Hi guys

 

Bit of a conundrum. I've just returned to work after being off sick a while, and im trying to update my machine which currently reports its version as 10 10240, i know there have been a lot of updates since November, and the update is listed in my windows updates, however, all i ever get, is "waiting to download" and the download never surpasses 0%

 

I've done the usual deleting of the software dist folder in c:\windows, that did bring me down a load of updates for office 2013, however i am still stuck with the update for 1511 10586 but i cannot download it, it just sits on 0% as mentioned.

 

Has anyone else experienced this?

 

I know i can download a newer ISO from the VLSC but i dont like the idea of having to do this each time a new windows version is released, thinking forward to a future deployment of 10.

 

10 Education 64 bit Build 10240

Edited February 12, 2016 by Bluetooth

[Michael]

Hi guys

 

Bit of a conundrum. I've just returned to work after being off sick a while, and im trying to update my machine which currently reports its version as 10 10240, i know there have been a lot of updates since November, and the update is listed in my windows updates, however, all i ever get, is "waiting to download" and the download never surpasses 0%

 

I've done the usual deleting of the software dist folder in c:\windows, that did bring me down a load of updates for office 2013, however i am still stuck with the update for 1511 10586 but i cannot download it, it just sits on 0% as mentioned.

 

Has anyone else experienced this?

 

I know i can download a newer ISO from the VLSC but i dont like the idea of having to do this each time a new windows version is released, thinking forward to a future deployment of 10.

 

10 Education 64 bit Build 10240

 

You don't have to upgrade to 10586 - Microsoft are supporting two branches - those on 10240 and those on 10586. 10586 is supposed to contain improvements, but it's nothing significant in my view.

 

Unfortunately you'll find that downloading new builds will be the way to go with Windows 10. Upgrading from 10240 > 10586 takes over an hour in most instances. It's quicker/easier to re-image and include other new components at the same time.

 

Also (for your reference), you cannot Sysprep a computer that has been updated from 10240 > 10586. The computer natively needs to be at 10586 and the only way to achieve this is to download the ISO and re-build a new image.

 

Unless Microsoft change/update their strategy, it'll be the same in future too for newer builds.

[sparkeh]

@Michael off the top of your head, do you know if new builds will come down via wsus? If so that's something to block :S

[Michael]

@Michael off the top of your head, do you know if new builds will come down via wsus? If so that's something to block :S

 

By default no - you have to enable Upgrades within WSUS, but you'll probably find you can only see this option with RSAT installed on Windows 10 and then opening the WSUS MMC.

 

As a general rule, your WSUS instance should be configured to deny all updates and only allow the updates you require putting you in full control.

[sparkeh]

By default no - you have to enable Upgrades within WSUS, but you'll probably find you can only see this option with RSAT installed on Windows 10 and then opening the WSUS MMC.

 

As a general rule, your WSUS instance should be configured to deny all updates and only allow the updates you require putting you in full control.

Hmm, we use SCCM and there isn't an 'upgrades' option. Need to do some looking into that.

 

Edit: Ah we are not running the required version for wsus for handling upgrades.

Edited February 12, 2016 by sparkeh

[Bluetooth]

So if we wanted to deploy a new build to say our entire site.. we'd have to reimage every machine?

 

Why is this taking place? isnt this a bit silly?

[Michael]

So if we wanted to deploy a new build to say our entire site.. we'd have to reimage every machine?

 

Why is this taking place? isnt this a bit silly?

 

You have two choices -

 

Deploy the new build via WSUS. The main issue being it's huge (2GB+) but more crucially, it typically takes over 1 hour to install. Not very realistic in many network configurations.

 

The alternative is to build a new/native 10586 image build from scratch and likewise do the same for future Windows 10 builds.

 

For example, all my domains are based on the original 10240 with the latest February 2016 update (at the time of writing).

 

I've looked at build 10586, but it offers no significant advantage/change, so I intend on skipping this build and looking at Redstone later in 2016.

 

I think you have to consider Windows builds a bit like Office versions. Again, all sites I support made the move from Office 2010 > Office 2016, skipping Office 2013 altogether. You have to weigh up the benefit to yourself and of course your end users.

[sparkeh]

I think you have to consider Windows builds a bit like Office versions. Again, all sites I support made the move from Office 2010 > Office 2016, skipping Office 2013 altogether. You have to weigh up the benefit to yourself and of course your end users.

But builds only supported for so long. Unless you upgrade to the latest build within 12 months you lose access to security updates.

[Michael]

But builds only supported for so long. Unless you upgrade to the latest build within 12 months you lose access to security updates.

 

You're absolutely right, but I'm pretty certain Microsoft will overlap Windows 10 Builds. It's not realistic to have some users on X build and others on Y build from a support perspective. Once Redstone is released, then in turn, I'll work through each site and upgrade them accordingly.

Edited February 22, 2016 by Michael

[Bluetooth]

You have two choices -

 

Deploy the new build via WSUS. The main issue being it's huge (2GB+) but more crucially, it typically takes over 1 hour to install. Not very realistic in many network configurations.

 

The alternative is to build a new/native 10586 image build from scratch and likewise do the same for future Windows 10 builds.

 

For example, all my domains are based on the original 10240 with the latest February 2016 update (at the time of writing).

 

I've looked at build 10586, but it offers no significant advantage/change, so I intend on skipping this build and looking at Redstone later in 2016.

 

I think you have to consider Windows builds a bit like Office versions. Again, all sites I support made the move from Office 2010 > Office 2016, skipping Office 2013 altogether. You have to weigh up the benefit to yourself and of course your end users.

 

I'm not following you, do you not have to have that build (1511 10586) and not 10240 to even get the other updates including the Feb 2016 update as well?

[Michael]

I'm not following you, do you not have to have that build (1511 10586) and not 10240 to even get the other updates including the Feb 2016 update as well?

 

No you don't need 10586 - Microsoft currently support both builds or branches as they're referred to.

 

You can get the February update for both 10240 and 10586 builds, but the KB numbers are different.

 

10240 = KB3135174

10586 = KB3135173

 

Once either of the above are installed, IE11 will read 11.0.28 as its version for example.

 

10586 essentially includes some improvements/fixes over 10240 but I found nothing that justified upgrading devices. The above are security fixes. I suspect Redstone released later this year will most probably include noticeable improvements to the end user.

[Bluetooth]

Well, after all my ranting and raving, and concerns over microsofts windows 10 build strategy, our machines finally started installing 1511 10586, for no reason what soever, no one was working on the issue, they just up and started installing yesterday... ive just finished the update process and im a little confused by it all as it doesnt make sense.

 

I shall chalk it down to good old Micro$oft.

 

Thanks for the comments guys, certainly given us a lot to think about Re our migration to windows 10, or if it will happen at all!

 

Thanks again

[Michael]

If you don't have WSUS in place, then all your devices will connect/download updates directly from Microsoft Update. If you don't have WSUS in place, I would recommend you look at it, as it puts you in full control what's deployed to your devices.