We have some portable devices with later builds of W10 1703 upwards and these will upgrade to 1903 via WSUS absolutely fine.

But the 1511 machines will not pull down the upgrade to 1903. If I run "usoclient startscan" it reports back that "Your device is up to date".WSUS console shows that the approved upgrade is applicable to the 1511 PC.

I have checked IIS & it already had a MIME type entry for .esd files. Exisiting entry was 'application/vnd.ms-cab-compressed'. Obviously this wasn't serving the files.So I have changed it to 'application/octet-stream' for testing purposes. Restarted IIS & WSUS service. No change to the 1511 client.

Is there anything else I should be looking at? I'm just about to finish for the day so any replies from me will be tomorrow.

If the systems are not reporting that they are needing the update, and they are reporting correctly, then you're probably best off using some other method to run the setup.exe file in unattended mode to upgrade those systems.

Is there only one Upgrade available to these 1511 PCs? I seem to recall an issue some really old versions like this had where if they had more than one OS upgrade available to them via WSUS - be it two different versions or even two different languages of the same version, they would get confused and ignore them and decide that there were no updates needed.

In the end for the few problem PC's like these we just did full rebuilds on them, or started the the upgrade manually via setup.exe.

In my understanding, the feature upgrade is actually an incremental update, which is intended to be upgraded for several nearby versions. That is to say, from 1511 to 1903, in this way, the span is too large.

Please consider observing the results of the self-reported version of the 1511 client in WSUS and approving the highest version of the upgrade it is prompted for, then stepping closer to version 1903.

Adam (AJ Tek)​ I have been reading through your WSUS articles (extremly handy, thanks!) & I had already changed the MIME type to application/octect-stream. I have approved the upgrades to a test group. I've determined that I need to appove the 1903 Business x64 en-gb & the Consumer x64 & x86 en-gb & en-us. So 5 in total. I've run "
C:\windows\system32>cscript slmgr.vbs -dli
" to help to choose. Our dekstop PC's were origianlly installed with Win8.1 Volume License Media then the free upgrade to Win 10. Running the slmgr.vbs script reports back VOLUME_MAK.

Nick-C​ as above, I have apporved a total of 5 upgrades, but the report viewer for the PC in question only reports back one is applicable. Maybe try declining all others apart from the Business x64 en-gb?

Yic Lv​ I understand what you mean about 1511 to 1903 is too large a jump. But not sure what you mean by "Please consider observing the results of the self-reported version of the 1511 client". Are you suggsting to approve all upgrades from 1603 through to 1903 and let the client decide which one to choose?

I'm going to try declining all but the relevant upgrade and try again.

If the systems are not reporting that they are needing the update, and they are reporting correctly, then you're probably best off using some other method to run the setup.exe file in unattended mode to upgrade those systems.

I am sorry that I did not express it clearly.I recommend that any upgrades be approved based on the needs of the client. That is, when the client completes its status report, it can be seen in the WSUS console that some clients "Needed" a version of the upgrade. At this point, you need to decide which version to upgrade to. Instead of approving when the client does not prompt "Needed".

KB4021702 -
This update includes new stability improvements for the update components in Windows 10, Version 1511. (not available in WSUS & also not listed in Windows Update Catalog)

KB4033631 -
This update includes diagnostic improvements for determining the
applicability of updates in Windows 10 Version 1703, Version 1607,
Version 1511, and Version 1507.
(not available in WSUS & also not listed in Windows Update Catalog)

KB3012973 - Which is the KB number used for all of the Feature Updates to 1903 & 1909 for all languages and and CPU architecture.

I installed PSWindowsUpdates from the Powershell Gallery. When checking against Microsoft Online using the command 'Get-WUList -MicrosoftUpdate' it lists the updates outlined above (along with a load of drivers). I installed
KB4023057,
KB4021702,
KB4033631
hoping that I would then be able to pull 1903 from WSUS.After a reboot and the updates installing, still nothing from WSUS. But checking again from MicrosoftUpdate the 1903 upgrade was available.

So it seems the only options available are to utilise PSWindowsUpdates on each PC to install directly from MicrosoftOnline or pull down the ISO and script the upgrades.

Another update on this in case someone else stubles across this thread.

As already stated 1511 will not find feature upgrades from WSUS.

1607 will pull them from WSUS.

PSWindowsUpdate does not seem to install a Feature Upgrade. Soemthing to do with the reboot interfers with this.I've tried manually from PowerShell on a local session. It prompted to reboot the machine instantly and it did just that. Just rebooted, no installation occured.

We had to script the 1511 updates from the ISO files. Everything on 1607 & above was upgraded via WSUS. Although some users had to initiate the install from Settings>Updates & Security>Windows Update.But happily we're 160 workstations now running 1909, last 20 or so just have to install the feature upgrade from WSUS.

Phew... Just in time for 2003 or 2004 whatever it is going to be. Hopefully that will be a smoother experience!