If this sounds like your week
When Windows Search gets in the way
modern Windows apps can expose command shims under %LOCALAPPDATA%\Microsoft\WindowsApps rather than classic install folders. Windows Search can confuse Store-style entries with web or shell results and hide the filesystem shim. terminal commands may work while the Start Menu path remains hard to inspect.
Where tooling usually breaks
Why local-first matters
index.db, config.json, and logs stay under %APPDATA%\SearchSentinel instead of a vendor-hosted workspace. Search queries are not uploaded for AI enhancement, analytics, or ad targeting. You buy the app once and keep the search index as a local workstation asset.
Technical proof points
- WindowsApps scan - Executable filters - Start Menu merge - ShellExecuteW - Windows app enumeration - COM shortcut resolution