Microsoft removes SaRA command-line tool from Windows; Get Help CLI replaces it

Windows updates from 10 March 2026 remove the SaRA command-line utility. Admin scripts calling SaRACmd must move to GetHelpCmd.exe. Here is how to migrate.

TechLogHub Engineering Team
April 6, 2026
3 min read
0 views

Share Article

Microsoft removes Support and Recovery Assistant from Windows

Microsoft has removed the Support and Recovery Assistant (SaRA) command-line utility from all in-support versions of Windows, starting with updates released on or after 10 March 2026. If your IT automation, RMM scripts or Intune remediations call SaRA to fix Outlook profiles, reset Office activation or scrub Office installs, those jobs need to move to the Get Help command-line tool.

What happened

In support article KB5086902, first published on 31 March 2026, Microsoft said the SaRA command-line utility (SaRACmdLine) was "deprecated to help secure and harden your environment" and removed from Windows in updates released on or after 10 March 2026. Microsoft's guidance to IT admins is direct: migrate away from SaRA and use the Get Help command-line tool (GetHelpCmdLine), which it says has similar capabilities and supports all SaRACmdLine scenarios on a more secure underlying infrastructure.

SaRA was a free, scriptable diagnostic tool that ran automated checks on Windows clients for problems with Office, Microsoft 365, Outlook and Windows itself. It could identify a root cause and either fix it automatically, suggest manual steps or route the user to support. Get Help is described as a self-contained, enterprise-ready diagnostic tool for Windows client issues affecting Microsoft 365 apps such as Outlook and Teams, runnable from the command line or PowerShell and suitable for remote use.

Who is affected

  • Windows 10 22H2, Enterprise LTSB/LTSC and IoT Enterprise LTSC 2021.
  • Windows 11 22H2, 23H2, 24H2 and 25H2.
  • Windows Server 2016, 2019, 2022 and 2025, plus 2008 R2 and 2012/2012 R2 under Extended Security Updates.
  • IT admins and helpdesk teams whose scripts or runbooks invoke SaRACmd, and anyone who packaged SaRA into deployment tooling.

Microsoft says existing SaRA scripts have been migrated to GetHelpCmdLine but will no longer work in the SaRACmdLine environment, so scripts that call the old executable need to be updated rather than reused unchanged.

Because the removal ships through regular monthly updates, the change lands quietly: there is no feature-update prompt or separate uninstall step. Machines patched with the March 2026 cumulative update or later should be assumed to lack SaRA, while machines that missed updates may still have it. Mixed fleets are exactly where a script works on one laptop and fails on the next, so migrate everything at once rather than waiting for failures.

What it means for developers and engineering teams

This is a tooling change, not a security incident, and the direct developer impact is small. The practical risk is silent breakage. Scheduled remediation jobs that call a now-missing executable often fail without anyone noticing until a user's Outlook issue is not auto-fixed. Treat it like any dependency removal: find every caller, update it, and add a check that the expected binary exists before the script runs.

A simple guard in PowerShell avoids that failure mode:

$tool = "C:\Tools\GetHelp\GetHelpCmd.exe"
if (-not (Test-Path $tool)) {
  Write-Error "GetHelpCmd.exe not found at $tool"
  exit 1
}
& $tool -S OutlookCalendarCheckTask -AcceptEula -LogFolder "C:\Logs\GetHelp"
exit $LASTEXITCODE

If you run these through Intune remediations or an RMM, a non-zero exit code surfaces the problem in reporting instead of hiding it. Capturing logs to a known folder also gives helpdesk staff something to attach to tickets.

It also fits a broader Microsoft pattern of retiring older utilities in favour of tools on newer infrastructure. Pinning automation to vendor tools you do not control means watching deprecation notices as closely as you watch library changelogs.

What to do now

  1. Find SaRA callers across your script repositories, Intune remediations, RMM jobs and Group Policy scripts:
    git grep -niE "saracmd|sara(cmdline)?\.exe"
  2. Download Get Help CLI from Microsoft's enterprise download link (aka.ms/SaRA_EnterpriseVersionFiles) and extract it to a managed location.
  3. Translate scenarios. Get Help uses the same scenario-switch style. Examples documented for the tool include:
    GetHelpCmd.exe -S ExpertExperienceAdminTask -AcceptEula
    GetHelpCmd.exe -S OutlookCalendarCheckTask -AcceptEula
    GetHelpCmd.exe -S OfficeScrubScenario -AcceptEula -OfficeVersion M365
    GetHelpCmd.exe -S ResetOfficeActivation -AcceptEula -CloseOffice
    Run Office scrub and activation scenarios from an elevated prompt.
  4. Add a pre-flight check in scripts that fails loudly if GetHelpCmd.exe is missing, instead of exiting silently.
  5. Test on a pilot ring before replacing SaRA calls fleet-wide, and update helpdesk runbooks.
  6. Report problems with GetHelpCmdLine through your Microsoft support channel, as the KB article advises.

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.