This is a cached version of the page. The site is temporarily undergoing maintenance.

Navigation section

RSAT on Windows 11 Arm64: Native Admin Tools Now Available

  • Thread Author
Microsoft has finally closed one of the longest-standing gaps in Windows 11’s admin story: Remote Server Administration Tools (RSAT) are now available natively on Arm‑based Windows 11 PCs. After years of workarounds, emulation, and painful image gymnastics, IT pros can install common RSAT modules — Active Directory tools, Group Policy Management, Server Manager, DNS and DHCP tools, and more — directly on Arm64 laptops and tablets using the same Optional Features and capability-based flows used on x64 devices.

Background: why this mattered​

RSAT has been the canonical toolkit for Windows administrators for more than a decade. Historically, Microsoft shipped RSAT as standalone installers for Windows client OSes, but since Windows 10/11 the company moved RSAT to a “Features on Demand” model. That change improved update cadence and security, but it also tightly coupled RSAT availability to specific Windows builds and servicing channels.
Arm64 PCs — the Qualcomm‑based ultrabooks and other energy‑efficient devices that offer long battery life and cellular options — have been a growing presence in enterprise device fleets. Despite that growth, RSAT remained effectively x64‑only for client devices. That forced admins who preferred Arm hardware to carry a second x64 device, use remote jump boxes, or run management tools under emulation. With RSAT arriving on Arm, the door opens for administrators to use a single Arm laptop to manage Active Directory, DNS, DHCP, and other Windows Server services directly — no emulation required.
This change landed in Microsoft’s February 2026 optional preview update and was included in the March 2026 cumulative release. Microsoft’s official release notes describe RSAT components being exposed for Arm64 devices as Optional Features, and independent coverage by multiple outlets confirmed the rollout across the February preview and March cumulative update channels.

What’s included: the RSAT components that now work on Arm64​

The Arm64 RSAT rollout exposes the same set of capabilities Microsoft treats as Features on Demand in Windows 11. Expect the standard collection that most admins rely on:
  • Active Directory Domain Services and LDS Tools (AD UC / AD management consoles and the AD PowerShell modules)
  • Group Policy Management Tools (GPMC and related consoles)
  • Server Manager
  • DNS Server Tools
  • DHCP Server Tools
  • Certificate Services tools
  • Other RSAT subcomponents that had previously been packaged as discrete capabilities
These are available as optional features in Settings, and they can also be staged or installed with the PowerShell and DISM capability commands IT teams already use for x64 RSAT installation. For offline or media‑based deployment, Microsoft documents explicit MSU / DISM installation steps for Arm64 packages in the same month’s cumulative update guidance.

How to get RSAT on an Arm‑based Windows 11 PC​

There are three practical paths to enable RSAT on Arm64 devices depending on whether you prefer the Settings UI, PowerShell, or offline installation.

1) Settings (GUI) — the simplest route​

  1. Open Settings > System > Optional features.
  2. Click “Add an optional feature”.
  3. Search for “RSAT” or scan the list for desired RSAT components (for example, RSAT: Active Directory Domain Services and LDS Tools).
  4. Select the tools you want and click Install.
  5. Reboot if prompted.
This is the most user‑friendly option but relies on Windows Update/Features on Demand being available from your update configuration.

2) PowerShell — scripted and repeatable​

  1. Open PowerShell as Administrator.
  2. List available RSAT capabilities:
    • Get‑WindowsCapability -Online -Name 'RSAT'
  3. Install a specific capability:
    • Add‑WindowsCapability -Online -Name "<capability-name>"
      Replace <capability-name> with the exact string shown from the Get‑WindowsCapability output for the component you want.
  4. Verify installation:
    • Get‑WindowsCapability -Online -Name '<capability-name>' | Select‑Object DisplayName, State
PowerShell is ideal for automation, imaging scripts, and configuration management systems.

3) Offline / image servicing (DISM or Add‑Package)​

For systems without direct access to Microsoft update servers, or for adding RSAT to installation media, use DISM with a Features on Demand ISO or the MSU/MSP files provided in the cumulative update package:
  1. Obtain the matching Features on Demand / Optional Features ISO or the specific MSU files that match your Windows 11 build.
  2. Use DISM to add packages:
    • DISM /Online /Add‑Package /PackagePath:c:\packages\Windows11.0‑KBxxxxxxx‑arm64.msu
    • Or mount an ISO and use Add‑WindowsCapability with the -Source parameter pointing to the ISO’s LanguageAndOptionalFeatures folder.
Important: offline installs require exact build matching between the FoD source and the target OS. A small build mismatch will cause failures or “not applicable” responses.

Required builds and servicing notes — the precise numbers you need to know​

Microsoft introduced Arm64 RSAT in the February 2026 optional preview (delivered in the KB5077241 preview release) and folded the change into the March 10, 2026 cumulative update for Windows 11 (KB5079473). Administrators should be aware of the build numbers and servicing types:
  • February 24, 2026 preview: KB5077241 updated Windows 11 to OS builds 26200.7922 (25H2) and 26100.7922 (24H2) in preview channels and included RSAT Arm64 support as an Optional Feature.
  • March 10, 2026 Patch Tuesday cumulative: KB5079473 produced OS builds 26200.8037 (25H2) and 26100.8037 (24H2), rolling RSAT Arm64 into the stable servicing channel.
If you want RSAT on Arm NOW, install the February preview on test devices, or apply the March cumulative update in production after standard validation. For offline deployment, follow Microsoft’s MSU ordering and DISM guidance included with the March cumulative support documentation.

Deployment and management considerations for enterprises​

Enabling RSAT on Arm is an important capability, but it comes with operational expectations that teams must plan for.
  • Features on Demand and WSUS: RSAT components are delivered as Features on Demand and require access to Microsoft Update endpoints by default. If your environment uses WSUS or a proxy that blocks FoD downloads, RSAT entries may not appear in Optional Features and PowerShell installs will return “Not applicable” or error codes such as 0x800f0954. To work around this, either provision matching FoD ISOs in your update store, temporarily allow access to Microsoft Update, or stage RSAT via DISM with locally hosted packages.
  • Build matching: Offline FoD packages must match the target OS build precisely. Keep FoD ISOs for each image/build you deploy. Minor build mismatches are a common cause of installation failures.
  • Servicing stack and order of MSUs: When installing the March cumulative or similar packages manually, use the order Microsoft documents. The servicing stack update (SSU) and any prerequisite MSUs can be required for a successful install.
  • Image management: If you maintain custom Windows images for provisioning, update your image pipeline to include the March cumulative or relevant preview so freshly imaged Arm devices have RSAT capability visible without post‑imaging workarounds.
  • Group Policy and FoD download policies: Group Policies that block Features on Demand or Windows Update access may block RSAT installation. Review policies such as “Do not use Windows Update for Feature on Demand downloads” and related registry keys when you troubleshoot missing RSAT components.
  • Testing and phased rollout: As with any change to platform servicing, validate RSAT install paths on representative hardware: OEM images, corporate images, devices with third‑party security agents, and machines that boot in BitLocker‑protected setups.

Early reports and potential risks — proceed with caution​

The feature rollout appears to be staged and broadly available via Microsoft’s preview and cumulative updates, but community reports and early telemetry highlight caveats administrators should treat seriously.
  • Several administrators reported a small number of devices experiencing unusual behavior after the February preview — examples included BitLocker recovery prompts and driver conflicts on specific OEM configurations. These reports are community‑sourced and relatively limited in scope, but they underscore the need for careful preproduction testing before mass deployment.
  • RSAT installs on Windows 11 have historically been sensitive to build/patch parity and Windows Update configuration; many installation failures in the field stem from WSUS blocking FoD payloads or missing servicing stack updates.
  • Some organizations have seen RSAT installs taking a long time or stalling on systems with third‑party endpoint protection active; plan for longer maintenance windows when enabling multiple RSAT features on managed devices.
Because the feature arrives via preview and then cumulative servicing, the safest approach is a staged release: validate RSAT installs on a small cohort of representative Arm devices, monitor for BitLocker prompts and driver anomalies, and only expand broadly after a clean validation cycle.

Troubleshooting checklist​

If RSAT doesn’t appear or fails to install on an Arm device, use this practical checklist to narrow root causes quickly.
  1. Confirm OS build and cumulative updates:
    • Check winver or System settings to confirm you are on a build that includes the RSAT Arm capability (February preview builds 26200.7922/26100.7922 or March cumulative builds 26200.8037/26100.8037 or later).
  2. Check Windows Update and FoD access:
    • Ensure Windows Update Service is running and policies or WSUS settings aren’t blocking Feature on Demand downloads.
  3. Query available capabilities:
    • Run Get‑WindowsCapability -Online -Name 'RSAT' to list what the system sees and the capability names you must install.
  4. Install via PowerShell and capture errors:
    • Add‑WindowsCapability -Online -Name '<capability-name>' -Verbose and review output for codes or network failures.
  5. Use offline sources when necessary:
    • If FoD downloads are blocked, mount the official Features on Demand ISO that matches your build and use Add‑WindowsCapability -Online -Name '<capability-name>' -Source 'D:...'.
  6. If you get 0x800f0954 or similar:
    • This commonly indicates WSUS blocking. Either allow Microsoft Update for FoD or stage via offline images.
  7. Reboot and verify:
    • After install, reboot and confirm the consoles or PowerShell modules are functional.
For uninstalling or remediating failed installs, use Remove-WindowsCapability -Online -Name '<capability-name>' and reattempt after resolving the underlying cause.

Why this matters for Arm adoption in the enterprise​

The arrival of RSAT on Arm is more than a checkbox — it’s a practical enabler for IT teams adopting Arm devices as primary endpoints.
  • Single‑device admin workflow: Admins can use power‑efficient Arm laptops for on‑the‑go management without carrying an x64 machine or relying on remote jump boxes for GUI tools.
  • Better device choice: Organizations evaluating Arm for battery life, instant connectivity, or thermal benefits now have fewer management blockers to adopt these devices.
  • Modern management parity: RSAT’s availability on Arm brings parity to the client management story — essential for labs, field technicians, and hybrid admins who need GUI consoles and PowerShell modules locally.
That said, true parity will depend on broader third‑party ecosystem support (drivers, security agents, specialized tooling) and IT operations teams’ willingness to adapt image and update pipelines for Arm builds.

Practical recommendations for IT teams​

If you manage Windows fleets, adopt a conservative, test‑first approach:
  1. Lab validation first. Build a small Arm test group (representative OEMs, corporate images, encrypted devices) and validate RSAT installs from both the February preview and March cumulative packages.
  2. Update your images. Incorporate the cumulative March update (or later) into your base images so newly provisioned Arm devices surface RSAT without manual steps.
  3. Audit WSUS and FoD policies. Confirm Features on Demand downloads are permitted, or provision local FoD sources that match your builds.
  4. Plan maintenance windows. Some RSAT components can take time to download and stage; schedule accordingly and be mindful of potential interactions with endpoint protection.
  5. Staged rollout. Move from lab to pilot to broad deployment only after monitoring for BitLocker prompts, driver issues, or other anomalies.
  6. Communicate with users. If you manage mobile or field crews, inform them of changes and provide straightforward steps for administrators who need to add RSAT features locally.
  7. Document rollback and recovery. Keep clear instructions for removing RSAT features, restoring images, and undoing manual changes if unexpected behaviors occur.

The long view: what to expect next​

Now that RSAT runs natively on Arm64 clients, expect incremental improvements rather than an overnight revolution. Microsoft will continue to refine the deployment UX, and third‑party tooling will gradually expand native Arm support. Administrators should watch for follow‑up servicing updates that stabilize FoD downloads and address any edge conditions reported in the initial rollout.
Two likely evolutions to monitor:
  • Better offline tooling and FoD packaging for enterprise image pipelines that reduce build‑matching pain.
  • Wider ecosystem support from security and systems management vendors releasing Arm‑native updates or improved compatibility for RSAT workflows.

Conclusion​

The arrival of RSAT on Windows 11 Arm64 devices is an overdue but welcome development for IT professionals who prefer light, long‑battery devices without sacrificing management capabilities. Delivered via the February 2026 preview (KB5077241) and included in the March 10, 2026 cumulative update (KB5079473), Arm RSAT uses the same Optional Features and Features‑on‑Demand model familiar to Windows 11 admins. The practical benefits are immediate: GUI consoles and PowerShell modules are now installable on Arm laptops and tablets.
That convenience comes with operational caveats. Successful adoption depends on build parity, Windows Update and WSUS configuration, and careful testing to avoid the small set of reported install/compatibility hiccups. For enterprises, the path forward is clear: validate in the lab, adapt images and update channels, and roll out RSAT for Arm in a staged, tested manner. When those steps are observed, organizations can finally make Arm a first‑class citizen in their Windows management toolkit.
Source: Neowin Windows 11 Arm PCs finally get RSAT support
 

Click to expand...
You must log in or register to reply here.
Back
Top