Search Not Indexing File Contents of Office or PDFs

Question

Search Not Indexing File Contents of Office or PDFs

Jeff Schmied 20

I have a Windows Server 2022 Standard VM with multiple File Shares. I can't figure out why but it will not index file contents of office or PDF documents. I have tried re-installing the search index, re-installing the Microsoft Filter Pack 2.0, rebooting, restarting services, running the Search Troubleshooter, making sure the file types are selected under the Advanced options and are set to index contents, rebuilt the index multiple times, move the index location, set the reg key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\SetupCompletedSuccessfully to 0, Windows is fully patched, no real errors in the event viewer with regards to searching, we have no group policies for search indexing, just about everything I could find online to try I've tried and it just won't index the contents of Office files or PDF's. I'm now just testing with single folders (indexing the entire drive contents takes about a week). It will index the contents of TXT files but that's not much help to my users. I even tried running SFC and DISM utilities with no results. I have multiple, identical file sharing VM's setup running the same OS and patch levels that do not have this problem.

I've seen posts from others saying they gave up and created a new VM and migrated files & shares over but I do NOT want to do that. Any help would be appreciated.

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Jeff Schmied,

Since plain text files are indexing successfully, your core search engine is functioning normally. This narrows the problem down to either a permissions issue with the indexer or a failure with the specialized IFilter components responsible for extracting complex text from Office and PDF files. The Windows Search service operates exclusively under the local SYSTEM account context. Even if you have full administrative rights, if the SYSTEM account lacks explicit Read permissions on your file share folders, the indexer will only read the file properties and silently fail to parse the internal contents. Checking the NTFS security properties of your testing folder to verify the SYSTEM account is explicitly granted Read access should be your first troubleshooting step.

If the NTFS permissions are already correct, the registry mappings linking document extensions to their respective IFilters are likely corrupted. Reinstalling the Microsoft Filter Pack often fails to resolve this because Windows installers typically will not overwrite persistent registry keys if they contain existing, albeit corrupted, data. Since you have identical, functioning Server 2022 VMs, you can leverage them to easily fix the broken server without rebuilding it. Open the Registry Editor on a working server and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes. Locate the problematic extensions like .docx and .pdf, expand them to find the PersistentHandler subkey, export these specific keys, and merge them into your broken server to restore the proper Class ID strings.

Regarding PDF files, Windows Server often struggles with native PDF content indexing if a third-party PDF reader has altered the default handlers during installation or an update. You must verify the problematic server is running the exact same PDF software version as your working servers, as a mismatch can easily unregister the handler. After verifying the SYSTEM permissions and importing the correct PersistentHandler registry keys from your working environment, restart the Windows Search service, point it at your test folder, and rebuild the index.

Hope this answer brought you some useful information. If it did, please consider hitting "accept answer". Should you have any questions, feel free to leave a comment.

VP

Jeff Schmied 20 Reputation points

2026-03-05T12:38:08.0433333+00:00

I really wish I had seen this response before I did a repair/reinstall of Windows, lol. After the repair the search does seem to be working, my test folder indexed contents of Office files so I expanded it to include its parent folder which also worked, now I'm doing the full share my test folder was in but after 2 days, it's only about halfway done indexing its 422,000 files (1.9TB). If that goes OK I will add more of the shares on this server but that may take at least a week to index the 767,000 files (1.7TB) contained in other shares.

Going through folder permissions in my test share I am seeing the SYSTEM account was removed from any folders that are not inheriting from the parent so I will add it back in.

Thank you for your suggestions VP

Share via

Search Not Indexing File Contents of Office or PDFs

0 additional answers

Your answer