This just started less than a month ago.

When I click the Search button in the Explorer toolbar, the following message appears:

"A file that is required to run search companion cannot be found. You may need to run setup."

I am running Microsoft Windows XP Sp3. (finally, I had a tough time installing xp3 and dound out that the registry didn't have the right permission settings)

I have google searched it and it seems like nothing will work. I've tried reinstalling the search thing using Srchasst.inf and it still won't work.

I read this article () and couldn't install the hot fix since it is for Sp1. I tried the other stuff and still won't work.

If anyone could tell me how to fix this without completely reinstalling Windows XP I'd be much obliged.

Dani AI

Generated

Quick note crediting for the policy hint and noting ’s successful tweak: changing the policy value type can make the Search Companion UI return, but when a Service Pack install or registry-permission change preceded the failure, that UI fix can be only a symptom-level cure. The system may still have missing or protected files, broken registrations, or incorrect ACLs that should be repaired to avoid recurrence.

Safe, practical next steps (in order):

  • Back up personal data and export the registry before making further changes (Regedit -> File -> Export).
  • Run System File Checker to restore protected system files (have the XP CD or a local i386 source ready):
sfc /scannow
  • Inspect Event Viewer (Administrative Tools -> Event Viewer) and look in the System/Application logs for errors recorded when Search failed — the log entries often name the missing module or error code and make targeted fixes possible.
  • If SFC cannot replace the missing/corrupt files, perform an in-place Repair Install of XP (run Setup from the XP CD and choose the Repair option when the installer locates the existing installation). This replaces system binaries while keeping installed applications and user data; always back up first.

Other checks and cautions:

  • Run a full anti-malware scan — odd permission changes and missing files sometimes follow infection.
  • Verify default file and registry ACLs were restored (SYSTEM and Administrators should own critical keys and system folders; avoid leaving Everyone with full control). Use well-documented tools or scripts only after backing up the registry.
  • If repair installs fail or multiple components are broken, a clean reinstall from a known-good image is the most reliable long-term fix.

This set of steps moves from least to most invasive and helps turn the temporary UI fix you found into a stable system repair.

Recommended Answers

All 4 Replies

Thanks for the suggestions. I actually have CCleaner runing at a scheduled time every day @ 3am. I went ahead and tried that reg cure program and fixed like 1369 more problems. Unfortunately, even after a restart, it still won't work.

Like I said before when I first tried to install Sp3, it couldn't install properly. Actually, an error came up that said that the changes that had been made couldn't be reverted either. All the problems that I'm having now started then.

I found out that the reason it wasn't working was a problem with the registry permissions. It was set to allow "Everyone" full access. I had to manually add "System", "Administrators", and my user name (I'm an administrator). After that it seemingly installed successfully. Unfortunately, it was still having the problems that it started having after the initial atempt to install it.

I tried to uninstall Sp3 and while it was uninstalling an error message came up that said "The system cannot find the file specified" "The Service Pack 3 was not uninstalled."


So... umm... yeah. I have no clue what to do with this. I really want the search feature back.

Any help is much appreciated!!!

found something on these site:

try this as suggested from the above site:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoFind

make sure all the value on the keys are zeros

Thanks again for the advice. I saw that on the link I originally posted, but I'm not sure what I did was what I was supposed to do. That key didn't even exist. I made a new REG_DWORD entry named "NoFind" (all the other entry types were that kind) and set the value to 0x00000000 (0). The value type is Hexadecimal. I don't think I did that correctly considering the fact that they describe the key value as follows:
"'NoFind' has the value '01 00 00 00'"

hmmm.... I probably should have tried different entry types...

1 sec....

trying alternative types........

Yes!!! It works! I had to change it from REG_DWORD to REG_SZ.

Thank you for you're help with the search thing!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.