DocFetcher Not Working? Common Errors & Fixes
The 10 DocFetcher problems users hit most often, why they happen, and the fixes that actually work — collected from user reports, forums, and official support docs.
DocFetcher Crashes With 'Program Died' Error
Workaround availableWindows, macOS, LinuxDocFetcher crashes during indexing are usually a parser choking on one bad file or the Java memory limit being hit. Update to 1.1.27, raise the memory limit, index subfolders separately and rebuild the broken index.
DocFetcher Out of Memory: How to Increase the Memory Limit
Workaround availableWindows, macOS, LinuxDocFetcher runs on Java with a fixed heap limit set by -Xmx in its launcher. Raise it (for example to -Xmx4g on an 8 GB PC) and big indexes stop hanging and crashing.
DocFetcher Won't Start or Open
Workaround availableWindows, macOS, LinuxIf DocFetcher does nothing when launched, disable the startup manual and HTML preview in settings-conf.txt, then try the script launcher to see the error. Old versions also fail without a matching 64-bit Java.
DocFetcher Not Finding Text in Files
Workaround availableWindows, macOS, LinuxDocFetcher matches whole words, so partial words, part numbers and scanned PDFs often return nothing. Use wildcards, check the file type is indexed, and update or rebuild the index.
DocFetcher Not Searching Scanned PDFs
Workaround availableWindows, macOS, LinuxDocFetcher has no OCR and only reads a PDF's text layer, so scanned PDFs show an empty preview and never match. OCR them first, then update the index.
DocFetcher 'Folder Hierarchy Is Too Deep' Error
Workaround availableWindows, macOS, LinuxThis error means Java ran out of stack space walking deeply nested folders. Raise -Xss2m to -Xss4m in the launcher script and always start DocFetcher from that script.
DocFetcher High CPU Usage
Workaround availableWindows, macOS, LinuxHigh CPU usually comes from folder watching reacting to a program that keeps changing files, or on Linux from the daemon when .indexes.txt is missing. Rebuild that index with watching off, or create the empty file.
DocFetcher Index Not Updating
Workaround availableWindows, macOS, LinuxThe DocFetcher daemon only flags changed folders; the actual update runs the next time DocFetcher starts. Open DocFetcher, update indexes manually, or schedule DocFetcher --update-indexes.
Outlook Won't Start After DocFetcher Indexing
Workaround availableWindowsOn Windows the DocFetcher daemon can block Outlook after you index Outlook PST mail. Rename docfetcher-daemon-windows.exe, reboot, and update your indexes manually from then on.
DocFetcher 'Requires a Java Runtime' Error
Fixed in latest versionWindows, macOS, LinuxOlder DocFetcher builds (1.1.25 and earlier) and the PortableApps version need a separate Java. Install 1.1.26 or newer, which bundles Java, or fix the CommonFiles\Java folder for the portable build.
SANDBOX · docfetcher RUNS IN YOUR BROWSER
Try it: a launcher with snippets and clipboard history
A hands-on DocFetcher-style sandbox, including the spots where users get stuck. 1-2 minutes, nothing is saved.
Problem not listed? See all DocFetcher complaints or compare DocFetcher alternatives.
// We build software. Any software.
Have an idea for an app? We'll build it.
We're a small team of developers who build custom software fast. Not just tools like DocFetcher: web and mobile apps, games, desktop software, AI tools, internal tools: whatever you have in mind. 50+ custom products built for clients so far, and we run our own products too: booking platforms, games, learning apps. See our work
- Web apps & SaaS
- Mobile apps (iOS & Android)
- Games
- Desktop software
- AI tools & automations
- Internal tools & dashboards
- Client portals & booking
- Your own version of any tool
- ✓ Free 15-min call to scope it
- ✓ Price agreed up front
- ✓ Your data, your code