Скачать net framework 3 5 windows server 2016

Большинство современных приложений Windows требуют наличия установленного .NET Framework. Например, в Windows 11/10 и Windows Server 2022/2019 по умолчанию уже установлена версия NET Framework 4.8. Однако некоторые старые приложения требуют наличия установленного .NET Framework 3.5, 2.0 или даже 1.0.

В этой статье мы рассмотрим, как установить .NET 3.5 в Windows 11/10 и Windows Server 2022/2019/2016.

Установка .NET Framework 3.5 в Windows 11 и 10

Проверьте, что .NET Framework 3.5 (включает в себя .NET 2.0 и 3.0) не установлен на вашем компьютере. Для этого, откройте консоль PowerShell с правами администратора и выполните команду:

Get-WindowsCapability -Online -Name NetFx3~~~~


В нашем случае .NET 3.5 не установлен (
State=NotPresent
).

В Windows 10/11 вы можете установить .Net Framework из панели Turn Windows Features on or off:

1. Выполните команду
   optionalfeatures.exe
   ;
2. В списке компонентов выберите .NET Framework 3.5 (includes .NET 2.0 and 3.0), нажмите ОК;
3. Если на вашем компьютере есть доступ в Интернет, в следующем окне выберите Let Windows Update download the files for you;
4. 
5. Windows скачает и установить последнюю версию компонента .NET Framework 3.5 с серверов Microsoft Update.

Если ваш компьютер не подключен к интернету или находится в изолированной сети, то при установке .NET 3.5 появится ошибка:

Windows couldn’t complete the requested changes.
The changes couldn’t be completed. Please reboot your computer and try again.
Error code: 0x8024402C

В этом случае вы можете вручную установить компоненты NET 3.5 с вашего установочного образа (диска) Windows. Для этого вам понадобится установочная USB флешка или файл с ISO образом вашей версии Windows (как проверить версию Windows в ISO образе):

1. Подключите ваш носитель с ставочным образом Windows к компьютеру. В моем случае у меня есть файл Windows11-22h2.iso. Щелкните по файлы и выберите Mount, чтобы смонтировать образ в виртуальный DVD привод (или воспользуйтесь командой PowerShell:
   Mount-DiskImage -ImagePath "C:distrWindows11-22h2.iso"
   );
2. В моем случае виртуальному приводу с образом была назначена буква диска E: (мы будем использовать эту букву в следующих командах);
3. Чтобы установить .Net 3.5 из файлов компонентов на установочном диске выполните команду:
   DISM /online /enable-feature /featurename:NetFX3 /All /Source:E:sourcessxs /LimitAccess
   
   Или (аналогичная PowerShell команда):
   Add-WindowsCapability -Online -Name NetFx3~~~~ -Source E:SourcesSxS

Чтобы проверить, что .NET Framework успешно установлен, выполните команду:

Get-WindowsCapability -Online -Name NetFx3~~~~

Name         : NetFX3~~~~
State        : Installed
DisplayName  : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
Description  : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
DownloadSize : 72822163
InstallSize  : 496836410

Выведите список версий .NET Framework, которые установлены на вашем компьютере:

Get-ChildItem 'HKLM:SOFTWAREMicrosoftNET Framework SetupNDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match ‘^(?!S)p{L}’} | Select PSChildName, version

[/alert]

Как установить .NET 3.5 в Windows Server 2022/2019/2016?

В Windows Server 2022,2019,2016 и 2012 R2 вы можете установить NET Framefork 3.5 несколькими способам:

• ерез Server Manager (Add roles and features -> Features -> .NET Framework 3.5 Features -> .NET Framework 3.5 (includes .NET 2.0 and 3.0 );
• С помощью DISM:
  DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
• С помощью PowerShell:
  Install-WindowsFeature NET-Framework-Core

При этом установочные файлы .NET 3.5 для вашей версии Windows Server будут загружены с серверов Windows Update. Чтобы сработал этот метод установки нужно убедиться:

1. Ваш Windows Server должен иметь прямой доступ в Интернет. Настройки прокси-сервера и файервола не должны ограничивать доступ к серверам Windows Update.
2. Хост не должен быть настроен на получения обновлений с локального WSUS сервера (проверьте настройки обновлений Windows в групповых политиках или напрямую в реестре);

   Проверьте значение параметра UseWUServer в реестре:
   Get-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU" -Name "UseWUServer" | select -ExpandProperty UseWUServer
   Если значение параметра равно 1, значить ваш хост будет пытаться получить обновления с локального WSUS сервера. В этом случае при установке .NET 3.5 появится ошибка 0x800F0954. Измените значение параметра на 0 или удалите его, чтобы подключиться напрямую к серверам обновлений Windows Update.

Если ваш сервер имеет доступ в Интернет, но настроен на получение обновлений со WSUS, при устапновке NET Framework появится ошибка 0x800f081f.

Решение: установить .Net 3.5 онлайн с серверов Microsoft и игнорировать локальный WSUS:

• Экспортируйте в reg файл текущие настройки Windows Update в ветке HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate (
  reg export HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate c:WindowsUpdateRegFile.reg
  )
• Удалите данную ветку (
  Remove-Item -Path HKLM:SoftwarePoliciesMicrosoftWindowsWindowsUpdate -Recurse
  ) и перезапустите службу:
  net stop wuauserv & net start wuauserv
• Запустите установку .Net из Интернета:
  DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
• После окончания установки верните настройки WU, импортировав reg файл (
  Reg import c:WindowsUpdateRegFile.reg
  ) и еще раз перезапустите службу Windows Update

Если с вашего сервера нет прямого доступа в Интернет, то при попытке установить .NET 3.5 в Windows Server через консоль Server Manager появится ошибка 0x800F081F (The source files could not be found), 0x800F0950, 0x8024402c, 0x800F0906 или 0x800F0907 (в зависимости от версии Windows Server).

Хотя .NET Framework 3.5 присутствует в списке компонентов Windows Server 2022/2019/2016/2012R2, на самом деле его бинарные файлы в хранилище компонентов Windows отсутствуют (концепция Features on Demand). Это сделано, чтобы уменьшить размер образа операционной системы на диске. Вы можете проверить наличие.NET Framework 3.5 в локальном хранилище компонентов Windows Server с помощью команды:

Get-WindowsFeature *Framework*

Как вы видите статус компонента
NET-Framework-Core
– Removed.

Для установки NET-Framework-Core вам потребуется дистрибутив с вашей версией Windows Server в виде ISO файла, или в распакованном виде в сетевой папке. Смонтируйте ISO образ с дистрибутивом в отдельный виртуальный диск (например, диск D:).

Теперь вы можете установить .Net Framework 3.5 с помощью графической консоли Server Manager:

Установить компонент .Net 3.5 можно из графической консоли Server Manager. Для этого выберите компонент .Net Framework 3.5 Features, но, перед тем, как нажать кнопку Install, нажмите небольшую ссылку внизу мастера — Specify an alternative source path.

1. Для этого выберите компонент .Net Framework5 Features. Перед тем, как нажать кнопку Install, нажмите на ссылку Specify an alternative source path внизу;
2. Укажите путь к хранилищу компонентов (SXS) дистрибутива Windows Server. Если вы смонтировали дистрибутив в виртуальный привод, это может быть путь
   D:sourcessxs
   . Также это может быть сетевая папка, куда вы предварительно скопировали дистрибутив (например,
   \server1distrws2022sourcessxs
   ). Нажмите ОК.

Гораздо проще установить компонент Net Framework 3.5 Features из командной строки или консоли PowerShell, запущенной с правами администратора. Просто выполните команду:

Dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:D:sourcessxs /LimitAccess

Если вы хотите установить компонент Windows Server с помощью PowerShell, воспользуйтесь командой Add-WindowsFeature:

Add-WindowsFeature NET-Framework-Core -Source d:sourcessxs

После завершения установки компонента, перезагрузка сервера не требуется.

Также вы можете вручную скопировать 2 cab файла
microsoft-windows-netfx3...
из каталога sourcessxs вашего дистрибутива. В этом случае для установки .Net 3.5 достаточно выоплнить команду:

dism /online /Add-Package /PackagePath:C:installnet35microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab.

Настройка параметров офлайн установка .Net 3.5 помощью GPO

С помощью групповой политики Specify settings for optional component installation and component repair (находится в разделе GPO Computer Configuration -> Administrative Templates -> System) можно настроить особые параметры установки компонентов Windows из локального источника или Windows Update даже при использовании WSUS.

На отдельностоящем компьютере вы можете включить этот параметр политики с помощью редактора локальной GPO (gpedit.msc). В среде Active Directory вы можете создать политику для всех компьютеров/серверов с помощью консоли GPMC.

Здесь можно указать, что при установки или восстановлении компонентов Windows необходимо всегда загружать файлы из Интернета с серверов Windows Update вместо локального WSUS (опция Download repair content and optional features directly from Windows Update instead of Windows Server Update Services — WSUS).

Также можно указать путь к каталогу с компонентами Windows Server (или wim файлу), который нужно использовать при офлайн установке (указывается в параметр Alternate source file path). Вы можете указать:

• • Путь к сетевой папке в UNC формате (
    \serverdistrws2016sxs
    ) (здесь можно указать несколько UNC путей через точки с запятой:
    \srv1ws22sxs;\fs01ws22sxs;\fs3sxs

• Также допустимо указывать WIM файл в качестве источника:
  WIM:\srv1distrws2016install.wim:2
  (в этом случае
  2
  – это индекс образа вашей редакции Windows Server в WIM файле. Список доступных редакций в файле можно вывести так:
  DISM /Get-WimInfo /WimFile:"\serverdistrws2016install.wim"
  )

Для разных версий Windows Server нужно использовать разные источники с каталогом SXS. Если в вашей сети есть несколько версии Windows Server, нужно создать отдельные GPO с разными UNC путями к сетевой папке с SXS. Чтобы GPO применялась только к хостам с определенными версиями Windows Server, можно использовать WMI фильтры групповых политик.

Lots of applications require the .NET Framework 3.5 installed on your Windows Server 2016 and later. By default, the .NET Framework 3.5 is not installed on these Operating Systems and must be installed manually by an administrator. You can install the .NET Framework 3.5 also on Windows Server 2022 by following the steps described in this blog post.

There are multiple ways to install the .NET Framework 3.5 feature on Windows Server 2016 and later:

• By using the “Add Roles and Features” Wizard of the Windows Server Manager
• By using PowerShell
• By using the DISM tool
• By using the Group Policy Feature on Demand setting

In this blog post I will focus on just two of them: The installation using the Windows Server Manager and the installation via the Windows PowerShell.

If you are using Windows 10, Windows Server 2016, or Windows Server 2019, Microsoft recommends installing .NET Framework 3.5 through the control panel or the methods listed above.

You can find more information about this installation within the official documentation published by Microsoft: Microsoft .NET Framework 3.5 Deployment Considerations.

Prerequisites

To install the .NET Framework on your system running Windows Server 2016 and later you need the Windows Server installation media that was used to setup the server. Within this blog post, we will need the contents from the subfolder [ISO]:SourcesSxS on the installation media.

If you are using a Windows Server installation ISO, you can simply mount the ISO file on your server or extract the contents of the [ISO]:SourcesSxS to a local directory, for example D:SourcesSxS. To mount the ISO file using the Windows Explorer, simply select Mount from the context menu of the ISO file:

Mount a ISO file using the Windows Explorer

Additionally, the user account used to run the steps described in this blog required administrative privileges on the system. This means the user must be a member of the local Administrators group.

Install the .NET Framework 3.5 Feature using the Server Manager

First you must open the Server Manager on the system where you want to install the .NET Framework 3.5.

1. In the Server Manager, open the Add Roles and Features Wizard by clicking Manage –> Add Roles and Features.
2. Step forward to Installation Type and select Role-based or feature-based installation.
3. Ensure that you have selected the correct server in the step Server Selection.
4. Continue to the step Select features and select the (Sub-)feature .NET Framework 3.5 (includes .NET 2.0 and 3.0).
5. Within the step Confirmation you must specify an alternate source path. On the bottom of the Confirm installation selections screen, click Specify an alternate source path. In the new dialog window Specify Alternate Source Path type the path to the [ISO]:SourcesSxS on the installation media or the local directory where you have copied the files to. In this example the files were copied to D:SourcesSxS. Close the dialog window with Ok and start the feature installation by clicking Install on the Confirm installation selections screen.

Select the Installation Type

Select the destination server

Select the feature “.NET Framework 3.5 (includes .NET 2.0 and 3.0)”

Specify an alternate source path

Specify an alternate source path

Install the .NET Framework 3.5 Feature using PowerShell

The following commands must be executed within a PowerShell that was started as an administrator.

You can verify if the .NET Framework 3.5 is already installed by running the following PowerShell command:

PS> Get-WindowsFeature -Name "NET-Framework-Core"

If the .NET Framework 3.5 is not installed, you will receive an output like the following:

Display Name                                            Name                       Install State

------------                                            ----                       -------------

    [ ] .NET Framework 3.5 (includes .NET 2.0 and 3.0)  NET-Framework-Core               Removed

To install the .NET Framework 3.5 Windows feature, you must run the following command:

PS> Install-WindowsFeature -Name "NET-Framework-Core" -Source "D:SourcesSxS"

After the command has finished, you will receive an output like this:

Success Restart Needed Exit Code      Feature Result

------- -------------- ---------      --------------

True    No             Success        {.NET Framework 3.5 (includes .NET 2.0 and...

If you run the following command again, the column Install State should show Installed for the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature:

PS> Get-WindowsFeature -Name "NET-Framework-Core"

Display Name                                            Name                       Install State

------------                                            ----                       -------------

    [X] .NET Framework 3.5 (includes .NET 2.0 and 3.0)  NET-Framework-Core             Installed

Known Issues

There are some system configurations that are incompatible with the described installation options in this blog post and result in weird errors.

For example, we observed such issues on systems that have been upgraded from Windows Server 2008 (R2) to Windows Server 2012 (R2) to Windows Server 2016 and Windows Server 2019 by using the Windows In place Upgrade.

To get the installation of the .NET Framework 3.5 feature working on such systems, we recommend additional research in the internet or to contact the Microsoft Support.

Nevertheless, in this case you can try to install the .NET Framework 3.5 using the Offline Installer provided by Microsoft.

Conclusion

This blog post describes two ways how to install the .NET Framework 3.5 feature on Windows Server 2016 and later. These two ways should work for most of your servers.

However, there are some system configurations that break the described installation options and require manual work to get the installation working. Solutions for these systems are not provided by this blog post!

Although the .NET Framework 4.6 is already pre-installed on Windows Server 2016, some applications still require the .NET Framework 3.5 version that you have to install on the server.

If the server has Internet access, the necessary files will be automatically downloaded during the installation process to complete the process. However, if there is no access, you will encounter error 0x800f081f – Installation of one or more roles, role services, or features failed. The source files could not be found.

Unlike installing the other features in Windows Server 2016, installing the .NET Framework 3.5 on an offline server requires the use of the installation disk and specifically the SxS distribution folder. So, you will either need to unpack the installation ISO to a local or network folder or to mount it on the machine before you install it.

Install .NET Framework 3.5 on the Server 2016 using the GUI

Follow the Add Roles and Features wizard from Server Manager and select the NET Framework 3.5 Features in the Features section.

In the last step of the wizard, before clicking on the Install button, click Specify an alternative source path first.

In the new window, specify in the path field the location of the SxS folder on the installation disc. For example, it may be in the form D:SourcesSxs or \servernameisosourcessxs.

Finally, install the .NET Framework 3.5 by clicking the Install button to complete the process.

[pro_ad_display_adzone id=”1683″]

Install the .NET Framework 3.5 on Server 2016 using PowerShell

Type the following command by changing the location of the SxS folder of the -Source switch based on your case.

Install-WindowsFeature -name NET-Framework-Core -source <drive>:sourcessxs

Alternatively, you can use the DISM command either from the PowerShell or from the command line, changing the folder location again.

dism /online /enable-feature /featurename:NetFX3 /all / Source:<drive>:sourcessxs /LimitAccess

That’s it! I hope I helped a bit to find how to install the .NET Framework 3.5 on Windows Server 2016.

Most modern Windows apps require the .NET Framework to be installed. For example, NET Framework 4.8 is installed by default on Windows 11/10 and Windows Server 2022/2019. However, some old and legacy applications require the .NET Framework 3.5, 2.0, or even 1.0 to be installed.

In this article, we’ll walk you through how to install .NET 3.5 on Windows 11/10/8.1 and Windows Server 2022/2019/2016/2012R2.

Installing .NET Framework 3.5 on Windows 11 and 10

Check that .NET Framework 3.5 (includes .NET 2.0 and 3.0) is not installed on your computer. Open a PowerShell console as an administrator and run the command:

Get-WindowsCapability -Online -Name NetFx3

In our case, .NET 3.5 is not installed (State=NotPresent).

On Windows 10/11, you can install the .Net Framework from the Turn Windows Features on or off panel:

1. Run the command optionalfeatures.exe;
2. Select .NET Framework 3.5 (includes .NET 2.0 and 3.0) in the list of components, click OK;
3. If your computer has direct Internet access, select “Let Windows Update download the files for you”;
4. Windows will download and install the latest version of the .NET Framework 3.5 component from the Microsoft Update servers.

If your computer is not connected to the Internet or disconnected from the network, then an error will appear when installing .NET 3.5:

Windows couldn’t complete the requested changes.
The changes couldn’t be completed. Please reboot your computer and try again
Error code: 0x8024402C

In this case, you can manually install the NET 3.5 feature from your Windows installation media. To do this, you will need an installation USB flash drive or an ISO image file with your Windows version (how to check the version of Windows in an ISO image):

1. Connect your media with the Windows installation image to your computer. In my case, I have the file Windows 11 ISO image file. Click on the file and choose Mount to connect the image to a virtual DVD drive (or use the PowerShell command: Mount-DiskImage -ImagePath "C:ISOWindows11-22h2.iso" );
2. In my case, the virtual drive with the image was assigned the drive letter E: (we will use this drive letter in the following commands);
3. To install .Net 3.5 from the component source files on the installation disk, use the command:
   DISM /online /enable-feature /featurename:NetFX3 /All /Source:E:sourcessxs /LimitAccess
   Or (a similar PowerShell command):
   Add-WindowsCapability -Online -Name NetFx3~~~~ -Source E:SourcesSxS
   

To make sure that the .NET Framework is successfully installed, run the command:

Get-WindowsCapability -Online -Name NetFx3~~~~

Name         : NetFX3~~~~
State        : Installed
DisplayName  : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
Description  : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
DownloadSize : 72822163
InstallSize  : 496836410

List the versions of the .NET Framework that are installed on your computer:

Get-ChildItem 'HKLM:SOFTWAREMicrosoftNET Framework SetupNDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match ‘^(?!S)p{L}’} | Select PSChildName, version

How to Install .NET Framework 3.5 on Windows Server 2022/2019/2016?

On Windows Server 2022, 2019, 2016, and 2012 R2, you can install NET Framework 3.5 in several ways:

• Via Server Manager: Add roles and features -> Features -> .NET Framework 3.5 Features -> .NET Framework 3.5 (includes .NET 2.0 and 3.0 );
• Using DISM: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
• With PowerShell: Install-WindowsFeature NET-Framework-Core

In this case, all the necessary .NET 3.5 installation files for your Windows Server version will be downloaded from the Windows Update servers. For this installation method to work, you need to check the following:

1. Your Windows Server must have direct Internet access. Proxy and firewall settings should not restrict access to Windows Update servers;
2. Your host must not be configured to receive updates from the local WSUS server. Check your current Windows Update settings using the Group Policy result report (rsop.msc) or directly in the registry;

   Check the value of the UseWUServer parameter in the registry:
   Get-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU" -Name "UseWUServer" | select -ExpandProperty UseWUServer
   If the parameter value is 1, then your host is configured to receive Windows updates from the local WSUS server. In this case, you will receive error 0x800F0954 when installing .NET 3.5. Change the registry parameter to 0 or remove it to connect directly to the Microsoft Windows Update servers.

If you can access the Internet from your Windows Server host, but it is configured to receive updates from WSUS, you will see error 0x800f081f when installing NET Framework.

Solution: Install .Net 3.5 online from Microsoft servers and ignore local WSUS:

1. Export the current Windows Update settings from the HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate registry key to a REG file:
   reg export HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdate c:WindowsUpdateRegFile.reg
2. Delete this key ( Remove-Item -Path HKLM:SoftwarePoliciesMicrosoftWindowsWindowsUpdate -Recurse ) and restart the service: net stop wuauserv & net start wuauserv
3. Run the .Net 3.5 installation from the web: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
4. After the installation is complete, return the previous WU settings: import the reg file ( Reg import c:WindowsUpdateRegFile.reg ) and restart the Windows Update service again

If there is no direct Internet access from the server, then when you try to install .NET 3.5 on Windows Server through the Server Manager, you will receive the error 0x800F081F (The source files could not be found), 0x800F0950, 0x8024402c, 0x800F0906, or 0x800F0907 (depending on the version of Windows Server).

Although .NET Framework 3.5 is listed as a feature of Windows Server 2022/2019/2016/2012R2, its binary files are missing from the Windows component store (Features on Demand concept). This is done to reduce the size of the operating system image on the disk. You can check if the .NET Framework 3.5 source files are available in the local component store of Windows Server with the command:

Get-WindowsFeature *Framework*

As you can see the status of the NET-Framework-Core feature is Removed.

In order to install the NET-Framework-Core, you will need a distribution with your version of Windows Server in the form of an ISO file, or in the extracted form in a network folder. Mount the ISO file with the Windows Server install image as a virtual drive (for example, drive D:). Now, you can install the Windows features from the GUI or using PowerShell.

You can install the .Net 3.5 feature from the Server Manager graphical console:

1. Select the .Net Framework 3.5 feature as earlier, but prior to clicking Install, click a small link Specify an alternate source path at the bottom of the form;
2. Specify the path to the Component Store (SXS) folder in your Windows Server distro. If you mounted the ISO image as a virtual disk, the path may look like D:sourcessxs. It can also be a network share, where you copied the distribution files (for example, \fs1isows2016sourcessxs). Then click OK.

It is much easier to install .NET Framework 3.5 feature from the elevated command prompt or PowerShell console. Just run the command:

Dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:D:sourcessxs /LimitAccess

If you want to install the Windows Server feature using PowerShell, use the Add-WindowsFeature command:

Add-WindowsFeature NET-Framework-Core -Source d:sourcessxs

After the component installation is completed, a server restart is not required.

You can also manually copy 2 CAB files microsoft-windows-netfx3... from the sourcessxs folder of your Windows Server install image. In this case, to install .NET 3.5, just run the command:

dism /online /Add-Package /PackagePath:C:distribnet35microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab.

Configure .Net Framework Offline Installation Options with GPO

You can configure specific settings for installing Windows components from a local source or Windows Update even when using WSUS with the Group Policy option Specify settings for optional component installation and component repair (located under GPO section Computer Configuration -> Administrative Templates -> System).

On a standalone computer, you can enable this policy setting using the Local Group Policy Editor (gpedit.msc). In an Active Directory environment, you can create a GPO for all computers/servers using the GPMC console (gpmc.msc).

Here you can specify that when installing or repairing Windows components, you should always download files from the Windows Update servers (Internet) instead of the local WSUS server (the “Download repair content and optional features directly from Windows Update instead of Windows Server Update Services” option).

You can also specify the path to the shared folder with Windows Server components that you want to use for offline installation in the “Alternate source file path” parameter:

• Specify the path to network shared folder in the UNC format (\fs01distrws22sxs) (here you can specify multiple UNC paths separated by semicolons: \fs01ws22sxs;\man02ws22sxs;\fs03sxs)
• It is also possible to specify a WIM file as a source: WIM:\fso1distrws16install.wim:2 (in this case, 2 is the index of your edition of Windows Server’s image in the WIM file. You can list available Windows Server edition in a WIM file with a command: DISM /Get-WimInfo /WimFile:"\serverdistrws2016install.wim" )

Use the different SXS sources for different versions of Windows Server. If you are running multiple versions of Windows Server on your network, you will need to create separate GPOs with different UNC paths to SXS sources. You can use Group Policy WMI filters to apply a GPO only to hosts that are running specific versions of Windows Server.