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
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

90 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-03-29T14:23:54+00:00

    @Jean-François Paccini

    Did you edit your response while I was writing up my response? Now you are mentioning a Current Channel build number.... You might need to ignore my last response :)

    Gen

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-03-29T17:02:01+00:00

    @Geneviève

    yes, you can say Salut ! ;-)

    Yes I am on Insider slow ring (on both Windows & Office). I understand the effect of having different branches.

    For the sake of clarity: I enabled updates again, checked for new version and ended up with 7967.2030. As search was broken again with that build, I rolled back to 7571.2109.

    I am confused about what I should do now...

    Thanks for your help!

    jfp

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-03-29T17:25:13+00:00

    @JFP, you did the right thing... and you will need to hold in there for just a while longer!

    @Everyone else that are on Insider Fast build;

    You will get the fix on the next Office Insider FAST update.

    I do not know when that update will be available to you. We presently don't even have an internal forecasted date for it.

    Plus, even if we did have a forecasted date I wouldn't tell you because it often changes and I wouldn't want to set false expectations. That's just wouldn't fair to anyone!

    JPF, je te laisse savoir aussitôt que la mise à jour est disponible.

    Gen

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more