Understanding the Error Code
The hexadecimal value -2147418113 translates to 0x8001010F, which maps to the COM error RPC_S_SERVER_UNAVAILABLE. In the context of Windows 10 language pack installation, this does not mean your computer is disconnected from the internet. Instead, it signifies that the client-side command cannot communicate with the server-side component responsible for processing the request.
When you use commands like Add-WindowsPackage in PowerShell or dism.exe in Command Prompt, these tools rely on WMI providers and specific Windows services to interact with the operating system's package manager. If any of these intermediaries are hung, disabled, or corrupted, the RPC call fails, resulting in this generic "server unavailable" message. It is crucial to distinguish this from actual network errors; the issue is local to the system's internal communication channels.
Verify Critical Services Are Running
The most common cause for this specific error is that the Windows Management Instrumentation (WMI) service or the Trusted Installer service has stopped responding or is set to manual startup. You must ensure these services are active before attempting installation again.
- Press
Win + R, typeservices.msc, and press Enter. - Locate Windows Management Instrumentation. Right-click it and select Properties.
- Ensure the Startup type is set to Automatic. If the service status is Stopped, click Start.
- Next, find TrustedInstaller (often named "Windows Modules Installer"). Repeat the process to ensure it is running and set to Automatic.
If you are unable to start these services due to access denied errors, it may indicate deeper permission corruption, which we will address in subsequent steps. Restarting your computer after adjusting these settings can sometimes clear temporary hangs in the service control manager.
Repair System File Corruption
Corrupted system files can break the RPC interface used by DISM and PowerShell. The System File Checker (SFC) utility scans protected Windows files and replaces incorrect versions with correct Microsoft versions. This is a standard first-line defense for unexplained CLI errors.
- Open the Start menu, type
cmd, right-click Command Prompt, and select Run as administrator. - Type the following command and press Enter:
sfc /scannow - Wait for the process to complete. This may take several minutes. Do not interrupt it.
If SFC finds and repairs files, restart your PC and try the language installation again. If SFC reports that it cannot fix some problems, proceed to the Deployment Image Servicing and Management (DISM) tool. DISM can repair the Windows image itself, which SFC relies upon. Run DISM /Online /Cleanup-Image /RestoreHealth in the same elevated Command Prompt window. This step downloads fresh copies of corrupted components from Windows Update if necessary.
Check Execution Context and Permissions
Language pack installation requires strict administrative privileges. If you are running the script from a non-elevated user account or through a scheduled task without the highest privilege level, the RPC connection may be rejected. Additionally, group policy settings might restrict access to the TrustedInstaller service for standard users.
Ensure you are launching PowerShell or CMD with explicit elevation. Right-click the application icon and choose Run as administrator. If you are using a script, verify that the execution policy allows the script to run with full trust. For enterprise environments, check if Group Policy Objects (GPOs) are blocking the installation of optional features or language packs. You can view applied policies by running gpresult /r in an elevated command prompt.
Alternative Installation Methods
If the CLI methods continue to fail despite repairing services and system files, the issue may be isolated to the specific DISM provider. In such cases, using the graphical User Interface (UI) can bypass the broken CLI pathway. Navigate to Settings > Time & Language > Language, click Add a language, and install the desired pack. The UI uses different background processes that may remain functional even when the CLI RPC channel is compromised.
For advanced users, extracting the language pack from the original Windows ISO and installing it offline can also circumvent online dependency issues. See How to Extract All Existing Languages Pack from Windows Installation Image for detailed instructions on preparing offline sources. This method ensures that all dependencies are present locally, removing potential conflicts with dynamic updates or cloud-based installation services.
Frequently Asked Questions
Why does my computer show RPC errors but internet works?
RPC errors in this context refer to internal inter-process communication within Windows, not external network traffic. Your internet connection handles downloading the files, while RPC handles the handshakes between PowerShell, DISM, and the Windows Modules Installer. A working internet connection does not guarantee that local services are communicating correctly.
Can I fix this error by reinstalling PowerShell?
No, reinstalling PowerShell is rarely effective because the error originates from the underlying Windows services (WMI and TrustedInstaller) that PowerShell calls, not PowerShell itself. The core issue lies in the OS-level components managing packages. Focusing on service restoration and system file repair is the correct diagnostic path.
What if SFC and DISM both report no errors?
If both tools report success but the error persists, the problem may be related to registry permissions or a stuck update transaction. Check the C:\Windows\SoftwareDistribution folder for locks or corrupted download caches. Clearing this cache and restarting the Windows Update service often resolves stubborn installation blocks.
Is it safe to disable UAC to fix this?
Disabling User Account Control (UAC) is not recommended and will likely not solve the root cause. While UAC prompts for elevation, the RPC failure occurs because the service is unreachable, not because of a permission denial. Disabling UAC reduces security without fixing the hung service state.
Does this error affect other Windows updates?
Yes, if the TrustedInstaller or WMI services are corrupted, general Windows Updates may also fail. However, minor updates sometimes use different pathways. If only language packs fail, the issue is likely specific to the DISM provider for optional features. If all updates fail, prioritize repairing the Windows Update service stack first.