If you install Windows XP, Vista or Windows 7 or have been forced to reinstall Windows and one of more device drivers were not installed and the Device Manager did not provide enough information to be able to identify the hardware to be able to obtain the drivers from the device manufacturers' website, to make good, you can make use of the free PC Wizard tool from http://www.cpuid.com/softwares/pc-wizard.html that provides a wealth of system information.
DLL or Dynamic Link Library files (files with a .dll extension) are used by Windows 98/Me/2000/XP/Vista/ Windows 7/Windows 8 and the applications installed on them to store functions and code that can be used whenever required. There are typically several hundred DLL files on a Windows system and several conditions that may result in DLL problems and errors. The most common causes are: missing, corrupt, or damaged DLL files - overwriting or deletion of one or more DLLs during program installation or uninstallation - faulty or corrupt applications - malware (spyware, worms, virus) infections - erroneous or invalid entries in the Windows Registry, the editor of which you run by entering regedit in the Start -> Run box in Windows XP and in the Start -> Start Search box in Windows Vista.
This page provides a few typical DLL problems. If you don't find any information here that is of any use to you, try entering the name of the DLL file that is named in an error message, if necessary followed by the version of Windows, in a search engine. - E.g., msvcr71.dll. You can also find pages such as this one:
Common DLL Errors and Fixes in Windows Vista -
"When trying to run a program, an error popped up indicating CNCS232.dll was missing or corrupted. I entered the file's name in a search engine to find it on the web, and then saved it to the Windows/System folder, and the problem was fixed. You can also use sites such as DLL Downloads - http://www.dll-downloads.com/."
Click here! to read the Q&A Missing DLLs on this page.
You can make use a search engine to find other such sites.
DLL - Resolving MS DLL version conflicts:
Different Microsoft applications can install different versions of the same DLL and this can often create major problems. If you get a DLL error message when using a particular Microsoft application, note the name of the DLL and then enter its name followed by the name of the application to find the information that is avialableon the web. The Microsoft DLL Help Database, which was very helpful in sorting out DLL problems with Microsoft's applications only supported Windows XP up to SP3, but, unfortunately, it has been retired.
This article describes the Windows File Protection (WFP) feature in Windows XP and Windows 2000. Windows File Protection (WFP) prevents programs from replacing critical Windows system files. Programs must not overwrite these files because they are used by the operating system and by other programs. Protecting these files prevents problems with programs and the operating system. WFP protects critical system files that are installed as part of Windows (for example, files with a .dll, .exe, .ocx, and .sys extension and some True Type fonts). WFP uses the file signatures and catalog files that are generated by code signing to verify if protected system files are the correct Microsoft versions. Replacement of protected system files is supported only through the following mechanisms: • Windows Service Pack installation using Update.exe • Hotfixes installed using Hotfix.exe or Update.exe • Operating system upgrades using Winnt32.exe • Windows Update. - http://support.microsoft.com/?kbid=222193
The following DLL problem pertains to Windows 9.x (95/98/Me), but contains the kind of information that can be used to fix a DLL problem in any later version of Windows, because the nature of DLL problems have remained more or less the same since Windows 9x were being used.
You have purchased a Minolta QMS PagePro 1100L mono laser printer. Unfortunately, the installation routine seems to have corrupted the system, which is issuing the following confusing message:
The MSVCP60.dll is linked to the missing export MSVCRT:dll:_lc_collate_cp.
Consequently, the printer works erratically, and several other applications that use the files, such as MS Works and Serif PagePlus 8, refuse to work.
You have downloaded and installed the updates from the Minolta website , and you have read the Knowledge Base article - 240032 - that addresses this problem in MS Office 2000, in vain. You want to know how to rectify the problem.
The message comes up because the copy of Msvcrt.dll is incompatible with the copy of Msvcp60.dll, most probably because one of them (probably Msvcrt.dll) is an old version. Both of these files are part of the Microsoft Visual C compiler run-time library.
It is a protocol of software installation programming that an application should never replace a new file by an older version. However, when it was installed, it is still possible that the printer driver may have overwritten the Msvcrt.dll file in the Windows\System folder with an older version. But it is more likely that the driver installation software has installed an old version of the file in its own folder, and it is this version that loads when a printer-monitor utility starts up with the rest of the system, because an application always searches in its own folder for the DLL files it needs before looking in the Windows and Windows\System folders.
The problem occurs when other applications that use this DLL library search the RAM to see if it is already loaded (all device-drivers are loaded into RAM). If the application finds it in RAM, it uses that version. So if an old version of a DLL file is loaded at start-up by a device driver, all of the applications that use it will use that version instead of using the newer version in the Windows or Windows\System folders.
To view the versions of modules (DLL and driver files) loaded into RAM in a Windows 9.x system, go to Start => Programs => Accessories => System Tools and run System Information. You can see the list of 32-bit modules loaded under the heading Software Environment. The version and the exact path from which it was loaded is provided. Look for system library files that are located outside the Windows\System folder.
Next, use the Find => Files or Folders feature to locate the msvc*.dll files. With View => Details enabled, sort the files alphabetically by clicking the Name column header.
Don't rely on the file date shown to tell you which of the files is the newest version, because the date of the file is often set to the same date as the date the whole package was released or completed. If you right-click on each of the files and click Properties, the Version tab provides the exact version number.
The version of Msvcrt.dll included with Windows 98 SE is 6.008397.0. The 6.00 indicates that it was distributed with the Visual C 6.0 file library, but the important version information is the 8397. If you find a newer, higher version on your computer, it just means that the file has been updated.
You should find that there are several versions of this file in different locations. Check for the latest version, and copy it into the Windows\System folder. If you can't find a later version than the one in use, you can try entering sfc in the Start => Run box to run the System File Checker (SFC), which can be used to extract the original version from the Windows CD's cabinet (.cab) files.
Click here! to go to information on this site on how to use the SFC in Windows XP, Vista and Windows 7.
See the solution to a DLL problem with Windows XP below...
I'm running Windows XP Pro and I've been having a particular crash problem for quite awhile now, and finally fixed it today.
It usually happened when opening Windows Explorer windows, all of a sudden all Explorer windows would close and I would get one of those "send or "don't send" messages that said: AppName: explorer.exe AppVer: 6.0.2800.1106 ModName: mfc42.dll ModVer: 6.0.8665.0 Offset: 00001b3e
Also, my whole desktop would disappear and then reappear shortly thereafter, minus some of my System Tray icons. Needless to say, this was a major pain in my rear. The first thing I did was a repair of XP so I could be sure that the copy of mfc42.dll that resides in the C:\Windows\System32 directory was good.
This alone didn't fix the problem and I verified that by opening various Explorer windows such as, My Computer, Recycle Bin, Windows Explorer, etc. After opening and closing about 3 or 4 of them, I got the same error.
The next thing I did was to do a search on my hard drive for the file mfc42.dll. It came up with about 5 of them, one in a game folder, and a few in some programs. I noticed that they were all different versions, so I just renamed all of them except the one in C:\Windows\System32 to mfc42.old.
I'm pretty convinced that this has fixed my crashing problem, which has been going on for months. I have continuously opened and closed various Explorer windows and not a single crash yet. I normally would have had several by now.
I've tried all the programs with the renamed mfc42.dll's also and they seem to work perfectly so far. I'm so happy now. Hope this helps someone.
Here are a few programs that install that DLL. Norton Utilities, 3D Mark 2001 and SE, HP printer driver and software, Nero, Easy CD Creator, Max Payne, Ulead Photo Explorer, Logitech Mousewares, Creative SBlive Playcenter, and it could also be part of some Creative Labs drivers.
I am having a lot of problems with my PC. It only connects to some websites. Every time I try to install something, error messages say that I have a dll missing. My Internet service provider isn't interested in using e-mail and it costs me a pound per minute to phone them. I am a single mother and I can't afford this. As it is I have already been conned. I bought Windows XP only to find out that it is a copy, and now the shop has gone out of business, so I can't return it. I am a novice with computers but will try anything you can suggest that gets me back on line properly.
If an error message tells you what software is having problems, you can try to repair it or remove and reinstall it. Most programs provide an uninstaller that can be launched from the program by accessing it via Start => All Programs. If not, uninstall it via Add or Remove Programs in the Control Panel.
However, if it's Internet Explorer that's generating the error message, you can't uninstall it, because it is currently built into Windows. There are ways of uninstalling it provided on the web, but it isn't usually necessary to remove it, because it can usually be fixed. Try the steps listed here:
How to reinstall or repair Internet Explorer in Windows 7, Windows Vista, and Windows XP -
To find links to more system-relevant information, enter the search query repair internet explorer followed by the version of Windows being used in a search engine.
If it is some other component generating the error message, you can enter the relevant search terms in a search engine.
If the error message names a particular DLL file, such as MSVCP60.dll, you could try entering: fix msvcp60.dll problem.
If doing that doesn't work, you can try searching for the specific DLL that is missing. For example, if the error message says: MSVCP60.dll missing or corrupt or something similar naming another DLL file, try entering "MSVCP60.dll download" (including the quotation marks) in order to find a site that provides a download of the particular DLL file in question. A number of sites offer downloads of common DLLs, including this one - DLL Downloads - http://www.dll-downloads.com/ - found by using the search query dll downloads.
The error message usually tells you where the missing file should be. You just have to browse to the folder by opening Windows Explorer (right-click the Start button with the mouse pointer on the Start button and click Explore). If that information isn't provided, try copying the missing DLL file into the C:\Windows\System32 folder, where Windows stores most of its DLLs, and, if the name of a program is provided, copy the file into the program's folder that contains other DLL files. Some programs use the C:\Windows\System32 folder to store their DLLs, and others use their own folder.
If the missing DLL file is another system file, such as the Shell.dll file, it will probably also be in the System32 folder.
In case the missing DLL file problem has been caused by malware (a virus, spyware, etc.), you should first run your antivirus/malware scanners to clean the system before you restore a new copy of the file to that folder, because if the malware has not been removed, it will just corrupt the new file again. Visit the Security pages on this site for information on suitable virus and spyware scanners.
You then re-register the new copy of the DLL file as follows:
1. Click Start => Run.
2. Enter regsvr32 C:\Windows\System32\msvcp60.dll in the Run box. You may have to change C:\Windows to the correct drive location of the folder that Windows is installed in on your system if it isn't a default installation.
3. Click OK.
4. Reboot and problem should be fixed.
You can also try using System Restore under Start => All Programs => Accessories => System Tools.
Click here! to go to information on System Restore, which is used by Windows XP, Vista, Windows 7 & 8, on this website.
Restore a restore point that pre-dates the problem, which would roll back the system to an unproblematic state. If you had a backup or master image of the system, you could also restore that, so think about investing in some CD-R or DVD-R discs (preferably the latter kind because of their much greater capacity). The PC must have a CD or DVD writer that supports the recordable discs that you want to use. Click here! to go to information on CD and DVD drives on this site. Click here! to go to the information on creating backups on this site.
Here is an excellent, free imaging application:
DriveImage XML - Image and Backup logical Drives and Partitions -