Does anyone know what I've done and how to fix this? Thanks!search-ms:crumb=location:C%3A%5CWindows
This file does not have a program associated with it for performing this action.
By way of a guess: did you enable Configuration > Shell Integration > XYplorer in shell context menu, as well as XYplorer is default file manager? If so, undoing both might help.Stilez wrote:I'm not sure what I've done, and can't find anywhere on the forum or google that explains how to undo it.
I'm using Windows 7. I enabled the "Search..." context menu item using the "LegacyDisable" registry edits. I installed Xyplorer. I probably tweaked a few Xyplorer settings.
Now when I right click a folder or drive in Windows Explorer and choose the "Search..." option, I get a message:
Does anyone know what I've done and how to fix this? Thanks!search-ms:crumb=location:C%3A%5CWindows
This file does not have a program associated with it for performing this action.
In that case the most likely culprit is explained in this FAQ. I'm unfamiliar with the legacy registry tweak you described in your first post, but if it's part of (64-bit) Windows it's most likely 64-bit code which a 32-bit app like XYplorer can't call directly as the FAQ explains.Stilez wrote:"XYplorer in shell context menu" was enabled, "XYplorer is default file manager was not". Disabled the first of these, no effect.
Yes, Win 7 x64.
Does Windows Search work in general, i.e. when searching for a known-to-exist file through the search box of the start menu, does Windows find it?Stilez wrote:Not that at all.
The LegacyDisable key is simply a registry edit described here. It works well and isn't affected by x64 or x32. But something got broken in trying to set up XYplorer. I'm hoping someone might be able to figure why, from the error message or general windows knowledge.
XYplorer Beta Club