Windows 10 1909 Features On Demand Iso Download

Posted on by admin
  • Download Windows 10 1909 ISO after May 2020 Update. Open Rufus website. Under the “Download” section, click the link to download the latest version. Double-click the executable to launch the tool. Click the Settings button (third button from left) a the bottom of the page.
  • RSAT Tools missing after 1909 update & not in FODs or 'Add a Feature'. On 2 machines this month, one imaged to the latest 1909 & one updated to the latest 1909, RSAT Tools were missing after a subsequent 1909 update more than a week later & is not showing up in FODs or 'Add a Feature.' I could understand this if the method of update was the.

I just logged in to Volume Licensing Service Center and clicked on Windows to filter it down, and it's still there (Windows 10 Features On Demand). I downloaded both 1809 and 1903 last week. There is a note that says 1903 is compatible with 1909 media. Sep 14, 2021 For offline RSAT installation, you need to download the FoD ISO image for your Windows 10 build from your personal section on the Microsoft MSDN / Volume Licensing Service Center (VLSC). The image is named something like this: Windows 10 Features on Demand, version 1903. Windows 10 comes with a lot of additional options to install, which are not part of the 'local' installationmedia. That means things like e.g. The OpenSSH Server component. These options are called 'Features on Demand' (FoD) and do need either an active internet connection to download and install, or a specializied FoD ISO which you only can.


Microsoft Features on Demand

Features on Demand (FODs) are Windows feature packages that can be added at any time to Windows 10 or Windows Server 2019. They are distributed as .cab files on the Feature on Demand ISO and you can use Deployment Image Servicing & Management (DISM) to add a FOD to a Windows image. There are 2 types of Features on Demand

  • FOD's without satellite packages: Comprise features with all language resources packaged into the same package. These FODs are distributed as a single .cab file.
  • FODs with satellite packages: Language-neutral FODs that have language and/or architecture resources in separate packages (satellites). These FODs are distributed as a set of several .cab files, but are installed by specifying a single 'capability name'.

Some FODs come preinstalled with Windows 10 or Windows Server 2019. You can also add additional FODs to support additional hardware features or enable certain use cases. The following Features on Demand come preinstalled, and have no satellite packages

  • Internet Explorer 11
  • Math Recognizer
  • OneSync
  • OpenSSH Client
  • Quick Assist

The following FODs are not preinstalled but are recommended to be preinstalled to enable certain scenarios

  • .NET Framework
  • Mixed Reality
  • Retail Demo Experience RDX
  • Server Core App Compatibility

The following FODs are not preinstalled

  • Accessibility Braille
  • OneCore Developer Mode
  • Graphics DirectX
  • WebDriver
  • MSIX Packaging Tool Driver
  • RAS Connection Manager Administration Kit (CMAK)
  • OpenSSH Server
  • Enterprise Cloud Print / Mopria Cloud Service
  • Remote server administration tools (RSAT)
  • Windows Storage Management
  • XPS Viewer

Discovery and Normalization of FOD

FOD Products will still continue to be captured into Technopedia along with Support Policies and Lifecycle dates as long as Microsoft still allows the Products to be downloaded separately. For example RSAT can be downloaded separately from the official website here and will show up in ‘Uninstall or change a program’. Note from the screenshot below this is where we could see the ‘Publisher’, ‘Name’ and ‘Version’ data which is typical for what we discover for Add/Remove evidences.

However, if the Product is downloaded as a FOD and installed using DISM then it only shows up in the ‘Turn Windows Features On or Off’ list. In this scenario, currently it is not possible to discover the ‘Publisher’, ‘Name’ and ‘Version’ data evidence, since DSIM requires Administrator privileges, and extractors do not have the capability to run Command line arguments since the versioning of RSAT is not available for Discovery when installed and activated as a FOD, it is not possible to capture lifecycle EOL/Obsolete dates.

Download Features On Demand

In certain circumstances, customers discovered data will present a FOD along with the OS installed e.g.

Note that the versioning of the FOD is not available from Discovery. To accommodate this, Technopedia will capture FOD titles, when they meet the S/W eligibility criteria with Versions based on the specific OS in which it is known to be installed an activated. The FOD lifecycle dates will piggyback on the lifecycle dates of that Windows OS version as well. For example, RSAT would be captured as follows:

Windows 10 1909 Features On Demand Iso Download Windows 10

Anyone testing/playing with W10 1909 yet?
When attempting to deploy the image with .NET3.5 pre-configured I am getting the following error:
The task sequence execution engine failed executing the action (DotNET_3.5) in the group (Setup Operating System) with the error code 2148468767
Action output: ... MSPKG$/TAP00174/sccm?/InstallNetFx3.ps1 to C:_SMSTaskSequencePackagesTAP00174InstallNetFx3.ps1
Downloading file /SMS_DP_SMSPKG$/TAP00174/sccm?/ range 0-72729052
Downloaded file from http://SERVERNAME.DOMAIN:80/ to C:_SMSTaskSequencePackagesTAP00174microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cb
VerifyContentHash: Hash algorithm is 32780
Content successfully downloaded at C:_SMSTaskSequencePackagesTAP00174.
Resolved source to 'C:_SMSTaskSequencePackagesTAP00174'
Command line for extension .exe is '%1' %*
Set command line: Run command line
Working dir 'C:_SMSTaskSequencePackagesTAP00174'
Executing command line: Run command line with options (0, 4)
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18363.418
Enabling feature(s)
I am using the same file / package / code from my 1809 and 1903 Deployments and those work without an issue.
I have verified that the cab file name has not changed between 1809/1903/1909.
Even trying to install .NET 3.5 on 1909 in the OS via System Center after the OS boots fails with this error:
Contents of the InstallNetFx3.ps1 file referenced above.
$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All