This article was previously published under Q319949
This article has been archived. It is offered "as is" and will no longer be updated.
After you connect to a Web site, you may receive the following error message:
A file that is required to run search companion cannot be found. You may need to run setup.
After you receive this error message, you cannot use Search Companion to search for files or folders, or to search the Internet. The options to search for files or folders, or to search the Internet, are unavailable.
This behavior can occur if a file required to run Search Companion is missing or damaged. Note that this problem affects only the English-language version of Windows XP.
NOTE: Search Companion files may be damaged if you have Search Companion open when you connect to certain Internet Service Providers.
To resolve this problem, use one of the following methods.
Method 1: Install Windows XP SP1
Method 2: Reinstall the Search Companion Files
To resolve this problem without obtaining the hotfix or installing Windows XP SP1, follow these steps:
Log on to the computer by using an account with administrator permissions.
Click Start, click Run, type %systemroot%\inf, and then click OK.
Locate the Srchasst.inf file.
Right-click the Srchasst.inf file, and then click Install. This reinstalls the files that Search Companion uses.
NOTE: You may need your Windows XP CD-ROM to finish installing Search Companion. This issue may occur again if you have Search Companion open when you connect to your ISP.
The problem may continue to occur after you disconnect from the Internet because the files that have been corrupted are cached. You can view the appropriate files (open them with Notepad, not Microsoft Internet Explorer) to determine the source of the corruption. The files that are involved are:
To prevent this problem from occurring, make sure the Search Companion is closed before you connect to your ISP.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.