The majority of Windows computer users will have experienced one or more seemingly nonsensical error messages pertaining to missing or damaged DLL files. This is because the DLL, or Dynamic Link Library, is an integral part of the Windows Operating System and is utilized by many of the programs and utilities that are installed on your system, as well as being used by the operating system itself.
A DLL is literally a collection of moderately small applications or pieces of code. Rather than being an executable program file, a program will call a DLL, which will in turn perform a specific task. The use of DLL files offers a number of advantages. Primarily the main advantage is that it causes less of a drain on the RAM (Random Access Memory) of your computer. Instead of having to rewrite lines of code and then load this code whenever an application is opened, the author of the application can instead call the DLL when it is required. Because the DLL is typically used only in a fraction of cases, this means that a portion of your RAM is left unused and available for use by other applications.
While an executable file is an entire program that can run independently, a DLL, although still an executable file, must be run from a program file. DLL files can not be run independently under any circumstances. Another use of a DLL file is to enable an application to communicate with another application or with a particular item of hardware on your system, such as your printer or speakers.
Information pertaining to each of the DLL files on your system is typically stored within the registry of the Windows operating system. A common problem can occur when an application updates a DLL file without checking whether any other programs rely on that DLL. If other programs do use that particular file and it becomes upgraded then those other applications may be incompatible causing software errors and general system errors.
Other problems with your DLL files can occur and will typically cause a range of problems with one or more applications. In some cases it will become impossible to open specific programs, otherwise it will prevent you from performing certain actions in at least one program. In the worst case scenario it can actually prevent access to your entire system, cause system crashes, and result in the blue screen of death.
DLL files can become corrupt, damaged, out of date, and infected with viruses or spyware. It is possible that you have an incorrect version of a DLL file installed for the application that you are attempting to run. However, in other cases, the error may not lie with the DLL file itself and the problem could be with the Windows registry or an incorrect call could be made from the program you are trying to use. These will, once again, cause serious issues on your computer and with the relevant applications and, for the most part, the resulting errors may appear to be related to the actual DLL file but this may not be the case. Do some research.
For the most part, the Windows operating system and the applications you use will automatically update the DLL files resident on your computer as and when required. However, it is also possible to manually update, remove, or replace any DLL file as required. In most cases the file can either be downloaded from an installation disk, the Windows website, or from an independent website. The file can then be installed within the DLL folder and you can continue to use the appropriate applications as designed.
However, before you begin attempting to download and install the latest DLL files there are some steps that you might wish to consider first. These general DLL error fixing techniques can help solve a lot of problems without having to remove and reinstall important system files. Install a good registry cleaner in order that you can clear out the registry of unnecessary entries. If there are conflicting registry entries then this will cause errors that may appear to be DLL errors. Similarly, you can attempt to uninstall and reinstall the application that you are struggling with.
The Windows OS disk contains a repair installation function that looks for missing and corrupt files and replaces them. Also consider scanning your system for infections from viruses and spyware in case this is causing a problem. Finally, check with the Windows update website and the website of the application publisher. If there are any updates available for download then you should install these immediately in order to combat any problems you are experiencing.
This guide is designed to walk you through the DLL file. It provides an in depth overview of what the DLL file is, how it is used, and common problems that can occur related to DL errors. There are also chapters dedicated to the Windows registry, registry cleaners to help clean the registry, and general error fixing rules. Later in the guide there is also a list of 30 of the more common DLL files, what they do, and any associated errors with those files. A guide is provided on whether you need to update or install the DLL file, where to look for the file itself, and any other considerations that might prove important to your cause.
We hope that you never need to refer to this guide, but the fact is that DLL files are one of the more common areas of the Windows operating system where problems can occur. When a DLL error does occur its effects can be catastrophic and difficult to resolve without the appropriate information and guidance. If you do require this guide then we wish you luck in finding the information you require, and we hope that the majority of that information will be found within these very pages.
What Is A DLL File?
A DLL, or Dynamic Link Library, is a collection of small executable files or functions. They canbeused to perform a number of tasks in the same way that any executable file is used to perform tasks. However, the functions and features that a DLL offers is much more restricted. There are also a number of other distinct differences between a DLL and an EXE file that we cover later in the guide. For now, though, it is important to realize that while a DLL is essentially an executable file, it cannot be run independently.
It sounds counter intuitive and more than just a little confusing but a DLL is a small executable that must be run through a main executable. A program can call a DLL file to perform a very specific task and, in doing so, it reduces the amount of system memory (RAM or Random Access Memory) that the main program needs to use.
In place of potentially hundreds of lines of code, a program can call a DLL function by using just a few lines of code. The DLL is then opened, the function performed, and the DLL closed. This means that your system memory is free to run without this code for the remainder of the time. The DLL file was introduced in a bid to save system resources when programs were becoming more competent, but before computer systems included so much RAM as standard. They are still used today because they offer a streamlined and much improved user experience.
However, for all of the benefits of the DLL file, it is certainly not without its potential problems. DLL error messages occur with alarming regularity for some users and virtually all of us will experience one of these errors at some point during our computer using lives. Unfortunately, DLL errors can also be accompanied by more serious errors. Software can become impossible to open, system errors more frequent, and you may also experience the blue screen of death or even a phenomenon dubbed as DLL hell.
Some applications naturally rely on the use of more DLL files than others. Theoretically, it would be possible to write an entire application using nothing but DLL calls, although in practice a program will require some skeletal programming to make it unique. The Windows operating system includes a large number of standard DLL files within its system folders but other applications, as well as the software associated with peripherals and other hardware, may also install DLL files into the appropriate section of your computer system.
DLL files are often updated to include new features, improve on existing features, and to generally update the way they operate. In most cases applications can run along more than adequately using the older versions, but with major changes it may be necessary to update the DLL you use. While this can cause errors with other applications that rely on the same DLL, application installers and updaters should check with the Windows registry to determine whether the update will cause any conflicts or errors.
DLL files are not only used to perform routine functions within applications. They are also executed in order that an application can communicate with other hardware on your system. For example, a common use of a DLL file is the print DLL. When called, this DLL will ready the printer and then execute the necessary code to complete the print. Other hardware such as your speakers, and input devices such as a scanner also have associated DLL files that work in a similar manner. All in all, the job of a DLL, is to save system memory on your computer and to make programs more uniform in their execution of regular functions.
A DLL file is a library of dynamic links. This means that a single DLL can contain a number of functions or features. When a DLL is called it is important that the program only calls the correct function within that DLL otherwise errors can occur. This process of calling only a small part of a DLL is referred to as a Declaration. Incorrect declarations, like incorrect calls, can cause serious errors with software and with your system as a whole and is one of the leading causes of DLL errors. Again, though, this is not actually an error caused by the DLL itself.
Having discussed what a DLL file is, some confusion may have arisen regarding whether a DLL file is the same as an executable file. The reason for this confusion is that, literally speaking, a DLL file is an executable file. The file and the functions that the file contains are executed once a call and a declaration are made. However, where the major difference between a DLL and an EXE file lies is in the fact that a DLL can not be directly executed.
A DLL needs to be called by a program file. Double clicking a DLL will not execute the file, but will only attempt to open a text version of the file containing the code in order that it can be edited. A proper call and declaration must be made by a .exe file before the functions of the DLL can be used.
As such, while a DLL file is an executable file it does not have the capability to be run as a standalone file. It is merely a collection of functions that are used by other applications and by the operating system itself.
A DLL file is a
particularly useful and beneficial accessory to your Windows operating
system. A Dynamic Link Library is literally a library, or collection, of
functions that can be accessed by the various programs on your system, and
by the system itself. It cannot be opened independently and, instead, must
be opened or executed by a full executable program file. Because a single
DLL contains several functions, the application must also declare the exact
function that it requires by using a declaration within the call.
The Windows Registry And DLL Files
The Windows Registry is one of the most important facets of the Windows operating system. It includes all details, settings, and information regarding your system, the users on that system, and the software installed. New entries are added to coincide with the addition of a new application or even a new file. The registry should also update when an application is removed by similarly removing the entries associated with that application, unless they are still required by another program.
Every DLL and application on your computer requires at least one registry entry in order to store pertinent details about it. When a new DLL is installed, a new entry should be added. When an old DLL is removed, Windows should first check to see whether it is required by any other applications and then remove or update the entry as appropriate. If a DLL is updated or changed in any way, then, again, the associated registry entry should also be changed to represent the differences.
Unfortunately, the registry of your computer can become filled with obsolete, incorrect, or corrupt entries. Similarly, many entries are inadvertently deleted causing an equal number of problems. Because DLLs are referenced and called by many applications, and because each DLL usually consists of a reasonable number of different functions it is imperative that registry entries are kept for each of the DLLs on your system and that they are updated accordingly to match the latest system information you have.
As we already mentioned, the registry is prone to problems. If you regularly install or remove software, make changes to your system settings, or generally use your computer then you are unfortunately leaving your system prone to errors. Cleaning the registry is absolutely essential if you wish to use your applications and the DLLs that are installed properly. This should be one of the first things you try when attempting to recover from a DLL error and the procedure is discussed later in this guide.
As well as incorrect, duplicate, or missing registry entries there are many other problems that may befall the DLLs on your system. It is possible to recover from virtually any error, but it may require some work, and may also mean a loss of functions in some programs. One of the leading causes of problems is an incorrect DLL version being called, and this can occur frequently. It may require the installation of several versions of a DLL, although most are backwards compatible.
Missing DLL this means that a call has been made by an application for a particular DLL. However, that DLL could not be found. In some cases this means that the DLL file in questions can not be found on your system. However, when a DLL is called, the application must provide a path to that library.
As such, a missing DLL error can occur in cases where the actual DLL name does not match the name of the DLL being called. It may also mean that the path that is being called does not match the actual path of the eisting DLL. The DLL may be on your system, but it is possible that it could have an incorrect name or be in the incorrect location. This could be an error with the DLL itself or with the coding of the application causing the error.
Corrupt DLL a DLL, like any other file or folder on your computer, can become corrupt. They become corrupt for one of a number of reasons. Spyware or virus infections can certainly lead to a number of important files on your system becoming corrupt. If you have manually attempted to alter the contents of a file, then this too can lead to a corruption. An interrupted installation, or even an interrupted execution of the DLL may also lead to a corrupt DLL error message.
Spyware and Virus Infection Spyware applications and viruses are rife. Even with antispyware software installed it is possible that you could have contracted an infection on your system. When this occurs you will most typically be informed that the DLL has become corrupt and cannot be used properly. However, some infections may attempt to alter the contents of a DLL so that it can still be executed. This may be done so that it executes a very different function, or so that your system hands or freezes because it is attempting to complete a never ending function.
Incorrect DLL Version DLLs are updated fairly regularly. This will soon become evident should you begin the search for one either on your system or from a third party website. In some cases, if you have the incorrect version installed on your system then this may cause errors. However, most DLLs are backwards compatible. This means that if you install a new version, but another application is calling for an older version you should not experience any problems.
Where errors of this nature tend to occur is when one application installs an older version of a DLL, while an existing application is demanding an older version. These errors are relatively rare, but when they occur, they can be the most troublesome to resolve.
General Protection Fault (GPF) a General Protection Fault typically results in an error message that reads something along the lines of ...has performed an illegal operation and will be shut down. You are then forced to shut down the application, or it will be automatically closed down. Typically, you will continue to receive this error either when you try to open the application, or when you attempt to run a particular function within that program.
A GPF usually occurs because a DLL no longer exists at the given location. The Windows Operating System or the application itself will display the GPF in order to prevent a total system crash. The software has called the error message rather than shut down your system. If the call for this error message does not exist then you may receive a more serious error.
These are only some of the more recognizable problems that can occur with your system associated with DLLs. There are many other problems that may manifest themselves in different ways. System crashes, the blue screen of death, and software that freezes may also be indicative that you have a problem with a DLL file somewhere within your system. Typically, each problem has its own resolution but there are certain things you can do to attempt to resurrect your computer from these errors.
DLL hell is a generic term that refers to virtually any problem associated with DLLs. However, it most commonly refers to problems with DLL versions that manifest themselves as poorly operating software. There are two leading causes of DLL hell, though both have become more obsolete with each new version of Windows that has been released, patched, and fixed.
If a working DLL is overwritten with one that is incorrect or contains incorrect data then you will receive an error. This is slightly different to the corrupt DLL problem above, but can cause serious problems when trying to use the functions of an application that require this DLL in particular. This was more of a problem when the exact contents of a DLL were first published on the Internet because incorrect versions were released at various locations. Once these incorrect DLL versions were installed they overwrote the correct version and software began to fail as a result.
This problem was largely fixed in Windows 200 onwards. Windows File Protection, usually referred to as simply WFP, ensures that your essential DLL files can not be easily overwritten without the appropriate permissions. This has all but eliminated this problem from most people's computers.
When a DLL is loaded onto a system, Windows will continue to use that version of the DLL, until all applications have finished using it. This means that if one application were to open a DLL from the system folder, and then a second application required a DLL with the same name but from the software folder, Windows would not attempt to open this second version. It would incorrectly attempt to use the first version that was not designed for the job in hand. This would typically mean that you would begin to experience problems when trying to open software in a particular sequence.
This problem was fixed in Windows XP. Windows XP opens separate versions of a DLL for every application using it. Because of the power, or more accurately the RAM, of modern setups, this does not tend to cause your system to run any slower but means that each application can open its own version of a DLL file as required.
For the most part DLL hell has become an obsolete problem. Windows updates and new releases have ensured that what were once common problems are now only really a problem for those of us that use older versions of the Windows operating system. There are manual workarounds for each of these problems, but they are not ideal.
General Steps To Fix DLL Errors
While most DLL errors are unique there are some steps that you should attempt before attempting to search for and reinstall the DLL you need from the Internet. Not all websites are trustworthy and, as such, you run the very real risk of potentially installing a virus or spyware riddled DLL onto your system. In most cases you should be safe, but if you can avoid taking the risk then you will avoid the possibility altogether.
Close down all open applications after saving your existing work. Attempt to open the applications again, and calling the same features as you did when the problem manifested itself. This provides your system and the software with the opportunity to open properly and can genuinely improve your chances of a trouble free session.
The switch off and switch on technique has long been the butt of many an IT joke. However, it does help to resolve a lot of problems because it gives your system the opportunity to reopen necessary files, including the DLLs required by your system and the software you are running on it. Always restart your computer properly, whenever possible. Obviously, if your system has hung or crashed then this may not be an option for you. While it may only be a quick fix and not the most ideal solution, attempting to reopen applications in a different order may prevent the problem from occurring again.
Software updates are usually available from the vendor's or publisher's website. These updates may contain critical file updates and so should be one of your first ports of call. Most applications include an automatic updater, but whether you choose to use this automated system or manually install updates as and when they become available, ensure that you do download the latest patches and updates. These may contain newer and more efficient versions of DLLs that you need.
As well as updating the software, update any drivers for attached hardware or peripherals. Where appropriate you may want to attempt to update with the latest firmware for those accessories that have it. Both of these methods are likely to introduce the most recent changes to the hardware you use. Because DLLs are sometimes used in conjunction with hardware and peripherals this simple technique may prevent a lot of heartache.
Like the software on your system, the Windows operating system also has regular updates. By default, when you install the Windows operating system, you will be informed of any new updates or patches. You will also be given the opportunity to install them onto your computer. Windows updates include vital patches, as well as security installations that are required to plug any holes left by earlier version of the operating system.
If you receive a DLL error when you attempt to use one specific application or a particular function within that application then you can attempt to reinstall the software. Reinstalling will remove some of the files or DLLs that have become corrupt or problematic in any way and replace them with genuine, clean versions. This may not be the case for those DLLs that are stored as part of the Windows operating system, however.
Also, contacting the software vendor or author may generate good results. Many users will contact them during the lifetime of the software, with any problems they encounter. The more proactive manufacturers will almost certainly find a way to resolve the problem and either publish the steps you need to take online or at least have the answer to hand when you make your own enquiries. Look for a knowledge base or support forum, because these can contain help from knowledgeable third parties. In some cases, other users may have resolved the problem themselves, and posted the solution on these forums and in articles.
If the problem is in the Windows registry, then cleaning the registry may help to resolve the error and ensure that your software and operating system can run properly. Registry cleaning should be done using a good registry cleaner. This third party software searches through the various registry entries to find any errors, duplicates, and other problems. In most cases it can resolve the problems, leaving you with a more efficient system and largely error-free applications.
Antispyware and antivirus software should be a staple part of every computer system. While it's unfortunate, it's also a sad fact that the majority of us are prone to picking up spyware and virus threats when we are online, especially if we download files, or even if we read email. Some threats can be picked up by doing little more than surfing to an untrusted website. These can effect the DLLs that are installed on your computer and, often, those that are currently running when you become infected. Download the latest updates to your security software and run a deep scan of your entire system and the Windows registry to find any infections and to clear them up.
With many DLL errors, you will have to do your research to discover the exact reasons behind the error. A good place to start this research is the Microsoft knowledge base website. The knowledge base contains literally thousands of articles, many of them related to DLL errors providing the reasons, the symptoms of the error, and the advised resolution. Where a Windows update has been released to assist in the resolution, a link is also usually provided to make your life easier.
It is possible that the Windows knowledge base will not contain the answers you are looking for. Use one of the major search engines and enter either the full error message you are receiving or just the name of the DLL. When you search, you will typically be presented with a number of websites, forums, and other resources that provide possible solutions. Do remember, that while these sites can be extremely useful, they are not always affiliated with Windows or with the software that is generating the error message.
If your online research has not generated a solution then you might need to take it to the next step. The error message you receive should, in most cases, contain the name of the DLL that it is attempting to call but this information alone is not nearly enough to help resolve the problem. There are applications available that will find and list all of the DLLs and processes that running software is calling. It will also display the path to the DLL, which is invaluable information for your purposes. Look at the full DLL name, path, and version number and then navigate to this folder on your computer.
Once you have found the path where the DLL should be loaded you will be able to determine whether the file is missing, incorrectly named, or if there is another problem. If the file is incorrectly named then you can create a copy of the necessary DLL and rename this copy. Unless otherwise instructed you should leave the original incorrectly named DLL in this folder, in case it is required by another program. Renaming the copy means that you have both the original and the renamed version of it on your system.
Even the slightest difference in the name of the file will make a DLL inoperable. A missing digit, an extra digit, or the inclusion of a version number that is different to the one you require can render the DLL completely useless. However, different DLLs can also be given names that are very similar in appearance. To be safe, it may be best to download and install a version of the DLL that you know to be correct.
If the DLL appears to be missing altogether, then it could either be saved in a different location, or it could be missing altogether. The safest means to resolve either of these problems is to download the right version of the DLL and save it to the path that is being called by your software. Check you are downloading at least the desired version of the DLL, although most are backward compatible so it should be OK to download a later version. Also ensure that you save the DLL to the exact location that your software is calling. If you place it in the wrong folder, thereby giving it a different path to the one that the application is using, then you still will not be able to use the functions within the file.
We've already discussed the importance of the Windows registry. It contains all of the relevant settings for your computer, the software installed on your computer, and the various users that log on to your computer. When you first start your computer, the Windows operating system consults the registry to determine the applications that should run on startup. When you open a file or an application, Windows consults the registry to determine the settings you use. When you perform virtually any task within Windows or a Windows based application, the changes are stored within the registry.
With regards to the use and handling of dll files, the registry contains information regarding each of the dynamic link libraries on your computer. If an application attempts to call a dll file then it will first query the registry to determine any relevant information that it requires. As such, the registry is highly important to the ongoing use of your dll files as well as your system and software as a whole.
Because the registry is so important to the safe and accurate use of your computer it is little surprise that it is also one of the areas of your computer that is prone to damage. If the registry, or any of the entries in the registry, become damaged, corrupt, or missing, then you are likely to struggle using some or all of the features of Windows and the software that you have installed on your computer.
In the course of fixing dll libraries it may be necessary to check, amend, or remove registry entries or values from registry entries. It is important to note that editing the registry incorrectly can lead to serious errors. In some cases it may not be possible to recover from these errors without completely removing and reinstalling your Windows operating system. If you do not fully understand how to use the Windows regsitry editor then we advise that you consult with somebody that does before progressing. The information we provide is accurate and, where registry editing is necessary, we provide the instructions you need to make the necessary changes.
In order to access the registry editor on your computer, follow these instructions:
In the Open: box, type regedit
The Registry Editor will display. Initially it will show the different classes of registry key which are as follows:
HKEY_CURRENT_USER Entries in this folder all contain information regarding the settings and configuration for the user that is currently logged on to the computer. This includes settings regarding the Start menu, control panel, display, and much more.
HKEY_USERS This contains the profiles for all users on a computer. When one of these people logs on to the computer, their profile becomes the HKEY_CURRENT_USER making that a subkey of HKEY_USERS.
HKEY_LOCAL_MACHINE This contains settings that are particular to the computer, and all users on the computer.
HKEY_CLASSES_ROOT This contains program associations to ensure that when a user opens a file, the correct applications is used to open it.
HKEY_CURRENT_CONFIG This contains information pertaining to the hardware on a system. Specifically it determines the hardware that is used when you log on to the computer.
In most cases, it is not advisable to manually edit the registry, unless a specific error or problem occurs that demands it. If there is a major error with the registry then you will not usually be able to operate your computer in a normal manner without restoring the registry back to a time and configuration when it worked properly.
Click Shut Down
Press F8 during system startup
Select Last Known Good Configuration
Select the appropriate operating system, if necessary, and press Enter
Restarting your computer from the last known good configuration can provide an effective way to combat many issues including the installation of incorrect drivers. It may also work if you are experiencing a dll related error, although in most of these cases you, or somebody with the necessary knowledge, may need to make changes using the registry editor to gain faull use of oyur system again.
Through the list of dll errors below you may notice that we mention registering a dll. An incorrectly registered or unregistered dll will not work rendering it completely useless. A dll file can become partially or incorrectly registered if it becomes corrupt or even if your system has become infected with spyware or a virus. Registering a dll is an easy process in later versions of Windows and can be done using the following technique:
Type regsvr32 followed by a space, followed by the name of the dll
If the registration is successful you will receive a message to this effect. On the message window you should click OK
30 Common DLL Errors
A lot of DLL errors are very specific to what you are doing when the error occurs. This is because a DLL can contain such a large number of different functions, of which you probably only require one or a small number at a time. When attempting to deal with a DLL error you should record as much information as possible. You should attempt to regenerate the error in order to help determine the exact reason.
In a bid to help you research any problems you might be suffering with DLL files we have included a list of some of the most common errors below. There are approximately 30 errors, and while this may only touch on the surface of the potential problems, they are a varied range of errors so give good insight into how you may be able to tackle similar errors on your own computer.
User Interface Failure:
The Logon User Interface DLL msgina.dll failed to load.
Contact your system administrator to replace the DLL, or restore the original DLL.
This error occurs on machines using the Windows 2000 operating system. Specifically, it occurs if you use Windows 2000 with Service Pack 3 installed. More recent service packs and older service packs do not encounter this problem.
This error occurs when you first log on to your computer, because several DLLs and executable files that are dependent on one another attempt to start at the same time. If the files start in the wrong sequence then you will receive this error.
In order to resolve this error users should download the latest Windows 2000 service pack, because this error is not present in any apart from version 3.
Iexplore caused an invalid page fault in module Tps108.dll
When attempting to open Internet Explorer version 5.5 on your system you may receive the error message above, or a GPF (General Protection Fault) that mean the application must be closed. A similar error may also be encountered when you attempt to open My Computer or Windows Explorer.
Tps108.dll is a third party DLL and this error only occurs if said DLL is resident on your computer. This DLL can prevent IE and Windows Explorer from working properly.
Any of the following solutions should prove effective for resolving this error:
Disable third party extensions within your Internet Explorer application Click Tools, Internet Options, and then Advanced. Within the Settings section of the page, locate the Browsing header and remove the tick from Enable third-party browser extensions (requires restart). Click OK and restart IE.
Disable tps108.dll Disabling the extension will enable Internet Explorer and Windows Explorer to work properly on your system. Locate the dll using the Windows search function, and note the path to the file. Click Start, then Run, type cmd, and press Enter. Type regsvr32 /u <<enter path here>>\tps108.dll. Click OK and then restart your computer.
Explorer caused an exception 6d007fh in module Webcheck.dll at...
Some users have reported receiving the error message above when their computer is idle as well as error messages when they click the Synchronize button in Internet Explorer. This problem occurs for people running Internet Explorer version 5 only.
The error occurs simply because you are using the incorrect version of webcheck.dll. You should use the version that was included with Internet Explorer 5.
Resolution of this problem is quick and simple reinstall Internet Explorer 5 on your system and restart your computer. You should not receive these errors any longer.
Microsoft Internet Explorer has encountered a problem and needs to close. We
are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
Restart Internet Explorer
Please tell Microsoft about this problem
We have created an error report that you can send to help us improve Outlook Express. We will treat this report as confidential and anonymous.
If you receive the error message above when attempting to browse the Internet using Internet Explorer version 6 then a third party IE add-on has added shell64.dll on your computer.
Resolution of this problem is relatively simple users can choose to either disable or delete the shell64.dll file from their system. The file itself is usually located within the system32 folder of your computer, although this may be different so do check thoroughly before taking any action.
Iexplore caused an invalid page fault in module Urlmon.dll
The error message above may be displayed when you attempt to run or open Internet Explorer. This occurs when there are several entries for Quick View Plus that appear within the Windows registry. Most applications require and indeed demand only one registry entry each, although more are possible in some cases.
Resolving this issue requires the editing of the Windows registry and the use of the registry editor. If done incorrectly, this can cause serious errors with software and with your system as a whole. If you are unsure how to use registry editor properly then seek advise from somebody else.
Remove all but one of the references to Quick View Plus that appear in the following registry key:
Iexplore caused an invalid page fault in module Mshtml.dll...
This error can occur when browsing the Internet using Internet Explorer version 5 or earlier. It is often caused by the use of High or True color resolution within the settings of Internet Explorer, and can typically be resolved quickly and easily.
Reduce the settings of the color palette to 256 color. This error usually occurs on computers that have a setting of High color or True color, which are 16 bit and 24 bit respectively.
Request a driver update from the manufacturer of your video card. Ensure that the driver version coincides with the version of Windows that you use.
Actxprxy.dll and shdocvw.dll
Internet Explorer Script Error
An error has occurred in the script on this page.
Error: No such interface supported
Do you want to continue running scripts on this page?
This error usually occurs when you attempt to open a link in a new window. The new window will not display the page you are attempting to open and you will, instead, receive this error message. Typically, this error is displayed, because information within the Windows registry that pertains to Internet Explorer, and specifically one of the DLLs listed, has become damaged.
In order to resolve this issue, you will need to register the DLLs again, in order that the information they contain can be updated and fixed. Click Start and then Run to open the Run dialog box.
Type regsvr32 actxprxy.dll in the box and click OK, and then OK again on the resulting message window.
Open the Run dialog box again, type regsvr32 shdocvw.dll, click OK, and then OK again on the message that appears.
Iexplore caused an Invalid Page Fault in module Kernel32.dll
This error message typically occurs when closing an open Internet Explorer window and you may receive similar error messages when closing Outlook or Outlook Express windows. It is most common for this error to occur when you have multiple Internet Explorer and Outlook or Outlook Express windows open.
This error can occur when using all of the email scan, Internet scan, and Internet filter functions in McAfee security software. The quickest way to prevent the error from occurring is to disable these features. However, you should contact McAfee to inquire about a fix for this issue in order that you can continue to enjoy the protection that these features of the software provide.
IEXPLORE caused an invalid page fault in module MSJAVA.DLL at 137:7c025b57
This error tends to occur when you attempt to open a web page that contains Java script or a Java object. It occurs solely because Explorer cannot run the Java code from the website. Usually this is because you do not have the latest version of the Microsoft Java Virtual Machine installed on your computer.
In order to resolve this issue, download the latest Java machine from the Microsoft website, restart Internet Explorer and attempt to navigate to the page that was causing the error.
This program has performed an illegal operation and will be shut down
This error occurs when attempting to open Windows, but only with versions of Windows that were added with a Microsoft Works suite. When you click to view the details of the error you will receive a further error message stating that an exception occurred in module msvcrt.dll.
This error most commonly occurs because files and DLLs associated with the Word add in for Works have become corrupt or damaged. This can happen for a number of reasons, as discussed earlier in this guide.
In order to resolve this issue and continue to use Word, remove the Works Suite Add-in for Microsoft Word entry from the Add/Remove programs function of Control Panel. Using Windows Search, find a file called normal.dot and rename this. Restart your computer so that you receive a message stating that Windows can not find all components of Works. Insert the Works disk, locate setup.exe from the WordAdd folder and double click it to reinstall the add-in and use Word normally.
Microsoft Word has encountered a problem and needs to close. We are sorry for the inconvenience
This error is associated with Hewlett Packard 1200 and 3200 printer drivers, especially when you then install other HP printer drivers. This is because all HP printers require the hpafd32.dll file, and many require the later versions of this DLL. While in the majority of cases, the dll will update on installation, this isn't always true. If you install another printer after using the 1200 or 3200 printers from HP, the dll does not update as required.
If you need to install a new printer driver then remove all of the components of the old HP printer and install the new printer as normal. This should install the updated version of the necessary dll. Failing this, contact HP support with the exact details of your problem and they will provide a solution.
Cannot load Library DLBAPRP.dll
This error message may display when you attempt to print a Word document and you have one of several Lexmark or Dell printers installed on your computer. In a small number of cases, the error can also occur when attempting to save a document. In either case the document will not print or save as you requested.
There is one workaround that should work in the majority of cases, otherwise you will need to contact the printer manufacturer to request a resolution to this problem.
Copy all the printer driver files from the drive:\Windows\System32\Spool\Drivers\W32x86\3 folder into the main Windows/System32 folder.
Clipart cannot complete the operation.
Interface not registered. Error code 0x80040155
This error is usually displayed when you attempt to add Clipart to a Word document. It occurs because the ole32.dll library has not been registered correctly and, as such, Windows cannot use the information it contains. This, in turn, may be caused by damage to your Windows installation.
In order to resolve this problem you should first attempt to register the ole32.dll library. This is done through the Run command Window as follows:
Type regsvr32 ole32.dll in the dialog box and click Open
Click OK on the message window that is displayed
If this does not work then you will, instead, need to reinstall your Windows operating system. This will replace and, therefore, repair any of the installation files such as Dynamic Link Libraries that have become damaged.
The command cannot be performed because a dialog box is opened, click OK then close dialog-boxes to continue
This error typically occurs when the officeav.dll library, the Office plug-in from Norton AntiVirus, has become corrupted or damaged. The error message above will be displayed when you attempt to open a Word document.
Dll files required by applications are often installed as and when needed. As such, removing the officeav.dll, or in this case renaming it, will enable you to add the Office plug-in through Norton and register a clean and undamaged version of the dll. To do this, follow these instructions:
Locate officeav.dll by using the Windows Search function
Rename it as officeavold.dll or officeav.old
Restart your computer
The MSIEXEC file is linked to missing export MSI.DLL:222
This error message is displayed during installation of Office applications, if the installation disks have become damaged or corrupted in any way. This can occur for numerous reasons. For instance, if you have downloaded the installation files and the download was interrupted before it could complete then this may cause damage to the installation files. Damage to an installation disk can also cause this error.
It is necessary to update the installer that is resident on your hard drive. This is done by visiting the Microsoft website, and downloading installer version 2.0. Once you have done this, try again to run setup. Everything should now work.
Wmpdxm.dll and dxmasf.dll
Cannot Complete Windows Media Player 9/10 Series Setup
This error message may be displayed when you attempt to install Windows Media Player version 9 or version 10. The installation will fail and you may also begin to experience problems when attempting to use Internet Explorer.
This error usually occurs because the wmpdxm.dll file has become damaged or corrupt, or has not been registered properly. In order to counteract this problem you should first exit all applications, especially the Media Player setup screens and then follow these instruction to register the library.
Type regsvr32 msdxm.ocx
Type regsvr32 dxmasf.dll
The file wmp.dll has a version number of 220.127.116.1175 where 18.104.22.16880 was expected. Windows Media Player is not installed properly and must be reinstalled.
This error message can be misleading in some respects. It is typically displayed whenever you attempt to open Windows Media Player but, despite the content of the error, uninstalling and reinstalling the Windows Media Player will have no effect in resolving this issue.
The issue does relate to a conflict in dll versions, however, as the message suggests and can be resolved using the following technique:
Type c:\windows\inf\unregmp2.exe /UpdateWMP
explorer has caused an error in wmp.dll and needs to close
wmp.dll is the main library used by the Windows Media Player and there are a number of problems that can surface because of this file. In this case, it is highly likely that the dll has not been registered properly or at all, or it has become corrupt for one reason or another. Re-registering the dll will usually resolve this issue and enable you to continue using Media Player on your computer.
Type regsvr32 wmp.dll
You should receive a message stating that the registration was successful click the OK button
Attempt to open and use Windows Media Player
Msvcp60.dll and msvcrt.dll
Msvcp60.dll is linked to the missing export Msvcrt.dll
This error usually occurs when you attempt to open Clip Gallery 5.0 although it may occur in other circumstances as well. The most likely cause is that you have the incorrect version of msvcrt.dll installed on your computer. In order to resolve this issue you should either repair your version of the Microsoft operating system or replace the msvcrt.dll file installed on your system. How to repair Windows will depend on the version that you have installed and also the settings on your computer. In order to replace the dll follow these instructions:
Search for msvcrt.dll using the Windows search function
Rename it to something like msvcrt.old
Restart your computer in MSDOS mode
Type cd system
Type ren msvcrt.dll msvcrt.old
Open Add/Remove Programs
Outlook.exe caused an 'access violation' fault in module Riched20.dll at 014f:4802bc95
You may receive this error message when attempting to start Microsoft Outlook. When you click OK on the error message the application will close down and you will be unable to access Outlook. Alternatively you might receive a similar error message when you attempt to create a new email. You will be unable to write the email but you should still have access to the Outlook program.
The solution to this problem is to first rename the riched20.dll file and then to repair your version of Outlook. Rename the file so that it will not be called by any other application and so that you do not mistakenly copy over another dll that may be required for other applications. One method to ensure this does not happen is to rename the file riched20.old.
Unable to open your default mail folders. MAPI was unable to load the information service GWMSPI.DLL
This is another error that typically occurs when you try to open Microsoft Outlook. This error is usually only prevalent in Microsoft Outlook 2000 Standard edition and when you click OK on the error message you will be unable to access the Outlook program or any of your emails. This error is caused by a software and feature conflict between Outlook and Novell, and you have added a messaging profile for both applications to the same Windows messaging profile.
To resolve this error ensure that you set up two Windows messaging profiles, one each for Novell and Outlook. Uninstalling and reinstalling either application, and attempting to install them in a different order will not help you to work around this problem.
Omint.dll and outlib.dll
Cannot start Outlook. A required component is missing OMINT.DLL. Please run setup again
This error only occurs when trying to start the older Outlook 98 version. It means that you have an incorrect version of outlib.dll installed on your computer that needs updating or backdating. Another possible cause, although less likely, is that the registry entries were not updated when you first ran Outlook on your system.
In order to resolve this issue you should first ensure that you are logged on to Windows NT as an administrative level user and you should then reinstall Outlook 98 on your computer. This will ensure that all registry entries are updated and that you have the proper version of all the necessary dll libraries installed. If necessary you will need to contact a network or computer administrator to either grant the appropriate access or to perform this for you.
missing WAB.dll file
This error occurs when attempting to open or use the Windows Address Book. In turn you will be unable to access the features that it offers until you have resolved the problem. There are two likely causes of this problem and both require similar steps to resolve. The Windows Address Book dll, or wab.dll is either missing or has become damaged or corrupt. It may also be possible that you have an incorrect version of the wab.dll library installed on your computer, but again these steps will resolve the issue if this is the cause.
Locate the wab.dll file on your system, and rename it something like wab.old. This will prevent Windows from attempting to access the file it is corrupt and enable you to add a clean and undamaged version. If the file does not exist then proceed with the following steps anyway. Ensure that you are logged on to your computer as an administrator or with administrator privileges and then remove and reinstall Outlook Express. Outlook Express contains the Windows Address Book files, including wab.dll, so this reinstallation will ensure that everything now works correctly.
When printing a PowerPoint presentation you may receive the above error message. The document will stop printing, meaning that you will not have a hard copy of the entire presentation. This error occurs on computers using PowerPoint 2000 Standard Edition, although may occur on other versions with a slightly different error message, but under the same circumstances.
This error is usually caused because Background Printing has been enabled on your computer. This means that a temporary version of the file is stored on your system before printing commences. It is during this process that the error occurs. To resolve the problem, disable background printing by following these instructions:
Select the Print tab
Remove the check from the Background Printing checkbox
Microsoft PowerPoint "hlink.dll" can't be loaded
Again, this problem can occur for one or more of several reasons. If the hlink.dll library, that is required by PowerPoint, has become damaged or corrupt then you will receive this error when attempting to view a PowerPoint Presentation. The library may also be missing or it may the incorrect version compared to the version that PowerPoint requires.
Resolution of this problem means the removal and addition of the hlink.dll file again. The hlink.dll library can be found on your Windows installation disk and is installed as part of the Internet Explorer installation. As such, you should first locate and delete or rename the existing hlink.dll file. Then, ensure that you have administrative privileges on your computer and remove and reinstall Internet Explorer from your installation disk. Restart your computer to refresh the required files.
There was a problem starting the Office Assistant. Would you like to try reinstalling it?
Microsoft Excel requires
file OLEAUT32.DLL to run. The version of OLEAUT32.DLL that is on your
computer is older than the one required by this version of Microsoft Excel.
Please run Setup again, and select the Reinstall option to install the correct version of the file.
The required file OUTLRPC.dll cannot be found in your path, please reinstall Microsoft Outlook.
The AGENTSVR.EXE file is linked to missing export OLEAUT32.DLL:277.
Microsoft FrontPage is
not installed properly on this system and cannot function. Please reinstall
Click OK to exit.
The file 'OLEAUT32.DLL' is out of date. This program requires a newer version.
If you receive one or more of these error messages when you attempt to open Microsoft Office applications then you have the incorrect version of oleaut32.dll installed on your system.
To resolve this issue, you may attempt to use the Detect and Repair function, install the correct version of the oleaut32.dll file or, perhaps the easiest method, download the latest security pack from the Windows website. Security packs often contain fixes and updated versions of files such as oleaut32.dll, providing you with a means to remedy many of the problems that might surface on your computer. This is especially true of older problems or problems with older versions of applications.
As you can see from this list, many of the problems are very specific to the program you are attempting to use. In some cases the error message does not necessarily indicate that the problem is associated with a dll file, while in other cases it may indicate a dll problem when the problem is associated with another file. This is why it is often best to research the exact problem that you are experiencing to ensure that you are getting the most relevant and useful information available to successfully and cleanly repair any errors.
DLL File Conclusion
Dll files are essential to the proper running of your computer. A Dynamic Link Library is essential an executable file that contains a long list of different functions. Applications and even your operating system can call a dll library and make a declaration for one specific function within this list. By doing so, the amount of code needed to perform this particular function can be greatly reduced, often replacing tens or even hundreds of lines of code with just five or six lines. This, in turn, means that the running application requires less system memory (RAM) in order to run.
Dlls are used by virtually all Windows based computers and applications, as well as a number of other operating systems. There popularity and the vast number of them that are usually included on your system makes them a prime location for system and application errors. When a dll becomes corrupt or damaged it may fail to work properly. Having the incorrect version of a dll will also cause errors, while a missing dll will almost certainly cause problems with any application that requires its use.
The registry of your computer contains a number of entries that are concerned primarily with the use of Dynamic Link Libraries. When these registry entries are incorrect you are also prone to receive errors with the use of software, hardware, or system functions that rely on making a call and declaration to these libraries. This may require the editing of the Windows registry using the registry editor. This is not advised if you do not have the knowledge of confidence to do so, because incorrectly altering the registry can cause more serious errors than you are already experiencing.
This guide is meant as an all round look at potential dll errors. We have listed some of the more common errors in order that you can learn how these errors are combated. With many thousands of different DLLs and the possibility of a number of errors for each it would be impossible to list each one in a guide of this size. Research the specific problem you are experiencing, and attempt to generate the same error again so that you may learn whether it is a specific function of an application, or the running of that application that is causing the error. Search online for help with the problem, and where necessary download and install any missing dlls onto your computer. Hopefully you should be able to resolve the error and regain a computer in fully working order.
RECOMMENDED: To Repair Dll conflicts and problems in the Windows Registry, Click "Start Download" above.