How to Install ADUC on Windows 11 (and Fix a Failed Install)

ADUC, the Active Directory Users and Computers console, is not a download. On Windows 11 Pro or Enterprise it belongs to the RSAT Active Directory Domain Services tools, added from Settings > System > Optional features > Add an optional feature (search for RSAT and tick the Active Directory Domain Services and Lightweight Directory Services Tools item) or with one Add-WindowsCapability line; it opens with dsa.msc. On a work PC it often fails because optional features come from a server that lacks them, a case covered below.

Install it in a minute from Optional features

Use this path on an unmanaged PC, or on a managed one to see whether the download is allowed before trying anything else. The labels follow Microsoft’s Remote Server Administration Tools page, which describes RSAT as a Feature on Demand added from the Optional features page in Settings; the path below is how current builds reach it.

  1. Press Windows + I to open Settings, then go to System > Optional features. If your build shows it under Apps instead, typing “optional features” in the Settings search box finds it either way.
  2. Next to Add an optional feature, select View features.
  3. Type RSAT in the search box.
  4. Tick RSAT: Active Directory Domain Services and Lightweight Directory Services Tools. Leave the other RSAT entries alone unless you need them; each one is a separate download.
  5. Select Next, then Install (labeled Add on some builds).
  6. Watch the progress under Recent actions. The package is small, about 17 MB plus its Server Manager dependency according to Microsoft’s Features on Demand list, so a few minutes is normal and ten minutes with no progress is a sign of the managed-PC problem described later.
Windows 11 Add an optional feature dialog with a search for RSAT and the Active Directory Domain Services tools checked
(1) Search for RSAT, then (2) check the Active Directory Domain Services tools and click Next. (Illustration)

A restart is normally not required. If the entry shows a pending state after the install finishes, or if dsa.msc is not found a few minutes after a successful install, restart once and check again. On Arm-based PCs, Microsoft’s Features on Demand list (linked in the PowerShell section) says RSAT is not offered as an optional feature on Windows 11 version 25H2; on those PCs some RSAT tools appear instead in Control Panel > Programs > Programs and Features > Turn Windows features on or off. If the RSAT entry is missing on an Arm device, look there.

Check your PC first: edition, rights and update source

Question Where to look What it means for ADUC
Which edition? Settings > System > About, under Windows specifications Microsoft lists Windows 11 Pro and Enterprise for RSAT. Home does not show the RSAT entries at all; upgrading the edition is the only route.
Am I an administrator? Settings > Accounts > Your info Adding a feature needs local admin rights. A standard user gets a credential prompt or a silent failure.
Where do updates come from? Settings > Windows Update; a line saying some settings are managed by your organization is the clue Unmanaged PCs pull the feature from Windows Update. PCs pointed at WSUS or a configuration policy may not be able to.
Is the PC on the domain? Settings > System > About, Domain or workgroup Not needed for the install, but needed to manage anything without extra steps (see the non-domain workaround below).

The edition rule is the one most often misread. Education is not on Microsoft’s RSAT page; if you are on an Education build, try the Optional features list and go by what it offers. For the administrator question, the ways to open an elevated window are collected in how to run as administrator in Windows 11.

Install with PowerShell or DISM

The command route is faster for a second machine and gives you an error message the Settings page hides. Microsoft’s non-language Features on Demand list gives the exact capability name, Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0, and notes that it depends on Rsat.ServerManager.Tools, which Windows pulls in automatically. The four tildes are part of the name: they separate fields that are empty for this language-neutral package, so do not shorten them.

  1. Right-click Start and choose Terminal (Admin), then approve the prompt.
  2. Run:
    Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0
  3. Confirm that it installed:
    Get-WindowsCapability -Online -Name Rsat.ActiveDirectory*
    The output should show State : Installed. Anything else (NotPresent, Staged) means the install did not complete.

Microsoft’s Add-WindowsCapability reference carries a detail that explains a lot of confused forum threads: when every source fails, the cmdlet fails silently. No red text, no ADUC. That is why step 3 is not optional. Running the command on a PC where the package is already installed returns without error too, so the Get check is the only honest status.

The DISM equivalent, for a Command Prompt or a script that runs outside PowerShell, is:
DISM /Online /Add-Capability /CapabilityName:Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0
A command using /Get-CapabilityInfo only reports on the package; it installs nothing, which trips up readers copying from pages that mix the two.

Where Windows looks for the feature

This is the part the Settings page never shows and the reason installs fail on office PCs. Microsoft’s Features on Demand (capabilities) page gives the lookup order for an online install:

  1. A path you supply with -Source (PowerShell) or /Source (DISM).
  2. Locations set by Group Policy.
  3. Windows Update, unless -LimitAccess or /LimitAccess tells it not to look there. LimitAccess also skips WSUS.

On a home PC, steps 1 and 2 are empty and Windows Update supplies the file. On a domain PC, Group Policy can point step 2 at a WSUS server or a file share, and if that location does not hold Features on Demand, the install dies there. The result is the familiar error 0x800f0954, or in the Settings page a download that sits at 0 percent and then disappears from Recent actions.

Fix a failed install on a work PC

Pick the first option you have the rights for.

Ask for the feature to be served

Microsoft’s Features on Demand and language packs availability page says WSUS could not host Features on Demand from Windows 10 version 1709 onward, and that Windows 11 version 22H2 reintroduced on-premises UUP updates so WSUS can supply them again. If your organization runs a current WSUS, the admin can approve the Features on Demand category and the Settings path starts working with no change on your PC. Pair this with a check that Windows Update itself is healthy; the fixes in how to fix Windows Update cover the stuck-service cases.

Change the policy (older builds only)

The policy is Specify settings for optional component installation and component repair under Computer Configuration > Administrative Templates > System. On builds before Windows 11 version 24H2 it has a checkbox to download repair content and optional features directly from Windows Update instead of WSUS; tick it, run gpupdate /force, and retry. Microsoft’s page states that this checkbox was removed in version 24H2, so on current Windows 11 builds the Windows Update checkbox is gone and the policy is used to point at an alternate source path instead. Older articles that tell you to tick the box are describing a control that no longer exists on a current build.

Install from a local source

If the admin gives you the Features on Demand media that matches your Windows build (an ISO or a share), mount it and point the install at it:

Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 -Source E:\ -LimitAccess

Replace E:\ with the drive letter or share path. -LimitAccess stops Windows from trying Windows Update and WSUS at all, which is what you want on a PC that cannot reach them. The media has to match the build; a package from a different release is skipped, and because the cmdlet fails silently you will only know from the Get check.

Read the logs

For anything else, C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\dism.log record the attempt. Search them for the capability name; the lines around it name the source that was tried and the HRESULT it returned, which is more useful to an admin than “it did not work”. Error 0x80070005 (access denied) in the same place means the window was not elevated.

Open ADUC and point it at a domain

  • Press Windows + R, type dsa.msc, and press Enter.
  • Or open Start > All apps > Windows Tools and double-click Active Directory Users and Computers. Right-click it there for Pin to Start or Pin to taskbar.
  • Typing “Active Directory” in Start search also finds it once the install has registered, which can take a minute after the Settings page reports success.

On a domain-joined PC signed in with a domain account, the console connects to the current domain on its own. On a PC that is not joined, or when you need a different domain, right-click Active Directory Users and Computers at the top of the left pane and choose Change Domain, then type the domain name. If the console refuses with a message that the domain does not exist or could not be contacted, the PC is not using the domain’s DNS servers or cannot reach a domain controller, which no ADUC setting can fix.

To run the console as a domain account from a non-domain PC, the commonly used form is:
runas /netonly /user:DOMAIN\username "mmc dsa.msc"
The /netonly switch uses the supplied credentials only for network connections, so the console opens locally and authenticates to the domain as that account. If the command errors on your build, open mmc normally, add the Active Directory Users and Computers snap-in, and use Change Domain with alternate credentials instead. Readers who need the wider RSAT set rather than just ADUC should start with installing the Active Directory tools on Windows 11; the companion piece on accessing Active Directory on Windows 11 covers the RSAT install from the connecting side.

Your first five minutes in ADUC

The console is a tree of the domain on the left and the objects in the selected container on the right. A few settings make it far more useful on day one.

  • View > Advanced Features reveals the Attribute Editor tab on every object and the system containers that are hidden by default. Most “where is that attribute” questions are answered by this one tick.
  • Action > Find searches the whole domain by name, so you do not have to know which organizational unit holds a particular user’s account.
  • Right-click a user for Reset Password, Disable Account and, on the Account tab of Properties, the checkbox that clears a lockout caused by bad password attempts.
  • Organizational units created in current versions are protected from accidental deletion by default; the checkbox lives on the Object tab (visible only with Advanced Features on), and you must clear it before a delete will succeed.

What you can change is governed by your domain account’s permissions, not by the console. A help-desk account delegated password resets will see every object and still get an access denied message on anything else. For changes across many accounts, the Active Directory module for Windows PowerShell, installed alongside the console in the same RSAT package on most builds, is quicker than clicking; run Get-Command -Module ActiveDirectory to confirm it is present on yours.

Remove it or roll it out to a team

To uninstall, open Settings > System > Optional features, find the RSAT Active Directory entry under installed features, expand it, and select Remove. The command form is:

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

For a help-desk team, install ADUC only on the workstations that will use it, and make the script safe to run twice by checking state first:

if ((Get-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0).State -ne 'Installed') { Add-WindowsCapability -Online -Name Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 }

Run it through whatever already manages those PCs (Intune, Group Policy startup scripts or Configuration Manager), and run it again after a Windows feature update, since a feature update can leave an optional feature missing until it is re-added. The Windows 10 steps differ slightly; the older walkthrough for installing ADUC on Windows 10 still applies to machines that have not moved yet, with the note that Windows 10 support ended on October 14, 2025.

ADUC and RSAT questions

Does ADUC work with Microsoft Entra ID?

No. ADUC manages on-premises Active Directory Domain Services. A PC joined only to Microsoft Entra ID (cloud-only) can install the console, but there is no on-premises domain for it to connect to; Entra users are managed in the Microsoft Entra admin center instead. Hybrid environments still use ADUC for the on-premises side.