Thanks again a lot for your further help & Best Regards,
Iudith Mentzel
Let's get some more information and do some things to get to a basic
starting point. While you do this, I will be looking at some other
things.
The shell32.dll file on your XP CD would be compressed so I don't know
how it can "look" like your one in system32, but we can easily let
Windows File Protection replace the one in system32 with what XP
thinks is a "good" copy. It is a "protected file" and if it ever
comes up missing, XP will want to replace it, so we'll make it missing
by renaming it.
Navigate to windows\system32 and rename shell32.dll --> shell32.tmp
(or some extension you can remember).
Within a few to several seconds WFP will replace the missing
shell32.dll file and put a message like this in the System Event Log:
Event Type: Information
Event Source: Windows File Protection
Event Category: None
Event ID: 64002
Description:
File replacement was attempted on the protected system file c:\windows
\system32\shell32.dll. This file was restored to the original version
to maintain system stability. The file version of the system file is
6.0.2900.5622.
Now you have what should be a "good" shell32.dll file so that will not
be a question about that. If that doesn't work and shell32.dll
doesn't reappear (refresh), you have another problem so put your old
one back.
I don't use ZA these days, but I am thinking if it may interfere with
this rename or WFP process, we need to start looking at ZA a bit. It
has a lot of configuration options and installed out of the box (or
out of the download) sometimes contributes to peculiar behavior until
it is tweaked for your system. I may be fine, but we'll see...
You may also be thinking about how to completely disable ZA long
enough to see if your problem goes away without ZA running. It would
be good if you could say: With ZA running, I have this problem.
With ZA not running, I have do not have this problem. Then we will fix
it if it needs fixing.
We should also try to catch the system when it is broken and easiest
to troubleshoot (not after a reboot) - so when you see your problem
and the shell32.dll error look in the XP Event Log for error messages
when it is broken. Here is how to do that:
Here is a method to post the specific information about individual
events.
To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.
A shortcut to Event Viewer is to click Start, Run and in the box
enter:
%SystemRoot%\system32\eventvwr.msc /s
Click OK to launch the Event Viewer.
The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.
Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.
If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.
When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.
To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.
Finally continue with more information from you and some other scans:
To eliminate questions and guessing, please provide additional
information about your system.
Click Start, Run and in the box enter:
msinfo32
Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
the information back here.
There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete it from the pasted
information.
Perform some scans for malicious software, then fix any remaining
issues:
Download, install, update and do a full scan with these free malware
detection programs:
Malwarebytes (MBAM):
http://malwarebytes.org/
SUPERAntiSpyware: (SAS):
http://www.superantispyware.com/
They can be uninstalled later if desired.