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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-03-17T13:57:50+00:00

    I got the private message, but it gave the same information as here, leading to recommendations of low-relevance articles and to an opportunity for someone generic technician to call in 10 minutes.  There was nothing about filing a report or a non-generic person contacting me.

    The Microsoft people with access to those private messages have an email address and a phone number for me.  No one has contacted me to explore this problem.  Since there is now a report of the problem being fixed by rolling back to another version I will do so over the weekend unless Microsoft contacts me today (I'm gone after 2 PM Pacific time).  But this means Microsoft will get no information other than another data point demonstrating there is a problem.  

    Have things gotten so bureaucratic at Microsoft that they can't treat a loss of functionality in their main money-making product as urgent to fix before many people are affected?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-03-17T10:37:38+00:00

    Hi Rhonda

    Yes, I had found the same "solution" in my quest... I reverted to 16.0.7766.2060 and recovered instant search, but this is not a proper fix as I am now stuck to this build number :-(  But this is the risk with using Insider Version, isn't it ?

    Thanks

    jfp

    Was this answer helpful?

    0 comments
  3. 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

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