The shell32.dll file may be corrupted. Replace it (and any other missing or corrupted system files) by going to Start|Run, entering
sfc /scannow (space before /) and clicking OK.
I have already tried that. There is no report given after sfc so I dont know if it made any changes to the files. The problem remained afterwards though.
Denny Denham
2 Intern
•
18.8K Posts
0
June 29th, 2005 17:00
The shell32.dll file may be corrupted. Replace it (and any other missing or corrupted system files) by going to Start|Run, entering sfc /scannow (space before /) and clicking OK.
David_UK
28 Posts
0
July 1st, 2005 07:00
Thanks Denny
I have already tried that. There is no report given after sfc so I dont know if it made any changes to the files. The problem remained afterwards though.