Outdated Windows versions, incomplete updates, or issues with the AppX Deployment Service may also trigger this error, especially when the system fails to properly handle app packages. A corrupted user profile can likewise cause problems with app removal or executing certain commands.
1. Verify and Restart the Remote Procedure Call (RPC) Service
2. Run PowerShell with Elevated Permissions
Running PowerShell with elevated permissions ensures that you have full access to modify system settings or uninstall apps, which might otherwise be blocked by permission issues. After executing this, try the AppxPackage command again. If the issue persists, proceed to the next step.
3. Use Safe Mode to Remove the Appx Package
Booting your computer into Safe Mode can help troubleshoot and resolve issues by loading only essential drivers and services, avoiding conflicts with third-party apps and software. If you’re still experiencing the “AppxPackage: The Remote Procedure Call Failed” error, Safe Mode may allow the system to remove the app. To Exit Safe Mode, repeat these steps and uncheck the Safe boot option, then restart your system. If you still don’t understand, you can try our detailed guide on how to exit safe mode in Windows.
4. Reset or Reinstall Problematic Windows Applications (Optional)
If the app is installed and causing issues, consider resetting or reinstalling it via the Apps & Features settings.
5. Check System Integrity with SFC and DISM Tools
Sometimes, system integrity issues can cause the “AppxPackage: The remote procedure call failed” error. Running the built-in SFC (System File Checker) and DISM (Deployment Imaging Service and Management Tool) can fix corruption in system files and the Windows Image, potentially unblocking the app removal process.
Run SFC Tool:
Run DISM Tool:
6. Create a New User Profile
If none of the previous steps have fixed the issue, a corrupted user profile might be the root cause. Sometimes, errors like “AppxPackage: The remote procedure call failed” only appear on a specific user profile due to profile corruption. Creating a new user profile can help test if the issue is tied to your current profile. If the issue is resolved on the new profile, your original profile might be corrupted, and you can transfer your data to the new account.
7. Check System Language and App Bundles
If your system uses a non-English language or has specific regional settings, app bundles might be complicating the removal or installation process. To address this, use the -PackageTypeFilter parameter with PowerShell to target all components of the app, including its bundles. Command: This command ensures that all related app bundles are included for removal. Remember to replace appname with the actual name of the app you’re facing issues with.
8. Use SetACL Tool (For Advanced Users Only)
If the Remote Procedure Call service is running but you still face issues, it might be due to third-party tools corrupting or misconfiguring registry entries linked to AppX packages. This step is for advanced users, as this error often appears after using cleanup software or the system file checker. Corrupted files can disrupt the process, leading to the “Remote Procedure Call Failed” issue. For this, we’ll use the SetACL tool. SetACL is a command-line utility for managing file and registry permissions on Windows. It allows advanced control over access control lists (ACLs) and can modify permissions, ownership, and auditing settings for files, directories, and registry keys. In this instance, SetACL repairs the “Remote Procedure Call Failed” error by providing necessary permissions to a specific registry key that may be locked or incorrectly configured. By executing these commands, SetACL modifies access control entries (ACE) for that key, enabling the system to perform the required actions without permission issues. This process ensures that the system has full access to the needed registry entries, thereby resolving the error that prevents smooth operations. First, we’ll create a registry key if it doesn’t already exist: Apply Permissions Using SetACL Tool: (a Windows manipulation tool) After restarting, try again. Hopefully, this will resolve your problem. Good luck!
