is no secret that any user running a Windows any version, Task Manager monitors the presence of incomprehensible to many service RunDll32.exe.Unfortunately, the errors that occur when you start this process, are not uncommon.We will understand what the process is and how to get out of the situation in the emergency failures in the service RunDll32.
RunDll32.exe: what kind of process?
To begin with, the service RunDll32.exe is a system process that is present in any of Windows.In simple words, it is responsible for the launch of the so-called dynamic link libraries, because they themselves direct the Windows start is not provided (as it applies to executable files such as EXE).
Deconstructing questions about how the service works RunDll32.exe, that in the process we have in this case and why errors occur, should say at once that it could be the original system process, and disguising viruses trying to getcontrol over any computer terminal.We will focus on the virus later.
What is the dynamic library DLL?
Dynamic libraries (Dynamic Link Libraries) are special compiled files containing executable code.Basically, they work like ordinary "ekzeshnym" files, only EXE-file is started directly by the system or manually, and dynamic libraries - with the help of the specified service.Yes, and a Windows service is much more correct than the executable EXE.
Incidentally, dynamic libraries have recently been increasingly used.The fact that, compared with conventional EXE file, they are much smaller and can belong to different programs, no matter using any programming language they were created.
Very often, these libraries are used for connection of software synthesizers and effects to virtual hosts.In fact, she is not an executable program and the call of each software component is performed using the executable code present in dynamic libraries.
principle of the service RunDll32.exe
As already mentioned, service RunDll32.exe as it derives from a dynamic link library code and executes it in the system for execution.For example, to enable the module Bluetooth, developed by Motorola, also used software process Rundll32.exe.Btmshellex (Bluetooth Shell Extension for Windows 8) in this case is precisely the library, from which the start of the main program and all of its associated components.
Bring these examples are enough.As another example, consider a system of assistance (help) developed by NewNextDotMe.Again to run the service using RunDll32.exe.NEngine in this case describes the process of New Next Helper Engine for Windows XP, which is the unified Help system.
RunDll32.exe application errors and their correction methods
malfunctions and failures in the system process are fairly common.Some of them can cause a blue "screen of death" that scares the average user.The service RunDll32.exe mistake - a very common thing, and its causes can be any number.First of all, the damage of the file RunDll32.exe, virus infection, or simply the absence of a computer.
The first thing you need to confirm his presence in the system.In Windows XP, the original file is on the path C: Windows \ System32 \ RunDll32.exe.With systems such as Windows 7 or 8, the situation is somewhat different.It is necessary to search the file in the folder SysWOW64, located in the root directory of Windows.
If suddenly there is a warning that the system can not find the component, do not panic.For starters, you can try to find the file in the folder located at C: \ Windows \ System32 \ Dllcache or C: \ Windows \ SericePackFiles \ i386.If he's there, it must simply copy the folder System32.
can use the original installation disc of Windows.For example, if the drive has lettered «Z», the command line will need to enter Z: \ i386 \ rundll32.ex_ C: \ Windows \ system32 \ rundll32.exe.After the computer restarts, the problem should disappear.
In some cases, you can use another method, which consists in the fact that you first need to download the utility DLL Suite, install and then run the application and start scanning for errors.If any are found, they can be corrected just by pressing one button.
That's what's interesting.In addition to the standard features of scanning and correcting errors, the program has to offer the user to download the original file RunDll32.exe with an open online resource, and then it will be automatically integrated into the system.
RunDll32.exe: suspected viruses
As for viruses, it's not so simple.To see whether the virus RunDll32.exe, that in the process in each case is present in the tree system services, you need to figure out for the launch of a component, it is responsible.
To do this, use the standard Task Manager "Processes" tab.Here, from the "View" menu select the display of additional columns, and tick mark "Command Prompt."Now, in the process tree you can see the full path to the file Rundll32.exe, dynamic library program for the launch of which it is responsible, and when the cursor is on the line - a brief description of the process and the manufacturer's software.
If for any reason the file path different from the original, and the library itself or running process is very suspicious, it is better to complete it in the Task Manager, and then apply a deep test of a powerful anti-virus package.Note the type of free antivirus AVG or Avira is better not to use, they are still in most cases do not find.
If the virus can not be determined, and the error will occur again and again, you may want to check your computer with the help of tools such as Rescue Disc from different developers.These tools usually start before the launch of Windows and can detect even the most cleverly disguised threats: viruses, Trojans, malware and so on. D.
Conclusion
Here we examined the service RunDll32.exe.What kind of process it is, probably, already outlined clearly.In addition, errors, as can be seen from the above, is not so terrible as it may seem at first.In principle, any user can correct them using any one or more methods alternately.If you look, all of these methods are good, but I think the use of a special tool DLL Suite with automatic check and fix file system errors is the most preferred and simple.
