RPC Endpoint Mapper (RpcEptMapper) Service Defaults in Windows 10
Resolves RPC interfaces identifiers to transport endpoints. If this service is stopped or disabled, programs using Remote Procedure Call (RPC) services will not function properly.
Default Settings
| Startup type: | Automatic |
| Display name: | RPC Endpoint Mapper |
| Service name: | RpcEptMapper |
| Service type: | share |
| Error control: | normal |
| Group: | COM Infrastructure |
| Object: | NT AUTHORITY\NetworkService |
| Path: | %SystemRoot%\system32\svchost.exe -k RPCSS -p |
| File: | %SystemRoot%\System32\RpcEpMap.dll |
| Registry key: | HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcEptMapper |
| Privileges: |
|
Default Behavior
RPC Endpoint Mapper is a Win32 service. In Windows 10 it is starting automatically when the operating system starts. Then the RPC Endpoint Mapper service is running as NT AUTHORITY\NetworkService in a shared process of svchost.exe along with other services. If RPC Endpoint Mapper fails to start, the failure details are being recorded into Event Log. Then Windows 10 will start up and notify the user that the RpcEptMapper service has failed to start due to the error.
Dependencies
While RPC Endpoint Mapper is stopped, disabled or working incorrectly, the following services do not start:
- Background Tasks Infrastructure Service
- Local Session Manager
- Remote Procedure Call (RPC)
- System Events Broker
Restore Default Startup Configuration of RPC Endpoint Mapper
1. Run the Command Prompt as an administrator.
2. Copy the commands below, paste them into the command window and press ENTER:
sc config RpcEptMapper start= auto
sc start RpcEptMapper
3. Close the command window and restart the computer.
The RpcEptMapper service is using the RpcEpMap.dll file that is located in the C:\Windows\System32 directory. If the file is removed or corrupted, read this article to restore its original version from Windows 10 installation media.