RSAT on Windows 11: How to Install It (and Why It Fails)

RSAT is not a download on Windows 11. It ships inside the operating system as a set of Features on Demand, and you install the pieces you need from Settings > Optional features or with a single Add-WindowsCapability command, but only on Windows 11 Pro or Enterprise, with administrator rights. Windows 11 Home cannot install it at all, and that single fact accounts for most of the “RSAT is not in my optional features list” reports.

Remote Server Administration Tools are what let you run Active Directory Users and Computers, DNS Manager, DHCP, Group Policy Management and Server Manager from a client PC instead of remoting into a domain controller. Microsoft’s Install and Manage Remote Server Administration Tools documentation is the authority here, and everything below is taken from it and from the Features on Demand capability list.

What you need before you start

Microsoft lists four prerequisites, and all four are hard requirements:

• Windows 11 Pro or Enterprise only. Microsoft’s wording is unambiguous: “You can install RSAT only on Professional or Enterprise editions of the Windows client operating system.” Home is out. (On Windows 10 the equivalent baseline is the October 2018 Cumulative Update or later, Pro or Enterprise.)
• Administrative privileges on the PC where you are installing.
• Administrative privileges on the remote servers for whichever service you intend to manage.
• Network connectivity to those servers.

The tools are per-machine, not per-user. Installing them once makes them available to every administrator who signs in to that PC.

Method 1: Settings (the fast way)

1. Sign in with an account that has administrative privileges.
2. Select Start, type Optional Features, then select Add an optional feature.
3. Scan the list first to see whether the tool is already installed.
4. If not, select View features at the top of the page, search for the tool you want, select it, then Next and Install.

Search for RSAT and the whole family appears with friendly names such as RSAT: Active Directory Domain Services and Lightweight Directory Services Tools, RSAT: DNS Server Tools, and so on. Once installed, the consoles live under Windows Tools in the Start menu, and under the Tools menu inside Server Manager.

Method 2: PowerShell (the repeatable way)

If you build machines more than once, use this. Run PowerShell as Administrator.

List what is available and what is already present:

Get-WindowsCapability -Online | Where-Object Name -like 'RSAT*'

An uninstalled tool reports as State : NotPresent. Install one by capability name:

Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0

The four tildes are part of the name, not a typo. They are empty fields in the capability identifier. You can pass several names separated by commas. A successful install returns Online : True and, usually, RestartNeeded : False.

The capability names worth knowing

Watch the dependencies. Microsoft documents them explicitly and they are the reason a “single” install pulls in more than you expected:

• Rsat.ActiveDirectory.DS-LDS.Tools depends on Rsat.ServerManager.Tools.
• Rsat.BitLocker.Recovery.Tools depends on Rsat.ActiveDirectory.DS-LDS.Tools, so a 52 KB tool drags in roughly 50 MB of prerequisites.
• Rsat.FailoverCluster.Management.Tools depends on Rsat.FileServices.Tools.
• Rsat.RemoteAccess.Management.Tools depends on both Server Manager and Group Policy Management tools.

Method 3: Windows Features (for the ones that are not Features on Demand)

Not every RSAT tool is a Feature on Demand. Hyper-V Management Tools, notably, is a Windows optional feature on the client instead. Select Start, type Windows Features, choose Turn Windows features on or off, tick the tool, and select OK. The PowerShell equivalent is:

Get-WindowsOptionalFeature -Online -FeatureName *tools* | FT FeatureName,DisplayName,State
Enable-WindowsOptionalFeature -Online -FeatureName <FeatureName> -All

The -All switch enables the parent feature and its default dependencies, which saves a round of trial and error.

When RSAT will not install: the three real causes

1. You are on Windows 11 Home

There is no workaround worth using. The capability is not present in the image and Microsoft does not supply it for Home. Upgrading the edition is the fix.

2. WSUS is blocking Features on Demand

This is the classic corporate failure, and it produces error 0x800F0954. Features on Demand come from Windows Update, not from WSUS, since Windows 10 version 1709 you cannot host FoD packages on WSUS locally. If the client is pointed at WSUS, the request for the RSAT package goes to a server that does not have it and fails.

The fix is a Group Policy setting: Computer Configuration > Administrative Templates > System > Specify settings for optional component installation and component repair. Set it to Enabled and tick Download repair content and optional features directly from Windows Update instead of WSUS. Then run gpupdate /force on the client and reboot before retrying. If it still fails, run gpresult /h report.html to confirm the policy is genuinely applying to the OU the machine lives in. A policy linked to the wrong OU looks identical to a policy that does not work.

3. You are on an Arm64 device running Windows 11 version 25H2

A newer and much less documented limitation. Microsoft’s Features on Demand reference states that for Windows 11, version 25H2 on Arm64-based devices, RSAT FODs are not supported, and that some tools must instead be reached through Control Panel > Programs > Programs and Features > Turn Windows features on or off. If you are troubleshooting a Snapdragon-powered laptop and the optional feature search returns nothing, this is why, not a broken image.

Removing a tool

Uninstall from the same Settings page, or with the matching PowerShell cmdlet:

Remove-WindowsCapability -Online -Name Rsat.Dns.Tools~~~~0.0.1.0

Remove dependents before dependencies. Pulling Server Manager out from under the AD tools will leave consoles that launch and then fail.

What you get, in practice

Installing the AD DS tools gives you the two things most administrators actually came for: the Active Directory Users and Computers MMC snap-in and the ActiveDirectory PowerShell module. The DNS tools add DNS Manager and dnscmd.exe. Group Policy Management Tools add the GPMC and the Group Policy Management Editor. Server Manager itself is a Feature on Demand on the client. On Windows Server it is installed by default.

One workflow note: after installing Server Manager on a client, open it, select Tools, pick the console you want, and supply the name or IP of the remote server when prompted. You do not need the server role installed locally; only the management tool.

Frequently asked questions

Can I install RSAT on Windows 11 Home?

No. Microsoft states that RSAT can be installed only on Professional or Enterprise editions of the Windows client operating system, and that it cannot be installed on Home or Standard editions. The tools are absent from the image entirely, so there is no optional feature to enable. Upgrading to Pro is the only supported route.

Why is RSAT missing from my Optional features list?

Three common reasons: the PC is running Windows 11 Home; Group Policy is pointing Features on Demand at WSUS, which cannot host them; or the device is Arm64 running Windows 11 version 25H2, where Microsoft states RSAT Features on Demand are not supported. Check the edition first. It takes five seconds and explains most cases.

What causes error 0x800F0954 when installing RSAT?

The client is trying to fetch the Feature on Demand package from WSUS instead of Windows Update. Enable the Group Policy setting “Specify settings for optional component installation and component repair” and tick the option to download repair content and optional features directly from Windows Update instead of WSUS, then run gpupdate /force and reboot.

Do I need to reinstall RSAT after a Windows feature update?

Generally no on current builds. Features on Demand are preserved across updates, which is one reason Reserved Storage exists. Historically RSAT was dropped by some upgrades, so it is worth running Get-WindowsCapability -Online with an RSAT filter after a major update to confirm the state is still Installed.

What are the four tildes in the capability name for?

They are empty fields in the capability identifier, which has the form Name~Publisher~Architecture~Language~Version. Nothing occupies those middle fields for RSAT packages, so they collapse into consecutive tildes. The name must be typed exactly, including them, or Add-WindowsCapability will not match a package.

The bottom line

On a domain-joined Windows 11 Pro machine, RSAT is two minutes of work: search Optional Features, add the tools you need, and find them under Windows Tools. Everything that makes it feel harder than that is environmental: the wrong Windows edition, a WSUS policy intercepting Features on Demand, or Arm64 hardware on 25H2. Identify which of the three applies before you start downloading anything from outside Microsoft, because there is nothing legitimate to download.

More Windows administration on Tech2Post: changing the administrator account on Windows 11, using the Installation Assistant to get a machine onto a supported build, fixing Wi-Fi that is not showing up, and customizing the taskbar. Turning off Sticky Keys covers the accessibility prompt that interrupts remote sessions.

Elsewhere on the site: what latency actually means is useful background for remote management over a slow link, optimizing a PC covers the same Device Manager territory from another angle, and AI coding tools and AI tools for daily use cover the scripting side of an administrator’s day. Screenshotting a console for a ticket is covered in screenshots on any device.

Sources: Microsoft Learn: Install and Manage Remote Server Administration Tools in Windows for prerequisites, the Settings and PowerShell installation steps and the tool availability table; and Microsoft Learn: Available Features on Demand for capability names, install sizes, dependencies and the Windows 11 25H2 Arm64 limitation.