1. When confronted with a DLL file problem, a copy of some Microsoft media may already be owned from which the file can be extracted, "Definition and Explanation of a .DLL file (Q87934)".
2. To determine whether the file is a Microsoft issue, access the "DLL Help Database", enter the file name -- including extension in the space provided, select the operating system and then press Enter (correct spelling and punctuation is recommended). If a list is rendered, simply determine from what is shown that you currently owned and then extract a copy, "Description and Explanation of a Cabinet File (Q310435)".
NOTE: You can click the Details button to the left of the file names which renders an explanation of the file wanted and may show a list of files which are dependencies. Unfortunately, this site does not show where an extracted file resides on the computer.
Tracking the threads for the past several days I see where you're dealing with a .dll file here and there and really wonder if your box is going to be fixed. If you had the XPCD and could use System File Checker perhaps everything could be ironed out in one pass. For instance, the .dll file in your first post was successfully extracted and placed in the \Windows\System32 folder. Please note that my similar system has that .dll file:
\Windows\System32
\Windows\ServicePackFiles\I386
\Windows\System32\dllcache
Two of the following folders with long numbers at the end:
\WINDOWS\WinSxS\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries
After we deal with one file I'm often concerned whether the file we're trying to recover also has other dependency files (#2 above) which are also either missing or corrupted.
Just a suggestion and that is to search for files leaving the extension off and simply add a * (asterisk) after the period.
If you ever get the chance to use it:
1. The article [Q310747] describes the Beta release of System File Checker (Sfc.exe), a command-line tool that examines protected system files and restores the correct versions by using backups stored in the Dllcache folder or files copied from the operating system CD. Protected files include those with .sys, .dll, .exe, .ttf, .fon and .ocx file name extensions. Due to disk space considerations, storing all protected files in the Dllcache folder might not be practical especially on computers with limited storage space. Therefore, the system may require and prompt for the operating system CD. In addition, SFC can be used to repopulate the %Systemroot%\System32\Dllcache folder if the contents become damaged or unusable.
2. Recommended reading and important to understand are these five articles:
a. "Description of the Windows File Protection Feature (Q222193)."
b. "System Files Reference."
c. "Windows File Protection and Windows" which explains that WFP prevents programs from replacing critical system files which must not be overwritten that are used by the OS and by other programs. Please note that WFP may record events to the system event log noting file replacement attempt that may lead to concluding certain anomalies.
d. "Registry Settings for Windows File Protection and System File Checker (Q222473)."
e. Also note, "Replacing files protected by the Windows File Protection (Q555486)" which explaining how to replace files, which you may never need to know or use.
Caveats: The WFP cache (%systemroot%\system32\dllcache) is not protected and its files can be overwritten either using the Windows Explorer or the command prompt. Since the folder is a compressed system folder, it is necessary to disable the Hide protected operating system files option in the global folder options to see the folder in Windows Explorer or in a directory listing.
3. The article [Q900910] discusses the situation and explains the correction process of when you try to run SFC on an updated WinXP-based computer to WinXP-SP2/3, you may be prompted to insert the SP2/3 CD and that SFC may not accept the fact that you have either or both the SP CDs or the original WinXP CD.
Note: The bottom line is that SFC expects to find something...which isn't...because WinXP was installed sometime in the past and now that OS has been updated through "service packs" and you therefore do not have a CD containing all that information. If the information is on the hard drive however, edit the registry as suggested in item 2a above.
CAVEAT: "If a Service Pack is installed by means of a CD-ROM or a distribution share, the ServicePackFiles directory is not created."