Search Results Limit In Outlook 2016 RRS feed

  • Question

  • Outlook 2016 apparently limits search results to 250 messages.

    Unchecking "Improve search speed by limiting the number of results shown" (located in Outlook under File > Options > Search) is supposed to remove that limit. It did for one user, but not for others.

    Exchange cached mode is off. Exchange Server = 2013.

    Editing the registry entry "SearchResultCap" did not make any difference.

    Not sure what else to try. Any suggestions would be appreciated. Thanks.

    Thursday, February 2, 2017 4:02 PM

All replies

  • Hi,

    This "Improve search speed by limiting the number of results shown" option and "SearchResultCap" registry key only works for Cached Exchange mode.

    This is actually a known issue for the search in Online mode. To fix this, you will need to install Cumulative Update 11 or a later cumulative update for Exchange Server 2013.

    After you have installed the update, the default value is still 250, but you can edit the Microsoft.Exchange.Store.Worker.exe.CONFIG file to increase the limit of search results. To do that, you must add the following entries under the <appSettings> section as follows:

        <add key="MaxHitsForFullTextIndexSearches" value="5000" />

    Note If <appSettings> doesn't exist, you will need to add it after the </runtime> tag. The above example will increase the search items returned to 5000. 

    Read more:



    Ethan Hua

    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, February 3, 2017 6:29 AM
  • We have noticed this issue after moving to CU12. users are receiving maximum results of 250 within outlook 2016.

    After updating the MaxHitsForFullTextIndexSearches to 1000 it works as expected. However we have a few users that require more results. the next change was to increase it to 5000. this value is within the valid range of 1-100000, however the databases do not mount.

    I suspect this is more a limitation of hardware, but am unsure how to calculate or even guess a maximum value that will work with the current server configuration. beyond just changing the value and seeing if it works.

    Wednesday, March 13, 2019 2:58 PM