Hello everyone. For sometime now I have had problems from time to time with DLL errors and Windows Explorer closing on me on my old HP Desktop PC running
Windows XP Media Center with SP3. I first thought the problem was bad RAM, but after running various scans I came to believe it is a problem with a number of corrupted DLL files found by sfc. I do not have XP SP3 on disc, and I really don't want to replace
those DLL files from disc anyway as I want to find clean copies in the exact versions I have. So, I downloaded a program called DLL Files Fixer that you can use to fix registry errors and defrag the registry. You can also search through their database for
clean copies of corrupted DLL files found on your computer. I got in contact with the tech guys at DLL Files Fixer and they sent back instructions on how to determine which DLL files sfc found as corrupt and determine which versions they are in. They told
me once I knew which DLL files I needed and in what versions I could search through their database for them and if I couldn't find them they would try to find them for me elsewhere. But now I am having a problem with sfc. It is supposed to create a file called
cbs.log in C:Windows\Logs where it logs all of its operations but for some reason it is not creating that log file for me when I run sfc. I don't know if the logging feature is just turned off or what. If it is I would sure like to know how to turn it on.
So, I followed some instructions I found on another forum to create an environment variable that tells sfc where to put the log file, but that didn't work for me. I then discovered those instructions were for Vista only. Could it be that there is another environment
variable sfc uses on XP that I don't have set? If so I could not find anything about it on Microsoft forums for Windows XP. Anyhow, in attempt to fix the problem I tried changing the cache file size for sfc with sfc /cachesize=100 to set the cache size to
100 MB. I then rebooted and ran sfc /purgecache to get it to actually change the cache file size. I then ran sfc /scannow. Now it is only finding 3 corrupted DLL files, as opposed to the 14 it was finding before. If those other DLL files it found as corrupted
earlier are still corrupted I would sure like to know it, and which ones they are and in what versions. But I can't figure anything out without sfc logging its operations for me. I did a search through the registry for sfc and I did discover that a number
off registry entries for sfc are missing. Entries that record various settings for sfc. Could that be the problem? If anybody could help me out I would appreciate it. Thanks in advance.
↧