How to Repair the Intune Remote Help App When It Crashes or Won't Launch

The Remote Help app relies on Microsoft Edge WebView2 for its browser controls. Outdated Edge versions are the primary cause of app crashes and launch failures.

Get-AppxPackage -Name "Microsoft.MicrosoftEdge.Stable" | Select-Object Name, Version

Open Microsoft Edge and navigate to edge://settings/help to check for updates. If Edge is outdated, update it first before proceeding with app repair.

Before attempting repairs, verify the current installation state and identify any obvious issues with the app registration.

Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Remote Help*"} | Select-Object Name, Version, InstallDate

Also check if the app appears in the Start menu or if there are any error messages when attempting to launch it. Look for the Remote Help icon in your installed applications.

Navigate to %ProgramFiles%\Microsoft\Remote Help to verify the installation directory exists and contains the necessary files.

This is the primary repair method that works for most Remote Help app issues. The Windows installer will attempt to fix corrupted files and registry entries.

Press Windows + R, type appwiz.cpl, and press Enter to open Programs and Features directly.

appwiz.cpl

In the Programs and Features window:

1. Scroll down and locate Remote Help in the list
2. Right-click on Remote Help and select Change
3. In the Remote Help Setup dialog, choose Repair
4. Click Next and wait for the repair process to complete
5. When you see "Setup Successful", click Finish

The repair process typically takes 2-3 minutes and will reinstall any missing or corrupted components.

If the Control Panel method doesn't work or you prefer the modern Settings interface, use the Apps & Features repair option.

Open Windows Settings using Windows + I, then navigate to Apps > Apps & features.

Start-Process ms-settings:appsfeatures

In the Apps & Features window:

1. Use the search box to type Remote Help
2. Click on the Remote Help app when it appears
3. Click the three dots menu (⋯) next to the app name
4. Select Modify from the dropdown menu
5. In the Setup window, choose Repair
6. Follow the on-screen prompts to complete the repair

This method uses the same underlying repair mechanism but through the modern Windows 10/11 interface.

Corrupted cache files can cause persistent launch issues even after repair. Clear the app's temporary data to ensure a clean startup.

Navigate to the Remote Help temporary directory and clear cached data:

cd %TEMP%
dir *RemoteHelp* /s
rmdir /s /q "%TEMP%\RemoteHelp*"

Also clear any Windows Event Logs related to Remote Help that might contain error states:

Get-WinEvent -LogName "Microsoft-Windows-RemoteHelp/Operational" -MaxEvents 50 | Where-Object {$_.LevelDisplayName -eq "Error"}

Clear the user-specific app data directory:

rmdir /s /q "%LOCALAPPDATA%\Microsoft\Remote Help"

After repair, thoroughly test the app to ensure all features work correctly. This step verifies that the repair resolved the underlying issues.

Launch Remote Help and check the following functionality:

1. App opens without crashing or error messages
2. User interface loads completely
3. Network connectivity test passes
4. Authentication with Intune services works

Run a connectivity test to Remote Help endpoints:

Test-NetConnection -ComputerName "remotehelp.microsoft.com" -Port 443
Test-NetConnection -ComputerName "login.microsoftonline.com" -Port 443

Attempt to start a test session (if you have appropriate permissions) to verify the complete workflow functions properly.

If repair methods fail, trigger an Intune sync to redeploy the Remote Help app. This ensures you have the latest version and configuration.

Open Company Portal app or trigger sync via PowerShell:

Get-ScheduledTask | Where-Object {$_.TaskName -like "*Intune*"} | Start-ScheduledTask

Alternatively, force an immediate Intune sync:

$namespaceName = "root\cimv2\mdm\dmmap"
$className = "MDM_EnterpriseModernAppManagement_AppManagement01"
$methodName = "UpdateScanMethod"
$session = New-CimSession
Invoke-CimMethod -Namespace $namespaceName -ClassName $className -MethodName $methodName -CimSession $session

Wait 15-30 minutes for Intune to process the sync request and redeploy applications. Check the Company Portal for any pending app installations.

If the app still doesn't work after redeployment, uninstall it completely and let Intune reinstall:

Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Remote Help*"} | ForEach-Object {$_.Uninstall()}

Network connectivity issues can cause Remote Help to appear broken even after successful repair. Verify firewall rules and network access.

Check if Windows Firewall is blocking Remote Help:

Get-NetFirewallRule -DisplayName "*Remote Help*" | Select-Object DisplayName, Enabled, Direction, Action

If no rules exist, create them manually:

New-NetFirewallRule -DisplayName "Remote Help Outbound" -Direction Outbound -Protocol TCP -RemotePort 443 -Action Allow
New-NetFirewallRule -DisplayName "Remote Help Inbound" -Direction Inbound -Protocol TCP -LocalPort 443 -Action Allow

Verify DNS resolution for Remote Help endpoints:

Resolve-DnsName remotehelp.microsoft.com
Resolve-DnsName login.microsoftonline.com
Resolve-DnsName graph.microsoft.com

Test proxy settings if your organization uses a corporate proxy:

netsh winhttp show proxy