Outlook Build 14131.20278 Click-to-Run: Selecting Search field crashes Outlook

Question

Hi:

Windows 10 computer has Outlook Version 2106 (Build 14131.20278 Click-to-Run) installed. 

If user selects Search field, Outlook crashes/closes then re-opens.

Already tried: 
Tried starting Outlook in Safe Mode, same issue.
Tried removing all Add-ins but same issue.
Tried creating new profile with new OST file but same issue.
Tried Office repair but same issue. 
Tried starting Index rebuild but same issue.
Tried re-installing Office over existing Office, i.e. did not uninstall Office first, but same issue.
Ran System Restore to earlier restore point, which was prior to installing two Intel drive updates (SCSI Adapter & System driver), but same issue.

Any insights greatly appreciated.

Thank you!
Bob

Answer 1

Microsoft confirmed this is a bug in Build 14131.20278

For my user with the issue, reverting to previous version 16.0.14026.20308 fixed the issue.

Bob

Answer 2

Hi @BobH-3096 ,

Welcome to Q&A forum.

Due to Outlook 2016, Outlook 2019 and Outlook 365 all have the version 2106, what's the Outlook client that you are work with?
Did the issue occur on this specific user only? And what's the type of your account(pop,imap or exchange)? If it's possible, it's recommended to search on your web mail for testing.

I have tested on my Outlook 365 version 2106 (Build 14131.20278 Click-to-Run), but it could work normally without any crash when I select search field. If the issue only occurred on this specific user, in order to further confirm if the issue is related to your account or client, it's recommended to configure other account in this Outlook client to check if it could work normally there.

If the issue could be reproduced on other account, it may be more related to your client, considering you have performed many troubleshoting methods before and we could exclude the influence of add-ins ,currpted profile and data file etc., as I know, any third-party programs may also affect Outlook, in order to avoid it, please try to perform a clean boot in windows to check if it could work normally in this case.

If the issue still exists, as an another method, you could try to work with SaRA tools to check , it could figure out what's wrong and offer the relevant solution for many identified problems by running tests automatically.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Has there been any more information on this? We've been able to narrow it down to those who have Version 2106 (Build 14131.20278 Click-to-Run). This is not happening to those of us who are on Version 2008 (Build 13127.21668 Click-to-Run).