One Possible Solution to "The RPC server is unavailable" Error
April 30th, 2008 - by James D. Murray
Have you ever encountered the “The RPC server is unavailable” error message when trying to start Disk Manager? Have you also noticed that Event Viewer and Disk Defragmenter don’t work either? In fact, if you look at the Services window, you’ll notice that many of Window’s necessary services are not running at all, including the Remote Procedure Call (RPC) Service. Try to start this service and (after a while) you’ll see the “Could not start the Remote Procedure Call (RPC) Service. Error 1058″ error message.
After some Googling, you will have discovered this is caused by the DCOM Server Process Launcher will also failing to start. Many other programs and services require this service because they are DCOM objects, or connect to DCOM objects. You will have also found many other people with the same problem and their solutions (e.g., reboot, Malware scan, sfc /scannow, rollback to restore point, reinstall Windows).
However, if you are like me, none of those solutions solved your Windows’ problem. Here’s what happened to me and how I solved it, and I hope it works for you. (If you are too impatient to read my prose, just skip ahead to the The Solution! section.
Have you ever encountered the “The RPC server is unavailable” error message when trying to start Disk Manager? Have you also noticed that Event Viewer and Disk Defragmenter don’t work either? In fact, if you look at the Services window, you’ll notice that many of Window’s necessary services are not running at all, including the Remote Procedure Call (RPC) Service. Try to start this service and (after a while) you’ll see the “Could not start the Remote Procedure Call (RPC) Service. Error 1058″ error message.
After some Googling, you will have discovered this is caused by the DCOM Server Process Launcher will also failing to start. Many other programs and services require this service because they are DCOM objects, or connect to DCOM objects. You will have also found many other people with the same problem and their solutions (e.g., reboot, Malware scan, sfc /scannow, rollback to restore point, reinstall Windows).
However, if you are like me, none of those solutions solved your Windows’ problem. Here’s what happened to me and how I solved it, and I hope it works for you. (If you are too impatient to read my prose, just skip ahead to the The Solution! section.






