RSAT for Windows 10 v1809

[Arthur]

In Windows 10 v1809, RSAT can be now downloaded and installed through the Settings app or with the following PowerShell one-liner.

 

Get-WindowsCapability -Online | Where-Object { $_.Name -like "RSAT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online

 

Settings > Apps > Manage Optional Features > Add a feature

 

[johnpd]

Do you still need Pro to install rsat as edu missing the ability it in 1803 and before

[jmak]

Edu sits above Pro in the hierarchy. You can install it on either.

[garethEds]

I#'m getting the following when installing via Powershell:

 

Add-WindowsCapability : Add-WindowsCapability failed. Error code = 0x80072f8fAt line:1 char:105+ ... AT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: ( [Add-WindowsCapability], COMException + FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsCapabilityCommand

 

Why they cannot make it downloadable like they used to is beyond me.

 

Gareth

[Arthur]

I'm getting the following when installing via Powershell:

What happens if you run either of the following two commands (from an elevated PowerShell window)?

 

Get-WindowsCapability -Name RSAT* -Online | Select-Object -Property DisplayName, State

 

Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability -Online

 

Why they cannot make it downloadable like they used to is beyond me.

Going forward, RSAT shouldn't be uninstalled every time you do a feature upgrade. That's a good thing.

[JamboD]

I#'m getting the following when installing via Powershell:

 

 

 

Why they cannot make it downloadable like they used to is beyond me.

 

Gareth

Do you have WSUS setup at all? I can't remember what my error was now but I fixed it with a post on TechNet, you can either download the Features on Demand ISO or change a GPO which is how I got it working. Apparently 1809 asks WSUS for RSAT but WSUS knows nothing about them. The fix for me was:

 

Launch local group policy editor via gpedit.msc and navigate to "Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair"

Enable the setting and select "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)"

 

Then I ran the following PowerShell command to install all of the RSAT tools:

 

Get-WindowsCapability -Online | Where-Object { $_.Name -like "RSAT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online

[DJ-1701]

Bumping this thread for anyone who is doing an upgrade on an IT Tech workstation.

[CHiLL]

What happens if you run either of the following two commands (from an elevated PowerShell window)?

 

Get-WindowsCapability -Name RSAT* -Online | Select-Object -Property DisplayName, State

 

Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability -Online

 

 

Going forward, RSAT shouldn't be uninstalled every time you do a feature upgrade. That's a good thing.

For some reason the combined Powershell command would bring up the error that others have posted. Running the two separately as you have posted worked. Strange.

[rosslaing]

The original RSAT tools work fine with 1809, just need to reinstall them (Upgrade removes them), no need for the ones through Optional features. just make sure you install the correct ones, which for just about everyone should be WindowsTH-RSAT_WS2016-x64.msu unless you are running Server 1803, in which case run WindowsTH-RSAT_WS_1803-x64.msu.

 

Im guessing the new RSAT tools through Optional Features will be for managing Server 2019.

Edited November 15, 2018 by rosslaing

[Wubbalubbadub]

Thanks for this! Worked great!

[DJ-1701]

In Windows 10 v1809, RSAT can be now downloaded and installed through the Settings app or with the following PowerShell one-liner.

 

Get-WindowsCapability -Online | Where-Object { $_.Name -like "RSAT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online

 

Do you have WSUS setup at all? I can't remember what my error was now but I fixed it with a post on TechNet, you can either download the Features on Demand ISO or change a GPO which is how I got it working. Apparently 1809 asks WSUS for RSAT but WSUS knows nothing about them. The fix for me was:

[color=#333333][color=#333333][i]Launch local group policy editor via gpedit.msc and navigate to
"Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair"[/i][/color][/color]
[color=#333333][color=#333333][i]Enable the setting and select
"Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)"[/i][/color][/color]

 

 

Then I ran the following PowerShell command to install all of the RSAT tools:

 

Get-WindowsCapability -Online | Where-Object { $_.Name -like "RSAT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online

 

If you want the tools installed on multiple PCs, you could create a GPO targeting them and just run this script, which should reinstall after an upgrade. The last bit of code at the bottom (commented) will also disable Microsoft Windows Update access for Optional Components again (in case you don't want to leave this open... otherwise just delete/comment it out ).

 

# If Active Directory does not exist, install RSAT.
If (!(Test-Path("$env:windir\System32\dsa.msc")))
{
   # Key controlling Optional Components details.
   $RegistryPath = "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\Servicing"

   # Ensure registry key is controlling Optional Components details is created.
   # Note: This should be created by default, but in case it's not, do it!
   If (!(Test-Path $RegistryPath)) {New-Item -Path $RegistryPath -Force}

   # Enable Optional Component updates via Microsoft Windows Updates to install RSAT tools in WSUS environment.
   New-ItemProperty -Path $RegistryPath -Name RepairContentServerSource -Value "2" -PropertyType DWORD -Force

   # Install all RSAT features.
   Get-WindowsCapability -Online | Where-Object { $_.Name -like "RSAT*" -and $_.State -eq "NotPresent" } | Add-WindowsCapability -Online

   # Disable Optional Components via Microsoft Windows Updates after installing RSAT tools.
   Remove-ItemProperty -Path $RegistryPath -Name RepairContentServerSource
}

[CHiLL]

I ran into an issue again installing the RSAT tools. This time I was receiving the error code: 0x8024500c

 

I came across this reddit thread and someone had posted this command:

 

#Set Windows Update Server Key to 0
Set-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU -Name UseWUServer -Value 0

#Restart Windows Update Service
Restart-Service -Name wuauserv -Force

#Get RSAT Tools
Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability -Online

#Set Windows Update Server Key to 1
Set-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU -Name UseWUServer -Value 1

#Restart Windows Update Service
Restart-Service -Name wuauserv -Force 
#Done

That worked for me.

[Arthur]

SCCM users may find the following blog post useful...

 

Deploy RSAT for Windows 10 v1809 using SCCM and PowerShell

[Arthur]

Deploy Features on Demand (FOD) using SCCM

 

Beginning with Windows 10 1709, you can’t use WSUS to host Features on Demand and language packs for Windows 10 clients. Instead, you need to download them directly from Windows Update.

 

Features on Demand (FODs) are Windows feature packages that can be added at any time. When a Windows 10 PC needs a new feature, it can request the feature package from Windows Update.

 

If you’re using SCCM or WSUS for your software update, you need to change a Group Policy setting that lets clients download these directly from Windows Update instead of your on-premise infrastructure. Without this group policy, all your installation tentative will fails with error 0x800f0954. This is because your client will check on your on-premise servers instead of Microsoft Update and won’t be able to find the feature.

 

You can also host Features on Demand and language packs on a network share, but starting with Windows 10 1809, language packs can only be installed from Windows Update. This is why we recommend using the group policy method to redirect your clients to Windows Update to get FoD or Language packs.