The structure of the Windows operating system of any modification, starting with the XP version, includes a service component, referred to as RPC. For the most part, ordinary users don’t know what it is, moreover, they don’t know what this service is for and how it works. In this regard, it is proposed to consider some basic aspects related to the component itself, the principles of its operation and the scope of use without describing unnecessary and complex technical terms. We will dwell separately on possible service errors and methods for their quick elimination.
Remote procedures (calling remote procedures): what is it?
Apparently, many users, based on the name of this service component, have already concluded that it is. Indeed, remote procedures (calling remote procedures) imply some actions when they are performed not on the local computer, but on the remote (most often on the server).
That is, the request is formed on one terminal, then transmitted to another, where it is executed, after which the response (report) on execution is returned to the first computer. But this is only a primitive explanation. In fact, everything is much more complicated, because here you need to consider data transfer protocols (UDP, TCP, HTTP) and many other mechanisms.
What is this service for?
Despite its main purpose, remote calling of RPC procedures can be applied not on different computers, but on one. As the simplest example, one can call a function of one program from another application. Many musicians working with virtual studios and sequencers know that each such application has its own editing or audio processing module, which does not always meet the requirements set by the user. And any studio allows you to connect any other external program instead.
For example, in the FL Studio sequencer settings, you can specify another application (say, Adobe Audition), which will be used by default for editing sound files (samples) in the main program environment. At the same time, the connection of Adobe Audition to FL Studio will not be through virtual hosts like VST, RTAS or DX, but directly through the use of the remote procedure call service. It goes without saying that this example is not the only one, since the scope of the described component is much wider.
Very often this service is also associated with the distribution of computing load on the terminals between which an interactive connection is established. At the same time, if the load is distributed evenly on the computing resources of several computers, maximum performance can only be achieved if small amounts of data are exchanged and a quick response between the components is achieved.
Remote procedure call failed: what is the reason?
Unfortunately, due to this demand, the appearance of failures and errors associated with this service is a fairly common occurrence.
As a result, it becomes impossible not only to use the component itself. Sometimes it’s not even possible to access some system settings, and Windows XP “flies” at all, after which it can be quite problematic to restore it to its normal working state. Another issue is the DISM online recovery tool, which is part of the operating system.
It is with violations in his work that the appearance of error 1726 is associated, which directly affects the functioning of the components of the RPC service.
The main reasons for such failures are called the means of checking or restoring the system when the DISM process is active or cannot complete the job correctly (for example, when DISM and SFC tools start from two command consoles at the same time); when a service runs in parallel with servicing RPC components; when the service is blocked by antivirus software.
Thus, if there is a failure during a remote procedure call in Windows 7 and above, the first thing to do is shut down DISM, restart the computer, and restart the service. If this does not help, you can try to switch to safe mode and completely disable anti-virus protection for the duration of the recovery. We will dwell on additional measures that help fix any failure during a remote procedure call and in any modification of Windows. In the meantime, let's look at issues related to disabling this system component (alas, but many users who do not know the essence of the issue are trying to do just such things).
Can I disable the RPC service?
So let's see how realistic it is to deactivate a call to remote procedures. Remote procedures, based on the recommendations of the developers, can not be turned off in any case. It is important! In principle, the operating system itself will not allow this. There are, of course, some workarounds involving the use of additional software, but for obvious reasons, the names of such applications are not given, because if they are used incorrectly, the entire system may become unusable.
The consequences of disabling RPC processes
Even if the user manages to somehow disable remote procedures (calling remote procedures), the consequences, unfortunately, can be the most unpredictable. As already mentioned, Windows XP may stop working altogether, and in an OS of a rank higher, as a result, there may appear a huge number of system failures that cannot be eliminated even if there is no access to critical Windows settings and parameters, and even in safe mode mode or when starting from removable media. However, a failure to call remote procedures in Windows 10 or earlier versions of the operating system can be fixed. The method is not the easiest, so when using it you need to be very careful.
Disabling Remote Access Locator
So, the main RPC service cannot be disabled. But maybe it makes sense to deactivate some of its related components? Yes, indeed, if you go to the section of system services and their components (services.msc), you can find the so-called RPC locator in it.
But it can be deactivated without fear for the appearance of catastrophic consequences. Having entered editing its parameters, you need to stop the component and set the startup type to disabled. Programs that can use remote procedures will also call remote procedures (without his help).
If, for some reason, the set parameters do not work, you can use the Windows installation disk, when booting from it, call the command line and enter the following:
- cd X: \ i386 (X is the drive letter);
- expand explorer.ex_% TEMP% \ explorer.exe;
- expand svchost.ex_% TEMP% \ svchost.exe.
After the reboot, the “Task Manager” is called and the process explorer.exe ends , then the copy% TEMP% \ explorer.exe% SYSTEMROOT% / y combination is written on the command line, after which absolutely all svchost processes are terminated in the “Task Manager”. Now you should be especially careful, because at the end of the process, in just sixty seconds you need to register the command copy% TEMP% \ svchost.exe% systemroot% \ system32 / y in the command console.
If the user, for example, in normal or safe mode has access to the system registry, in the editor (regedit) in the HKCC branch, you need to find the CSConfigFlags parameter and assign it a value of zero.
Troubleshoot 1726
Finally, fixing error 1726 is also done through the registry. But in this case, in the HKLM branch, you need to find the RpcSs directory, and on the right edit the value of the Start parameter.
It must be changed from four, usually installed by default, to two, and then restart the system.
Afterword
That, in fact, is all about calling remote procedures. Remote procedures, the principles of operation of this component in an extended version can be described for a very long time, but the emphasis in the material presented was made on a general familiarization with the service and some methods for eliminating errors and failures that it can cause in a computer system. Ordinary users will have to be patient and be very careful, because one incorrect action in the registry can lead to a complete crash of the operating system.
Please note that failures of this type by any other means, such as optimizer programs and parameter adjusters of Windows operating systems, are not resolved. With all desire, neither the command line, nor, moreover, intervention in the registry at the level of editing keys in such software packages is provided.