Did February 2017 Office 365 update break Outlook Search?

Anonymous
2017-03-14T00:36:33+00:00

I upgraded 2 computers to the Office 365 February update: https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Office-365-95c8d81d-08ba-42c1-914f-bca4603e1426?ui=en-US&rs=en-US&ad=US

Ever since then search is broken in Outlook on both computers - any search returns no results.  Windows 10 search outside Outlook works fine.  I've rebuilt the index, used ScanPST.exe and tried other things at https://lookeen.com/blog/how-to-fix-outlook-2016-search-problems and https://support.office.com/en-us/article/Reset-indexing-by-rebuilding-your-Instant-Search-catalog-213a2728-0ef4-427a-9bb2-aed329a59b17 but the problem remains on both computers.  

Did February 2017 Office 365 update break Outlook Search?

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-03-28T14:37:06+00:00

Hello everyone,

There is an updated build that was just released. Please turn auto updates back on, install the latest build & confirm that it fixed the issue.

Gen

Was this answer helpful?

90+ people found this answer helpful.
0 comments No comments

90 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-03-18T18:16:33+00:00

    I'd like to jump in and report that my Outlook 2016 (Local PC installation with POP3 .pst's) experienced a complete ceasing of instant search functionality upon updating Office this week to Version 1702 (Build 7870.2024) on Windows 10.

    I have perhaps figured out a fix... (but please let me know if this works for you as it did for me)

    First off, I tried EVERYTHING to correct this problem, short of reverting to an older build.

    I tried everything in terms of the search index (unchecking Outlook, rebuilding, changing indexing location, etc) and nothing worked.  I tried starting and restarting the windows search service in services.msc.... still nothing.

    I ran the PST repair tool over and over... still nothing change.. search functionality did not work and always said "No Results".

    Here is what actually did work for me and brought back search functionality:

    Open Outlook 2016 and click....

    File -->  Info -->  Account Settings... --> Data Files (Tab)

    There you will see a listing of the Outlook Data Files you are using (ie. PST or OST files)

    Look at the "Location" that is being used.

    You'll either notice something like:

    C:\Users{Your_Username}\Documents\Outlook Files\yourpstname.pst

    -- or, something like.. --

    \?\C:\Users{Your_Username}\Documents\Outlook Files\yourpstname.pst

    (notice the preceding '\?')

    Now I don't know why it might have the '\?' prepended to the filepath -- but has something to do with the search functionality working or not.

    Now with that list of Outlook data files you are looking at, click each and select the 'Settings...' button above it.

    You should see the filepath location listed in the popup window here.  Don't edit it, but rather, just hit OK.

    Do this for each Outlook data file.

    You'll notice that simply doing this, the file location for some of your PSTs/OSTs will change to include the '\?' prepended to the filepath.

    I have no idea what this means, or what this does, but immediately after doing this, my search functionality returned.

    After doing this, the indexing began (as I was hoping it would) and after 5-10 minutes I had all 100,000+ emails indexed are now fully searchable in Outlook using instant search.

    I really hope this works for everyone -- and really hope you will tell me if it does or does not work for you.

    In the meantime, I urge Microsoft to recognize that there are many people that lost Outlook search functionality on this update, and that there is likely a bug causing this.

    Thank you and hope this helps someone.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-03-17T08:06:14+00:00

    Hi Everyone,

    Thanks for reporting this. We have done a lot of test in our lab. However, we’re unable to reproduce this issue in the same OS version and Outlook version.  If you are pretty sure that the problem is caused by upgrading your client to Version 1702 (Build 7870.2020), you can roll back your Outlook client via https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run

    Further, we have sent the private message to all of you in this thread. Please feel free to let us know the feedback, you can also provide your tenant information (if you’re an Office 365 for Business user) and account type (like POP/IMAP) via private message.

    Thanks,

    Aaron

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-04-08T09:29:35+00:00

    Hi Jfp,

    If the issue persists after updating Outlook to 7967.20**35,**please post a new thread in our forum as it may be related to another root cause. Our engineer will further help.

    Thanks,

    Aaron

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-03-28T21:39:00+00:00

    This seems to have worked for me - so far.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments