Article ID: 321186 - View products that this article applies to.
This article was previously published under Q321186
If you double-click a drive or folder, Search Companion may start and the drive or folder may not open. If you configure settings for other actions that are associated with drives or file folders (for example, Open Command Window Here or Print Directory Listing), Windows may perform one of these actions instead of starting Search Companion.
NOTE: If you configure the Single-click to open an item (point to select) setting in Windows, this problem may occur if you single-click a drive or folder.
This problem occurs when you open the Edit File Type dialog box for the Drive or File Folder registered file types. For example, this problem occurs for folders if you complete the following procedure:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To have us fix this problem for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.
Fix it for me
To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run and then follow the steps in the Fix it Wizard.
Fix this problem
Microsoft Fix it 50665
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfTo resolve this problem, edit the registry to set the value data for the Default string value in the registry keys that are described in the "Cause" section of this article to none:
Did this fix the problem?
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.