Windows XP pulling out the wrong DLLs in the system

In Windows, a DLL (dynamic-link library) file is used by almost all applications, and its normal or not is related to whether the software works properly. Many software failures are also directly related to it. But the application will often call dozens of DLL programs, how to determine who is the "culprit"?

Case playback: After an illegal operation, the Windows XP Search Companion becomes a whiteboard, and the user account item in Control Panel also appears "Expressionless". Click "Start → help and support", the mouse flashes but always missing the "Help and Support" program interface traces.

Case study: By feeling, I think that a DLL file in the system has been cancelled, lost or corrupted. But almost every program in Windows calls into hundreds of DLL files, and if you look for an analysis in the usual way, it's a haystack. Considering that three programs are "disfigured" at the same time, they should be affected by the same (or several) DLL files. To do this, you must find the DLL files that are used together by these three programs, and then find out "the real culprit behind the scenes."

Find and compare pairs

The first step: first from the "Search Assistant" to start, to find out its "origin". In another computer with Windows XP, open Search Companion, press Ctrl+alt+del to bring up Task Manager, select Search Companion in the Application tab, select Go to process, hehe, it is Explorer.exe, oh, it is. Resource manager).

Step two: In a similar way, it can be learned that "help and support" belong to the process Helpctr.exe, but in the "user account" it is only possible to find out the attribution process Mshta.exe by means of observation and comparison.

Small Tips

You can determine which process is owned by comparing the changes in Task Manager by opening and closing the user account method, or by typing "tasklist/fo table>c:\acc1.txt" in the command prompt when you open Search Companion, after you close the program "Tasklist/fo table>c:\acc2.txt" in the command prompt, and then compare FC C:\acc1.txt C:\acc2.txt>c:\acc.txt with the FC command. The remainder of the comparison is the process to which the program belongs.

The third step: Restart the computer, the following to please software listdlls out. Download the software here, then move ListDLLs.exe to C:\Windows, press Ctrl+r to open the "Run" box, enter "CMD", and in the command prompt, enter:

Listdlls-r Explorer.exe>c:\explorer1.txt.

Next, open Search Companion and enter at the command prompt again:

Listdlls-r Explorer.exe>c:\explorer2.txt

Finally, the FC command is used to compare:

FC C:\explorer1.txt C:\explorer2.txt>c:\explorer.txt.

This opens the C:\explorer.txt file, which is the DLL file that the Search Companion invokes.