I can confirm the same issue and have performed fairly extensive troubleshooting.
The problem has been reproduced on two different new hardware platforms:
Dell Pro Premium Lenovo ThinkPad X1 Carbon Gen 14
In both cases, Classic Outlook indexes and searches:
subject sender plain-text email body
but does not index the body of HTML-formatted messages.
I have tested:
Office 2024 Microsoft 365 Apps 64-bit Microsoft 365 Version 2608, build 16.0.20326.20132 Microsoft 365 Version 2508, build 16.0.19127.20264 after rollback clean Windows 11 installation no third-party antivirus no BitLocker no Dell/Lenovo OEM applications new Outlook profile new Windows user profile multiple index rebuilds IMAP and POP accounts
The same behavior occurs on both new hardware platforms.
I also performed additional diagnostics using MFCMAPI and direct Windows Search queries.
For an affected HTML email, MFCMAPI shows:
PR_HTML present PR_NATIVE_BODY_INFO = 3 PR_BODY_W present
PR_BODY_W contains the complete readable text of the HTML message.
The email itself is present in the Windows Search index as a mapi16:// item and its subject/sender are indexed correctly.
However, when querying Windows Search directly for a unique word that exists only in the HTML body, using:
SELECT System.ItemName,System.ItemUrl FROM SystemIndex WHERE CONTAINS(System.Search.Contents, 'unique_html_body_term')
the result is:
Rows.Count = 0
At the same time, if the same HTML email is saved as a .msg file into an indexed Windows folder, Windows Search successfully indexes and finds text from the HTML body.
This strongly suggests that the issue is not the MSG IFilter itself, but rather the path used when Outlook messages are indexed through the MAPI16 Search Protocol Handler.
In other words:
Outlook HTML message PR_HTML -> OK PR_BODY_W -> OK
MAPI16 Search Protocol Handler Subject -> indexed Sender -> indexed Plain text -> indexed HTML body -> NOT indexed
I have also tested disabling HVCI / Memory Integrity and VBS security services. This did not change the behavior.
Interestingly, this problem seems to be associated with newer hardware platforms. An older ThinkPad previously used with the same Outlook/Windows environment did not exhibit this issue.
I have already submitted this to Microsoft Support / Feedback Hub. If anyone from Microsoft is monitoring this thread, it would be useful to have this escalated to the Windows Search / Outlook MAPI indexing engineering team, as the issue appears to occur specifically when HTML body content is passed from the Outlook message store through MAPI16 into System.Search.Contents.
The fact that the same issue is reproducible on both a Dell Pro Premium and a Lenovo ThinkPad X1 Carbon Gen 14, while an older ThinkPad worked correctly, may be relevant when investigating interaction between Windows Search/MAPI16 and newer hardware platforms.