OLEAUT32.DLL
DLL errors related to the oleaut32.dll file are usually caused by an incorrect version of this particular DLL file being installed on the operating system. The error is triggered when you attempt to run a Microsoft Office product, although some programs will run better than others. You’re most likely to see the oleaut32.dll error when running Microsoft Excel.

HLINK.DLL
DLL errors sprung from the hlink.dll library are typically found when attempting to view a Powerpoint presentation on Microsoft Windows. The file may have become corrupt, or could require updating to function effectively. You can update your hlink.dll file by downloading the latest Windows security package, or by running the installation package that comes with Internet Exporer. The old hlink.dll file should be removed first.

WAB.DLL
The wab.dll error is usually accompanied by a message stating that the file is missing. This could be down to a corrupt version of the file exiting, or it may have been deleted by access. To resolve these kinds of DLL errors, you will need to rename the old wab.dll file and then re-install Outlook Express. The re-installation will write a fresh working version of the wab.dll to your system.

OMINT.DLL
DLL errors that produce a message stating that the required component omint.dll is missing are usually restricted to older versions of Outlook Express. If you are trying to run Outlook Express 98, for example, you may find that your version of the omint.dll file is newer than the application itself. In this case, you will need to roll back to an older version. It’s also possible that the registry entries have become corrupted.

GWMSPI.DLL
The gwmspi.dll error message is caused by a conflict between two applications. These applications are Microsoft Outlook 2000 (standard edition only), and Novell. You will need to create two separate messaging profiles to get rid of DLL errors such as this. Uninstall one of the two applications and then install from scratch as an additional method of fixing the error.

RICHED20.DLL
When accessing Microsoft Outlook, you may notice an access violation DLL error related to the riched20.dll file. This shows that the file has become corrupt and you will need to repair Microsoft Outlook to fix the problem. Before you run the repair function, be sure to rename the riched20.dll file so as not to compromise the effectiveness of the repair.

MSVCP60.DLL
DLL errors tied to the msvcp60.dll file are notoriously hard to repair and usually require the complete re-installation of the Microsoft operating system. The error appears when trying to run features of Clip Gallery 5.0 in particular.

WMP.EXE
If you encounter an error related to the wmp.exe file, you could easily be misled in to believing that you have a problem with Windows Media Player itself. This is false. The problem actually stems from the DLL library associated to the program. You will need to re-register WMP.DLL to fix the problem, and can do so from the Run command on recent versions of Windows.

WMPDXM.DLL
DLL errors are quite common with Windows Media Player versions 9 and 10. The wmpdxm.dll error is directly related to the media player, as you’d expect, and is usually caused by the DLL file not being registered. To fix, you should attempt to re-register the DLL file. In some cases, a fresh version may be required as the DLL may have become corrupted or deleted.

MSI.DLL
If you’re trying to install a Microsoft Office product, and receive an msi.dll error, it’s likely that you will need to update Microsoft Installer which relies on the DLL file. The problem can be caused by a download being interrupted or by one of many types of corruptions. Visit the Microsoft website and upgrade your Installer to the latest version to resolve the error.

OFFICEAV.DLL
DLL errors related to the officeav.dll file are triggered when attempting to open a document in Microsoft Word while having a damaged officeav.dll library. The file is typically sound in the Norton add-on that caters for Microsoft products. You can fix the error by renaming the officeav.dll file and then re-activating the Norton plugin.

OLE32.DLL
The ole32.dll error may appear when attempting to add a clipart image to your open Word document. DLL errors such as this are usually caused by the ole32.dll library not being registered correctly on the Windows operating system. You can try re-registering the file, but if this doesn’t work, a complete Windows re-install may be necessary.

DLBAPRP.DLL
If you have Lexmark or Dell printers installed on your system, you may eventually encounter DLL errors related to the dlbaprp.dll file. This typically appears when you try to print or save a document in Microsoft Word. Besides from contacting the manufacturer directly, you can attempt to fix this DLL error by copying your key printer DLL files and placing them in the Windows/System32 folder.

HPAFD32.DLL
DLL errors linked to the hpafd32.dll file will cause Microsoft Word to close suddenly and without prior warning. The error is caused after a user has been using an HP printer model 1200 or 3200, and subsequently attempts to update to a newer model from HP. The installation won’t automatically update the hpafd32.dll file, and thus the printer will have problems. A driver upgrade is necessary.

MSVCRT.DLL
If your program has caused an illegal operation and been forced to shut down because of a msvcrt.dll error, it’s likely that your DLL files for the Word add-in with Microsoft Works have become corrupt. You should deactivate the Word plug-in before restoring it. This will force new copies of the files and will fix the DLL errors in most cases.

MSJAVA.DLL
The msjava.dll error is caused when you access a web page that attempts to load a script which the browser isn’t capable of handling. DLL errors related to the Java virtual machine, like this one, can usually be fixed by updating to the newest version of the JVM. Also ensure that you actually have scripting enabled in your Internet Explorer settings.

KERNEL32.DLL
The kernel32.dll error is generally caused by MacAfee software which runs a quick scan when you close a window in Internet Explorer, and occasionally Microsoft Outlook. The best way to get rid of these kinds of DLL errors is to access the MacAfee software directly and disable these scanning features.

ACTXPRXY.DLL
DLL errors related to the actxprxy.dll library are triggered when the user tries to open a fresh window in Internet Explorer, but the browser crashes and throws an error instead. Unfortunately, these DLL errors are related to the Windows registry itself and may be a giveaway sign that you’ve got several corruptions in the core files. Consider a registry scanning tool which should help to get rid of bad entries and fix this variety of DLL errors.

MSHTML.DLL
This is one of a select few very rare DLL errors that you shouldn’t be experiencing unless you’re running the extremely outdated Internet Explorer version 5.5 or earlier. The mshtml.dll error can be triggered by IE settings which involve the use of high or true colours. To fix, simply reset your settings to use 256 colours in the colour palette. Alternatively, you can upgrade your video card drivers via the manufacturer’s website.

SHELL64.DLL
Occasionally, you may encounter an error in Internet Explorer stating that the application has struck an error and will need to close. The shell64.dll error is caused in Internet Explorer version 6 when a third party program attempts to attach itself on to the browser and write a separate shell64.dll file to the system folder. Delete or rename the file to fix the problem.