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: Oldest
  1. Anonymous
    2017-03-16T15:45:46+00:00

    Jean,

    Are you still seeing the search issue?  There was a service incident in Office 365 that caused issues but it should be resolved now, incident EX94603.  

    The instructions to revert are in this KB, https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run.

    Here are the main steps to revert to the previous working version:

    1. Open a command prompt and run the following commands in order:

    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun

    officec2rclient.exe /update user updatetoversion=16.0.7571.2109

    2. Open Outlook and click File, Office Account and set Update Options to Disable Updates

    3. Add an appointment on your calendar for a month or more out to remind you to re-enable updates.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-03-16T17:50:58+00:00

    Hi Jean-François,

    You can use the instructions from Gabriel Bratton, or follow these:

    https://www.msoutlook.info/question/784

    or these:

    https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run

    Good luck. I cannot fathom why Microsoft fixed the problem for business accounts but not home accounts. Just boggles the mind.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-03-16T18:22:30+00:00

    I'm not about to fool around with "support" for this. I'm reverting to 7668.2074 from 7870.2024. Please note that y'all broke it in February (2020), and March (2024) didn't fix it. 

    If people solve this problem by reverting (or don't) that would be helpful information to share.  

    Since the Microsoft people are unable to reproduce this themselves this may take a long time to get fixed.  At the beginning of this thread they asked for my email address and phone number, but they haven't taken me up on my offer to contact me in those ways.  

    Outlook bugs related to iCloud have taken months to fix, and one bothersome bug from 2013 is still not fixed: https://answers.microsoft.com/en-us/msoffice/forum/msoffice\_outlook-mso\_win10/icloud-kills-touch-scrolling-for-outlook-messages/3f085788-c0a4-446e-a3e9-85522d055adf 

    I plan to wait until the weekend before doing a backup and trying more invasive potential fixes.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-03-16T19:16:00+00:00

    I cannot fathom why Microsoft fixed the problem for business accounts but not home accounts. Just boggles the mind.

    There seem to be at least one form of this problem not addressed by Microsoft's fix.  The one that was fixed wasn't the one that was affecting me, even on the business version.

    Was this answer helpful?

    0 comments No comments