my computer/c/(any folder) = Search Results window

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Running Win XP Pro on HP Pavilion zv5000 laptop. This just started -
when I click on My Computer, then any drive, then any folder, the Search
Results window comes up, not the contents of that folder. Any ideas.
This doesn't happen if I go through Windows Explorer. (not IE)

I have an 80 gb dive partitioned into 3 virtual drives: Windows in C,
programs in D, Documents and graphics, and swap in E.

JR

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

David Candy wrote:
> Type in Start Run
> regsvr32 /i shell32
>
>
Thank you!!! It's fixed now. What might have caused this to happen in
the first place and what exactly did this command to? I'm always trying
to learn.

Thanks.

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Issue: Search Companion Starts If You Double-Click a Folder

This problem occurs when you alter the "Drive" / "File Folders" entries via
File Types dialog, to add a "Command Prompt here" or "Print Directory"
feature for folders. (example)

http://support.microsoft.com/?kbid=321379
http://support.microsoft.com/?kbid=321186

Resolution:

Click Start/Run and type this command to fix this problem:
(Tip from David Candy)

regsvr32 /i shell32.dll

-or-

To fix this manually via registry:

If this problem is seen for Drives:

HKEY_CLASSES_ROOT\Drive\shell
Set (default) to "none" (without " )

If this problem is seen for folders:

[HKEY_CLASSES_ROOT\Directory\shell]
Set (default) to "none" (without " )



--
Ramesh, MS-MVP
Windows Shell/User

Windows XP Troubleshooting
http://www.winhelponline.com
http://windowsxp.mvps.org

Windows XP Newsgroup Setup Instructions for Outlook Express:
http://www.microsoft.com/windowsxp [...] setup.mspx


"JR" <jgreid1notat@yahoo.com> wrote in message
news:Jq3ve.50398$j51.5225@tornado.texas.rr.com...
> David Candy wrote:
>> Type in Start Run regsvr32 /i shell32
>>
>>
> Thank you!!! It's fixed now. What might have caused this to happen in the
> first place and what exactly did this command to? I'm always trying to
> learn.
>
> Thanks.