What is rundll an error occurred during startup. RunDLL encountered an error while starting. The specified module was not found. How to fix

While loading operating system The error “An error occurred while starting ...dll” may occur. The specified module was not found." The error can be found on the Windows 7, Windows 8 and 8.1 operating systems (Windows 10 is not yet known).

This is what the error might look like:

Interestingly, in some cases it does not cause problems for the user, but not in all. Thus, some users complain that when they try to launch any application, the same error appears and the application does not start. Sometimes the problem is further complicated by the fact that the error number is not shown, so the user does not know what to do.

How to fix the error? Solution

There are several types of solutions to the difficulty that has arisen.

First- This is a reinstallation of the operating system. Of course, there is little good in this method, since re Windows installation It takes a lot of time, and the programs will have to be re-installed.

Second— system update. Some users claim that the banal helped them Windows update. Although how this can help if the updates have nothing to do with the appearance of the error, I honestly don’t understand. But you can still try.

Finally, third This is the type of solution that I recommend using. It was actively discussed by the Russian-speaking Windows community, but, as far as I know, it came from abroad. Be that as it may, you need to use a utility called Autoruns from Sysinternals (you can even find it on the official website Microsoft). Just before you start using the program, just in case.

So, download the program to your computer as an archive, unpack it and go to the folder. Here you see several files. Select the Autoruns file and double-click on it with the left mouse button to launch it.

Yes, yes, you need to delete these processes. After removing them, you need to restart your computer and look at the effect - it should help. The main thing is not to remove other processes that may affect the operation of the operating system.

That's all. If you have a different solution for the specified error, be sure to share it with site users.

Many users computer systems on Windows based They often encounter a problem when a message is displayed stating that the specified module was not found (error 126). Not everyone knows how to interpret it, and the question of which particular device is causing this problem often causes confusion. Let's figure out what's what.

Reasons and devices causing the error “The specified module was not found”

The failure itself with the indicated error, in general, does not represent anything particularly serious in terms of consequences for the operation of Windows operating systems.

This error can occur in the most different situations, but, as practice shows, in most cases this can come down to incorrect identification of damaged dynamic libraries, disabled HID devices (such as USB mice), or services that interpret correct access to server OS functions.

Error “The specified module was not found”: problem solution for Radeon video cards

To the great regret of fans of graphics chipsets from Radeon, these video adapters are most susceptible to failures of this kind. Even with correct installed drivers There may be a conflict when using OpenGL functions.

In the case when the system issues a notification that the specified dll module was not found, there may be three ways to solve this problem: either updating the video card drivers to latest version, or installation of the most relevant DirectX versions, or directly interfering with the system using the command line and performing several subsequent actions.

With the first two methods, I think everything is clear, so we won’t dwell on them. But it’s worth talking about manually fixing the problem separately. Now there is no point in explaining how the commands below will operate (especially from a software or technical point of view). It's enough that they just work.

So, for integrated graphics adapters (those that are built directly into motherboard) Intel type HD Graphics or for similar Radeon, nVIDIA, etc. chips command line you need to first register CD /d C:/Windows/System32, and then copy atio6axx.dll atiogl64.dll (pressing the enter key after each command). For desktop (non-embedded) models, the command looks slightly different: copy (again, followed by “Enter”. In theory, after this everything should work fine.

HID devices

So-called smart HID devices can also cause errors like “The specified module was not found.” In a sense, the situation with them is the same as with graphics equipment, however, in most cases the problem only comes down to the fact that for some reason the driver files were damaged or deleted.

In such a situation, for example, for Windows XP, you need to boot from the installation or recovery disk(for example, Live CD), find in the installation distribution a file called Drivers.cab, which is usually located in the i386 folder, and extract three main components from it: mouclass.sys, mouhid.sys and hidserv.dll.

After this, you must restart your computer in safe mode(F8 key when Windows startup), then copy the specified files to the System32 root directory Windows folders. Next - another reboot of the OS, but this time normal mode. As a rule, after this the system works stably in normal mode and without any glitches.

Server errors

Unforeseen difficulties may also arise with access to servers. In this case (similar to previous situations), the error “The specified module was not found” appears. You will have to fight it through the editor system registry, which is called by the regidit command in the Run menu ( Win combination+ R).

Here we need to go to the HKEY_LOCAL_MACHINE\SYSTEM branch, then CurrentControlSet, then along the “tree” - Services, and finally - the parameters section located in the lanmanserver branch. Here you need to enter the value “%SystemRoot%\System32\srvsvc.dll”, of course, if any other value is specified. The point here is that the Windows OS itself perceives any server, whether internal or external, as general concept"server" and doesn't make much difference even if different parameters access.

Bottom line

As a result, as is already clear, even if an error occurs due to the fact that for some reason the specified module was not found, it is still possible, and this is done quite simply, and no critical failures in the system are expected in the future. But first, it is advisable to determine the nature of the error, and only then make a decision in favor of correcting it. What it will become depends only on which component is experiencing a failure: software or hardware.

Of course, not all problems that may arise in connection with such errors are described here. However, in our case, these are the most common types of failures and the most practical methods for fixing them. We cannot exclude the possibility that the problems may be related to the hardware itself, that is, the drivers have nothing to do with it at all, but it is the hardware that will have to be changed. However, these, as they say, are the most extreme cases, which should be resorted to when nothing else helps (and it does not depend on the user or the operating system). But that's a completely different story...

If you receive the error "RunDLL - the specified module was not found" every time you start the operating system Windows systems 8.1, which has been updated from Windows 8, you can find a solution to the problem here.

Although clean install modern Windows versions takes only a few minutes, you will have to spend anyway Extra time for subsequent installation of all the programs you need.

The main advantage of a clean installation is that during this process, unlike an update, there are guaranteed to be no corrupted or incorrect entries left inside the system. So it's obvious that clean install Windows is more preferred option than update old version to a newer one.

On the official forum Microsoft support It's quite common to see reports from users who, after upgrading from Windows 8 to 8.1, receive the following error message after booting up their computer:

RunDll
An error occurred during startup
C:\PROGRA~1\COMMON~1\System\SYSPLA~2.DLL
The specified module was not found.

As you can see above, the message does not contain any error code that could help you understand which way to dig. However, users can see up to three such dialogs when starting their updated system.

To start, you can try SFC team/SCANNOW in a command prompt running with administrator rights. If this doesn't fix the problem, try the next method, but first create a point recovery systems - just in case.

1. Download the tool Autoruns by Sysinternals. This tool is recommended by IT specialists from Microsoft themselves for analyzing the system and various processes. You can read more about it on TechNet. After downloading, unpack the archive using any program for working with compressed files.

2. After unpacking the downloaded file, in the "Autoruns" folder you will see two executable file, namely "autoruns" and "autorunsc". Launch the first one.

3. In the program window, on the “Everything” tab, find the entries highlighted yellow. All you have to do is delete them individually. To do this, use the keyboard shortcut Ctrl+D, or simply click right click mouse on the entry, and then select "Delete".

Once all these entries are deleted, close Autoruns and restart the machine. The problem should be fixed.