Outlook 2024 (POP/PST): Search does not index HTML email bodies (IFilter issue)

Question

Outlook 2024 (POP/PST): Search does not index HTML email bodies (IFilter issue)

bernard Andri 0

Hello,

I am facing a persistent search issue in Outlook 2024 (using POP accounts with .pst data files). The search function only returns results if the keyword appears in the Subject line or in the name of an attachment. Words inside the email body are ignored, unless the message is formatted as Plain Text (HTML-formatted bodies are not indexed).

Here is what I have already checked and tested:

Indexing Status: Windows Search indexing completed successfully, and Outlook reports 0 items remaining to be indexed.
Indexing Locations & File Types:
- Microsoft Outlook is correctly listed under Included Locations.
  - Under Advanced Options > File Types, .pst is set to "Index Properties and File Contents".
    - Observation: In Indexing Options > Advanced > File Types, the .pst extension shows "Plain Text Filter", whereas .msg shows "Office Outlook MSG IFilter".
    1. Registry Tweaks: I spent significant time attempting registry modifications to force Windows Search to use the correct IFilter for HTML parsing inside PST files, but without success.
    2. Safe Mode: Search works as expected when running Outlook in Safe Mode (since Outlook falls back to its built-in legacy search engine), but it is naturally very slow as it rescans on every query.
    3. New Profile & Clean PST: I created a fresh Outlook profile with a minimal PST file containing only a few test messages. The problem persists even on a clean setup.

It appears Windows Search is failing to load or assign the proper IFilter to handle HTML-formatted message bodies inside PST containers in Outlook 2024. Any insights or registry/DLL fixes to restore proper HTML body indexing would be greatly appreciated.

Thank you!

Zahid Barrera Ramirez 5 Reputation points

2026-09-06T21:12:53.53+00:00

Your Safe Mode test is probably the most important clue here.

If body searches work in Safe Mode but fail with Windows Search enabled, and the same behavior occurs with a new Outlook profile and a clean PST, I would stop troubleshooting the PST/profile itself and focus on the Windows Search/Office filter registration.

One thing stands out: seeing “Plain Text Filter” associated with .pst does not look right for Outlook content indexing. PST is a container, and Outlook/Windows Search should expose the message properties and body content through the appropriate Outlook search components rather than treating the PST as a plain-text file.

Before forcing an IFilter through registry changes, I would check:

• Whether the Microsoft Office/Outlook search filter components are correctly registered. • Whether Office and Windows architecture match (x64/x86). • Whether another application has modified the PersistentHandler/IFilter associations. • The Windows Search event logs for filter-host or protocol-handler errors while indexing the test PST. • Whether an Online Repair of Office restores the original search/filter registrations.

I would be particularly careful about manually assigning the MSG IFilter directly to .pst. A PST is not simply a collection of MSG files, so forcing that association could create additional indexing problems.

Given that you reproduced this with a clean profile/PST, I would also test the same PST on another Outlook 2024 installation. If HTML body content indexes correctly there, you have strong evidence that the issue is with the local Windows Search/Office integration rather than Outlook data.

At this point, ProcMon against SearchFilterHost.exe/SearchProtocolHost.exe while indexing the small test PST could also tell you which filter DLLs and registry registrations Windows Search is actually loading.

Your Safe Mode result strongly suggests the messages themselves are searchable — it is the indexed search path that is failing.
Hornblower409 14,425 Reputation points

2026-09-08T00:09:01.6466667+00:00
@bernard Andri said

Search works as expected when running Outlook in Safe Mode

Since Safe Mode's primary impact is to disable all Add-ins, it might be work trying another test:

Start Outlook normally.

File → Options → Add-ins.

Manage COM Add-ins → Go.

Take a screen shot of the dialog, or make notes, so you know which Add-Ins are normally enabled.

Disable everything by unchecking it.

Restart Outlook normally.

Do your search test.
Zahid Barrera Ramirez 5 Reputation points

2026-09-08T01:05:11.89+00:00

@Hornblower409 Good point — I agree this is an important test before going deeper into the Windows Search/IFilter path.

Safe Mode disables COM add-ins and other Outlook extensions, so the fact that search works there does not by itself prove that Outlook is bypassing Windows Search.

I would disable all COM add-ins as you suggested, restart Outlook normally, and repeat the HTML-body search test.

If the issue disappears, I would then re-enable the add-ins one at a time to identify the component interfering with search.

If the issue remains with all COM add-ins disabled, that would make the Windows Search/indexing path more interesting again, especially given that:

the issue reproduces with a new profile and clean PST,

indexing reports 0 items remaining,

Plain Text messages are searchable by body,

HTML message bodies are not,

and Microsoft expects the Outlook MSG IFilter to be correctly registered for Outlook content indexing.

At that point I would compare the filter/protocol-handler activity between normal and Safe Mode, potentially using ProcMon against SearchFilterHost.exe and SearchProtocolHost.exe.

Thanks for pointing this out — disabling the add-ins separately is definitely a cleaner isolation step before assuming an IFilter problem.
bernard Andri 0 Reputation points

2026-09-08T18:15:06.0166667+00:00

I’d already tried disabling all COM add-ins, but the problem persists
bernard Andri 0 Reputation points

2026-09-08T18:19:58.3566667+00:00

I should point out that I’ve just changed my computer. On the old one, which ran Windows 11 but had Office 2019, the search function worked. On the new computer (still an HP EliteBook), I’ve installed Office 2024. Do you think it would be worth trying to install Office 2019 instead of Office 2024 on my new laptop?
Zahid Barrera Ramirez 5 Reputation points

2026-09-08T18:24:53.6933333+00:00
@bernard Andri Yes, that comparison is very useful, but I would not replace Office 2024 with Office 2019 just yet.

The fact that the same type of POP/PST configuration worked correctly on Windows 11 with Outlook 2019, while the new Windows 11 + Outlook 2024 installation does not index HTML message bodies, makes the Outlook/Office version or its Windows Search integration a much stronger suspect.

Before downgrading, I would complete the COM Add-ins test Bernard suggested earlier:

Start Outlook 2024 normally.

Disable all COM Add-ins.

Restart Outlook normally.

Test a search for a word that exists only inside the HTML body of a message.

If the problem remains, I would then consider Office 2019 a very useful diagnostic test — not necessarily the permanent solution.

If you still have access to the old computer, an even better comparison would be to check the Windows Search/File Types configuration on both machines, particularly the Outlook-related filter registrations. That could show us whether Office 2019 and Office 2024 registered different search components.

If Office 2019 indexes the same test PST correctly on the new computer while Office 2024 does not, that would be very strong evidence that we are dealing with an Office 2024/Windows Search integration issue rather than corrupted PST data, the Outlook profile, or Windows itself.

So yes, testing Office 2019 could be worthwhile — but I would use it as a controlled troubleshooting step after testing Outlook 2024 with all COM Add-ins disabled.

Also, before changing Office versions, I would make sure you have a backup of the PST files and your Office 2019 installation/license available.

If this answer helped, please consider marking it as helpful. It helps other users experiencing the same issue find the troubleshooting path more easily.
Hornblower409 14,425 Reputation points

2026-09-08T18:57:56.48+00:00

@bernard Andri said

Do you think it would be worth trying to install Office 2019 instead of Office 2024 on my new laptop?

Before you go down that path, I would suggest that you bring in Microsoft Support. They can examine your setup and pull diagnostic logs from Outlook and Windows Indexer.

For Classic Outlook In-App Chat Support, do Help -> Contact Support

Your answer

Hornblower409 14,425 Reputation points

2026-09-08T00:09:01.6466667+00:00

@bernard Andri said

Search works as expected when running Outlook in Safe Mode

Since Safe Mode's primary impact is to disable all Add-ins, it might be work trying another test:

Start Outlook normally.

File → Options → Add-ins.

Manage COM Add-ins → Go.

Take a screen shot of the dialog, or make notes, so you know which Add-Ins are normally enabled.

Disable everything by unchecking it.

Restart Outlook normally.

Do your search test.
Zahid Barrera Ramirez 5 Reputation points

2026-09-08T01:05:11.89+00:00

@Hornblower409 Good point — I agree this is an important test before going deeper into the Windows Search/IFilter path.

Safe Mode disables COM add-ins and other Outlook extensions, so the fact that search works there does not by itself prove that Outlook is bypassing Windows Search.

I would disable all COM add-ins as you suggested, restart Outlook normally, and repeat the HTML-body search test.

If the issue disappears, I would then re-enable the add-ins one at a time to identify the component interfering with search.

If the issue remains with all COM add-ins disabled, that would make the Windows Search/indexing path more interesting again, especially given that:

the issue reproduces with a new profile and clean PST,

indexing reports 0 items remaining,

Plain Text messages are searchable by body,

HTML message bodies are not,

and Microsoft expects the Outlook MSG IFilter to be correctly registered for Outlook content indexing.

At that point I would compare the filter/protocol-handler activity between normal and Safe Mode, potentially using ProcMon against SearchFilterHost.exe and SearchProtocolHost.exe.

Thanks for pointing this out — disabling the add-ins separately is definitely a cleaner isolation step before assuming an IFilter problem.
bernard Andri 0 Reputation points

2026-09-08T18:15:06.0166667+00:00

I’d already tried disabling all COM add-ins, but the problem persists
bernard Andri 0 Reputation points

2026-09-08T18:19:58.3566667+00:00

I should point out that I’ve just changed my computer. On the old one, which ran Windows 11 but had Office 2019, the search function worked. On the new computer (still an HP EliteBook), I’ve installed Office 2024. Do you think it would be worth trying to install Office 2019 instead of Office 2024 on my new laptop?
Zahid Barrera Ramirez 5 Reputation points

2026-09-08T18:24:53.6933333+00:00

@bernard Andri Yes, that comparison is very useful, but I would not replace Office 2024 with Office 2019 just yet.

The fact that the same type of POP/PST configuration worked correctly on Windows 11 with Outlook 2019, while the new Windows 11 + Outlook 2024 installation does not index HTML message bodies, makes the Outlook/Office version or its Windows Search integration a much stronger suspect.

Before downgrading, I would complete the COM Add-ins test Bernard suggested earlier:

Start Outlook 2024 normally.

Disable all COM Add-ins.

Restart Outlook normally.

Test a search for a word that exists only inside the HTML body of a message.

If the problem remains, I would then consider Office 2019 a very useful diagnostic test — not necessarily the permanent solution.

If you still have access to the old computer, an even better comparison would be to check the Windows Search/File Types configuration on both machines, particularly the Outlook-related filter registrations. That could show us whether Office 2019 and Office 2024 registered different search components.

If Office 2019 indexes the same test PST correctly on the new computer while Office 2024 does not, that would be very strong evidence that we are dealing with an Office 2024/Windows Search integration issue rather than corrupted PST data, the Outlook profile, or Windows itself.

So yes, testing Office 2019 could be worthwhile — but I would use it as a controlled troubleshooting step after testing Outlook 2024 with all COM Add-ins disabled.

Also, before changing Office versions, I would make sure you have a backup of the PST files and your Office 2019 installation/license available.

If this answer helped, please consider marking it as helpful. It helps other users experiencing the same issue find the troubleshooting path more easily.
Hornblower409 14,425 Reputation points

2026-09-08T18:57:56.48+00:00

@bernard Andri said

Do you think it would be worth trying to install Office 2019 instead of Office 2024 on my new laptop?

Before you go down that path, I would suggest that you bring in Microsoft Support. They can examine your setup and pull diagnostic logs from Outlook and Windows Indexer.

For Classic Outlook In-App Chat Support, do Help -> Contact Support