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.

No Comments »

DLL files, or Dynamic Link Library files, are the tiny resources that make it possible for our applications and programs to interact with modern day versions of Microsoft Windows. To fix DLL errors, you have to possess a good understanding of DLL files in general, and the way that we can troubleshoot these tricky errors and locate their true source on the Windows platform.

To fix DLL errors, you should know that they can occur at any time and are rarely ever obvious in the message text. That is, when you read the debugging message, it’s unlikely that you’ll know instantly where the DLL error is stemming from. Through trial and error, and a fair bit of experience, we can begin to fix DLL errors manually by simply understanding how Windows relates them.

A lot of the time, DLL errors are triggered by the incomplete removal of programs via the Windows Control Panel. Some software also have their own uninstall scripts written which for obvious reasons, can be about as effective as the developers that wrote them. It depends from program to program. What you need to remember when you fix DLL errors, however, is that not every uninstall is successful, even though it may look it on the surface if you can no longer see the program in question.

Every Windows application comes with its own batch of DLL files, and it needs them to interact with the default operating system files. However, some of these files can linger on the operating system after their parent application has been removed. Attempting to access the same memory and reference points at a later date can trigger DLL errors since Windows thinks the memory should be available, but for whatever reason, it isn’t.

Find yourself a registry scanning utility and run regular registry scans. These will help to stamp out the problems and fix DLL errors before they become a greater issue. How do you know that they’ve progressed in to a greater issue? Well, runtime errors, illegal operations performed and the dreaded blue screen of death are generally great pointers!

In some cases, to fix DLL errors e can simply rename the original DLL file that is calling the problem and then re-run the application’s installation procedure. You will notice that many of these installation scripts come with an “Upgrade/Repair” option after Windows recognises that the app is already present. By renaming the DLL file and re-running through this process, Windows will write a fresh DLL file to the system and you should be able to regain the program’s functionality.

This will help if the problem lies in a DLL file becoming corrupt. But sometimes viruses and spyware will latch on to the files making it quite a challenge to go through manually and fix DLL errors. It’s important to have good anti-virus software installed, as this will prevent malicious third party users gaining access to your DLL resources ad further damaging the operating system. You’ll find it twice as hard to fix DLL errors if spyware is present on your computer so browse the Internet safely!

No Comments »

When you install a fresh copy of Microsoft Windows, you’ll notice that all of your programs and applications seem to run so smoothly and without errors. It can be quite disheartening when a few months on, your operating system seems to have grinded to a halt with lots of applications failing to respond as they once did.

There are many reasons why your copy of Windows may be degrading in performance. DLL problems and issues with the computer registry are two of the most documented reasons for such a downturn in performance. The Windows registry sits behind the operating system as the backbone of files. It stores all the key application variables and handles configuration settings that we come to rely on.

DLL problems are just as critical as registry problems if allowed to get out of hand. DLL files are written to Windows every time we install a program. They are the libraries that sit behind our applications and allow them to perform all of their tasks. Every time we install a new program, we add a new set of DLL files to Windows. Likewise, when we remove a program or application, we hope that the DLL files associated with that particular program are removed as well.

In some cases, however, after attempting to uninstall a program, the DLL files will remain present on Windows and this can lead to some pretty drastic errors at a later date. Ensuring that you keep Windows free of stray DLLs is one of the tasks that many of the registry cleaning suites have made a priority out of.

DLL problems may be months in the making, without you knowing any better until a new application attempts to access your system memory and can’t because the same memory is corrupted by past DLLs. Keeping the PC clean is important and going back to the original point, one of the top reasons why Windows loads so much faster when you boot it up for the first time.

DLL problems can also be caused by malicious third party software latching on to the system resources. Windows likes to know what its allocating memory to, and if spyware or adware starts to leech from the memory that it previously set aside for other recognise applications, you can expect your attention to be drawn to many runtime errors and illegal operations.

Yes, those runtime errors that can plight system performance if left to develop over time. Most of us have seen them at some point, and they’re usually caused by bad registry entries or interrupted uninstall procedures. These lead on to DLL problems and if an application has DLL problems, it may terminate without warning, or simply function in a wayward manner.

The blue screen of death is another unfortunate symptom of DLL problems. Are you experiencing random blue screens while you try to run ordinary application? It could be because of DLL files being left behind, or becoming corrupted over time. Be sure that you run regular registry scans, and be extra careful when removing programs from Windows.

No Comments »

DLL files, shorted from Dynamic Link Libraries, are the important chain makers that allow us to use our Windows applications and programs and have them interact with the essential Windows registry. Without DLL files, we simply wouldn’t be able to get the functionality out of Windows that you’ve come to expect from the twenty first century. You’ve probably heard about DLL files, and you might have even seen an error relating to them, we’re going to look at what they do, how they do it, and why DLL errors are such a problematic occurrence.

As you can tell by the extended name, a DLL file isn’t actually one piece of data, but rather a link of reference points that can include many different strands of information. When you install a new program on to Windows, you need to consider that the program hasn’t been initialized before and thus without the correct working DLL files, Windows won’t know what to do with it, or how to handle its requests.

The unfortunate reality is that for all the good that DLL files can do, they can also cause a lot of problems as well. DLL errors are notoriously common, and not always easy to remove without some further investigation. Worse yet, they can be triggered without warning and called by programs where the error doesn’t necessarily lay. We have to be clever about handling our DLL files, and usually it’s best to rely on third party scanning software to decipher whether you have errors. Manual detection would take forever, and can be quite complex to fix once you’ve found an error.

Most DLL errors occur after attempting to uninstall an application from Windows. For all intensive purposes, the application may be removed according to the human eye. It’s removed from Control Panel, gone from the Start menu and disappeared completely in Program Files. But that isn’t to say that all of the DLL files related to the program are gone. And this can cause some quite significant problems, usually at a later date when Windows tries to access the same “spare memory” or “spare reference points” that are being consumed by the stray DLL file.

The simple solution to this is to have automated software in place that goes about the business of finding and removing DLL files that are outstaying their welcome on the operating system. Ensuring that you remove all DLL files with each uninstall is vital for maintaining system performance over the long term.

You can’t stop there though. DLL files can also become corrupted or damaged through other means that are slightly more malicious in their nature. Viruses and spyware are designed to latch on to stray DLL files and negatively affect the functionality of that particular file. Third party hackers and bug creators have spotted the weakness in DLL files, and often see them as a way of controlling the Windows system, which is exactly what they’re capable of doing to a certain extent.

Having anti-virus software installed and a good spyware scanning utility should be seen as the first step towards preserving your all important DLL files.

No Comments »