bad dll

[jgmic1989]

I keep getting a message system32\shfolder.dll is either not desinged to run
on windows or it contains an error. Think I have a bad dll, don't know how
it happend, or how to fix it. tried system recovery but recovery point is
not old enough to recover to a point before this started.

 

[Andrew McLaren]

I keep getting a message system32\shfolder.dll is either not desinged to
run
on windows or it contains an error. Think I have a bad dll, don't know
how
it happend, or how to fix it. tried system recovery but recovery point is
not old enough to recover to a point before this started.

Hi jgmic

Go to Start Menu, Accessories, and find the Command Prompt icon. Right-click
the icon and select "Run as Administrator" from the context menu. Give the
administrative consent, when prompted. A command prompt window will now
open.

At the command prompt, run this command:

sfc /scannow

and press <enter>. "Sfc" is "system file check", this command will walk
through all your system files to verify that they are in good shape. If
shfolder.dll is damaged or missing, then sfc will replace it.

If that doesn't fix it, you'd better report back with the size, time and
date, and version number of your shfolder.dll file; and whether you have
32-bit or 64-bit Vista (probably 32-bit - if you have 64-bit Vista
installed, you'd certainly know about it).

 

[uvbogden]

See details in this tutorial.

http://www.vistax64.com/tutorials/101393-repair-vista-options-preferred-sequence.html

 

[jgmic1989]

I ran the sfc command, and if found corrupted files, and put them in a log, I
thought I could cd to the directory, but I guess my pc skills are more
limited than I though. Anyhow decided to call Dell, where I got my pc, the
gal on the phone talked me through stopping everything at startup, the
message went away, and I am now able to launch programs I could not before.
SO what would you suggest as next steps, things are running fine now.........

 

[Andrew McLaren]

I ran the sfc command, and if found corrupted files, and put them in a log,
I
thought I could cd to the directory, but I guess my pc skills are more
limited than I though. Anyhow decided to call Dell, where I got my pc,
the
gal on the phone talked me through stopping everything at startup, the
message went away, and I am now able to launch programs I could not
before.
SO what would you suggest as next steps, things are running fine
now.........

If things are running fine now, it sounds like the problem is solved?

The sfc command will repair the files, as it runs. Sfc creates a cbs.log
file, but you don't need to do anything with the log; it's just there for
post-mortem analysis.