Hi
mickhart
Ztruker may be stopping by later with the same or better information.
I'm replying in case you can use the information now, and quickly get back to your Malware Removal Thread to complete that work.
C:\Windows\System32 is a protected folder in which Windows keeps various registered executable files that activate or support your machines operating system and third-party applications.
As such, it is a favorite target for the bad-guys to alter the victims machine functioning.
C:\Windows\System32\dll cache is a protected and non-active "holding" folder in which original copies of executable .dll files that are either registered or have been accepted by the owner/user, can be stored.
Whenever an executable file in System32 becomes corrupted, either by ordinary foul-ups during use, or intentionally change via malware infection, Windows attempts to replace an original of the .dll from the dll cache.
Each time Windows boots up, it reads the dll cache file to compare the contents to registered dll files in System32\
Windows File Protection will automatically attempt to correct any corrupted or missing dll files by copying form dll cache.
It is "unusual" to say the least, that you are unable to find your C:\Windows\System32\dll cache\ folder.
It should be listed "alphabetically" under C:\Windows\System32\ in the list of Folders contained in that parent Folder.
I suppose it could have been damaged/removed by the malware infection, though I am unable to confirm or deny if that is the case in your situation.
Ztruker has reported that the wininet.dll file reported from his machine is 894KB
Yours is reported as 890KB
I looked wininet.dll up on a Desktop XP pro Dell machine and found it to be 807kb (created 12/20/2008)
I looked wininet.dll up on a Desktop XP home Compaq machine and found it to be 807kb (created 12/20/2008)
I looked wininet.dll up on a Desktop XP pro Dell Laptop machine and found it to be 894kb (created 03/08/2009)
Yours, listed as 890KB, is not necessarily corrupted, and may be that size due to your own machine brand/type and the date on which it was created….
But I wouldn't rely on it, simply because you have had associated problems reported via your work in Malware Removal.
___________________
So what to do?
As you previously stated, you can safely download wininet.dll from internet sources.
I'd suggest this free source (and I urge you to ignore all the handy for-fee utilities that they offer)
http://www.dll-files.com/dllindex/dll-files.shtml?wininet
wininet.dll is also available on your Windows XP Installation CD (and a couple of other places hidden on your machine that we can look for if necessary)
Do you have a legitimate Windows XP Installation CD?
____________________-
How-To:
If you
download wininet.dll….
Save it to it's own temporary folder.
Double-click on the zipped file to allow Windows to expand it.
Select for it to
expand and save it into the
same temporary folder.
Next:
Rename the current wininet.dll (the one in your System32 folder) –> to
wininet.old
Next:
Copy/paste the fresh wininet.dll into C:\Windows\System32\
For now:
Leave the "renamed" wininet.old where it is. It will cause no problem, and Windows will simply ignore it.
Next:
Reboot your machine and carry on with your previous intended activities.
_____________________
Additional work to be done….
If you really do not find a
dll cache Folder listed in your C:\Windows\System32\ folder…
It should be replaced.
Windows File Protection system has a feature known as SFC (System File Checker) which is a built in utility to check all of the Windows operating system files and folders. If a file or folder is missing or corrupted, Windows will search for a Windows XP Installation CD source from which to copy and replace the missing or corrupted file or folder.
SFC is performed as follows:
System File Checker -
sfc /scannow can only be run in Normal mode.
Boot Normally
GoTo:
Start - Run - (type)
sfc /scannow - Enter <— Notice the space between "c" and "/"
Have your XP installation CD handy since SFC will call for it to copy and replace missing or corrupt files.
SFC typically takes more than 2 minutes and less than 10 minutes.
If SFC opens and closes in less than 1 minute, then it did not perform.
Let us know.
_________________
There is a "work-around" in case you do not have a Windows XP installation CD
Let us know.
Best Regards,
Doug