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: Newest
  1. 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 No comments
  2. 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 No comments
  3. Anonymous
    2017-03-29T14:22:06+00:00

    @Mickey Segal glad the search functionality is back for you. I totally am on the same page as you that partial word search is a good feature! Please also go vote for that feature:

    Provide an option of performing partial word search without using Advanced options in Microsoft Outlook 2016

    @Byron Huffman, KennethRudy , GeertWens  , Tanks for confirming it worked for you, that’s great to hear!

    @WilliamHerbert_911 & jimihenderson did you create a new profile after the Update that had broke search in the first place? If so please try to create a new profile now that the new update is installed. 

    And  if the issue persists please also ty rebuild the indexing.

    @Jean-François Paccini

    Hi!

    Or am I aloud to assume that I could say Salut?

    You seem to be on Insider build and that might be why it is not fixed.  It might take me a few hours to explain all the intricacies of how fixes are checked in all the channels and what not... So to make it super simple without boring anyone to death here, I think this is what happened:

    We released an update for both Current Channel & Office Insider Channel on the same day, but it is possible that only the Current Channel had the Outlook search fix in it. It was probably not checked in the Insider Channel yet.

    Hope this makes sense.

    Geneviève

    P.S. If you feel like reading all about the releases and channels here are some great articles to get you started:

    Overview of update channels for Office 365 ProPlus

    Office 365 client update channel releases

    Version and build numbers of update channel releases for Office 365 clients

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-03-29T14:13:27+00:00

    My new build is v. 1702, build 7870.2031, running on Windows 10 64-bit, and works fine.

    Was this answer helpful?

    0 comments No comments