Share via


Windows 10 - 1809 - RSAT Toolset - error code of 0x800f0954

Question

Wednesday, October 3, 2018 3:10 PM | 1 vote

Got the upgrade the 1809 this morning - trying to add the RSAT Toolset

Getting error code of Add-WindowsCapability failed. Error code = 0x800f0954

Does anyone know what this means and how to correct this?

Thanks in advanced

All replies (36)

Wednesday, October 3, 2018 6:41 PM âś…Answered | 78 votes

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.


Wednesday, October 3, 2018 3:34 PM

I have same problem. I tried installing from GUI and then from Admin PowerShell and received this message.


Wednesday, October 3, 2018 3:42 PM

Same here. Tried DISM, Powershell and GUI, no luck enabling RSAT. What gives MS?


Wednesday, October 3, 2018 4:00 PM | 2 votes

I was able to add the 'Active Directory Users and computers' with the following command:

DISM /online /add-capability /CapabilityName:Rsat.RemoteAccess.Management.Tools~~~~0.0.1.0

You an add other RSAT tools this way too.  Try

DISM /online /get-capabilities

To see a list of the other tools that can be added this way.


Wednesday, October 3, 2018 6:15 PM

Hello,

Are you using WSUS in the environment?

If you are have you enabled it to host Features on Demand (FOD) content?

Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


Wednesday, October 3, 2018 6:23 PM

Hello,

Are you using WSUS in the environment?

If you are have you enabled it to host Features on Demand (FOD) content?

Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

Is WSUS the only way to get additional FOD content like Microsoft-Windows-SystemInsights-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~.cab for example? They have a nice list of .cab files that could be injected with DISM, but no direct download links to them..

Also in the case of RSAT, previously you could install the .MSU, but you'd had to *enable* the feature, this is not possible anymore since the installed FODs are always installed and visible, right?


Wednesday, October 3, 2018 6:44 PM

Thanks for all the feedback and great answers!


Wednesday, October 3, 2018 6:47 PM

Hello,

You can get them via Windows Update.

There is or will be an ISO with the Features on Demand on MSDN or the Volume Licensing Portal.

I see it on MSDN download site, I do not see it on the Volume License download site yet.

Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


Wednesday, October 3, 2018 6:53 PM

RSAT utility is/was a Win XP software,dought it still exist for Win 10..Try MSDN search,they created it 15 yrs ago.


Wednesday, October 3, 2018 7:21 PM | 4 votes

RSAT utility is/was a Win XP software,dought it still exist for Win 10..Try MSDN search,they created it 15 yrs ago.

RSAT are the utilities to remotely manage Windows Server services.  They are post-XP and starting with Win10 1809 they changed how they get installed.

https://www.microsoft.com/en-US/download/details.aspx?id=45520


Friday, October 5, 2018 8:52 AM

Thnx, this fixed it for me


Wednesday, December 19, 2018 12:16 PM

it worked for me.  Thanks a lot


Friday, January 18, 2019 7:12 AM

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.

Thanks! This did the trick for me!


Tuesday, January 22, 2019 8:27 AM

I found this answer in another thread. It worked for me!

.....

saved my day. Thx a lot.


Monday, February 11, 2019 5:51 PM | 2 votes

Another approach to the same workaround would be temporarily changing Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer to 0 followed by a reboot and reverting the change after rsat installs.

Why is it necessary though?   Win10 1809 & FOD options are selected in the wsus products list on a fully updated Server 2012 instance, wsus synchronization successfully ran, rebooted 1809 client, but rsat installs still fail without the workaround.  Are these expected to fail by default in wsus environments?


Thursday, February 28, 2019 2:07 PM | 1 vote

Another approach to the same workaround would be temporarily changing Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer to 0 followed by a reboot and reverting the change after rsat installs.

Why is it necessary though?   Win10 1809 & FOD options are selected in the wsus products list on a fully updated Server 2012 instance, wsus synchronization successfully ran, rebooted 1809 client, but rsat installs still fail without the workaround.  Are these expected to fail by default in wsus environments?

Many thanks..... Worked for me, as didnt have the correct Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair key in my local policy


Monday, March 18, 2019 9:04 AM

Thank you, had the same situation.


Tuesday, April 2, 2019 6:08 PM

Thank you David.  I was on this issue most of the day!  yours is the only solution that worked!


Thursday, April 18, 2019 7:03 PM

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.

I tried five different things to enable .NET 3.5 before this with no success, but the local group policy setting 'Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair' did the trick!


Monday, May 13, 2019 6:38 AM

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.

You saved my day. Thank you very much.


Tuesday, May 14, 2019 8:25 AM

I cannot see it - maybe i am looking for the wrong entry.

What is the name that it is listed under?


Tuesday, May 14, 2019 5:29 PM | 1 vote

From gpedit.msc navigate to:

Computer Configuration> Administrative Templates> System

Then Look for:  Specify settings for optional component installation and computer repair

Select radio button for:  Enabled

And enable check box for:   Windows Update instead of Windows Server Update Services (Windows Server Update Services)

Lastly run:  gpupdate /force

For my notes above you can use link as a reference:
https://www.prajwaldesai.com/rsat-tools-installation-error-0x800f0954/
Very clearly illustrated by Prajwal
...hope this helps

...did not work for, but I'm also going to check the registry setting at:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
But it gets changed back when I run gpupdate /force
Need to put it in OU without GP and test again....

 

Regards, Kurt


Wednesday, May 15, 2019 12:08 PM | 6 votes

Set-ItemProperty "REGISTRY::HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU" UseWUserver -value 0
Get-Service wuauserv | Restart-Service
Get-WindowsCapability -Online -Name RSAT*  | Add-WindowsCapability -Online
Set-ItemProperty "REGISTRY::HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU" UseWUserver -value 1 

For the PS savy ones.

-Raymond


Tuesday, May 21, 2019 10:57 PM

Raymone,

the gpedit.msc fix that seemed to work for many others in this thread didn't work for me.

However, the PS cmdlets you provided worked great! Thanks alot!


Tuesday, May 28, 2019 3:49 PM

This Powershell script worked for me. The "UseWUserver" setting is managed by group policy, so I could not simply change it and reboot my machine (which would set it back to the policy setting). This script did the trick. I did modify it to only install the RSAT tools I needed...

Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools0.0.1.0
Add-WindowsCapability -Online -Name Rsat.GroupPolicy.Management.Tools
0.0.1.0
Add-WindowsCapability -Online -Name Rsat.ServerManager.Tools.Rsat.GroupPolicy.Management.Tools
Add-WindowsCapability -online -name Rsat.ServerManager.Tools~~~~0.0.1.0


Wednesday, June 19, 2019 12:17 PM

Thank you for this! Had my head baffled for an hour!!


Tuesday, July 2, 2019 8:33 PM

This was the fix for me as well. Many thanks!


Wednesday, July 17, 2019 1:12 PM

I was having the same issue on Win10 1903 Ent trying to install RSAT via Powershell. @David Hoeft suggestion worked for me.


Wednesday, July 24, 2019 10:27 PM

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.

This worked great!!

Robert


Wednesday, July 24, 2019 10:27 PM

I found this answer in another thread. It worked for me!

Run "gpedit.msc" to edit your local computer policy The setting in question is: Computer Configuration\Administrative Templates\System\Specify settings for optional component installation and component repair

My local policy seems to have defaulted to "Disabled" - after changing it to "Enabled" and selecting the checkbox labeled "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" the RSAT tools installed for me.

This worked great!!

Robert


Tuesday, August 13, 2019 1:08 PM

This worked for me but instead of rebooting I restarted the Windows Update service and it allowed me to install RSAT. Group Policy would have written over my registry change upon reboot which is why the service restart is key.


Sunday, October 6, 2019 7:34 AM

If you are behind a corporate GPO you should have a combination of all these:

1. Set UseWUServer = 0 as stated

2. Set the "Download repair content from WU" settings as stated before

3. Also remember to check
   "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"
   using
   "DoNotConnectToWindowsUpdateInternetLocations" = 0

Also remember that many of these settings will be reverted with gpupdate or regularly.
Just check values again in registry before starting the RSAT powershell commands, or when you get:
0x8024500c
0x800f0954

Thanks for all the help in this thread


Tuesday, December 3, 2019 11:13 AM | 1 vote

Set-ItemProperty "REGISTRY::HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU" UseWUserver -value 0
Get-Service wuauserv | Restart-Service
Get-WindowsCapability -Online -Name RSAT*  | Add-WindowsCapability -Online
Set-ItemProperty "REGISTRY::HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU" UseWUserver -value 1 

For the PS savy ones.

This saved me :)


Tuesday, December 3, 2019 2:16 PM

Thanks for making this fix even better by streamlining it with PowerShell.


Monday, December 30, 2019 6:11 PM | 1 vote

Running a recent 1909 update on an environment with WSUS, I did not find this gpedit.msc setting until I selected "All Settings" under Computer Configuration | Administrative Templates.  Enabling the setting, and checking the "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" allowed the following elevated PowerShell command to succeed.

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

I'm rebooting now, and hope to find it really did work as well as it seems.

Thanks


Wednesday, January 29, 2020 4:23 AM

Running a recent 1909 update on an environment with WSUS, I did not find this gpedit.msc setting until I selected "All Settings" under Computer Configuration | Administrative Templates. 

Thanks so much for mentioning this, eieioeieioeieio. Now that I'm on v1909, your reply helped me to try the solution mentioned by David Hoeft. 

Once I had done that, it didn't work until I tried tektotket's solution. I'm not sure if tektotket's solution would have worked on its own, but if not, both of them together does work.