Outlook 2016 search not working
Posted On April 16, 2019
Recently I was notified by a customer that Outlook search wasn’t working anymore as expected (Search not working at all, or missing results). After some searching I found out that this was caused by a Windows 10 Update where a shared DLL was updated: KB4467684
In the the end there is a quick fix by running a simple command that repairs the effected MSWB7.dll file.: sfc/scannow (run as administrator)
The following output will be generated bij de SFC/scannow command
- 2018-12-31 12:04:55, Info CSI 00007a95@2018/12/31:11:04:55.091 Primitive installers committed for repair
- 2018-12-31 12:04:55, Info CSI 00007a96@2018/12/31:11:04:55.091 Primitive installers committed for repair
- 2018-12-31 12:04:55, Info CSI 00007a97@2018/12/31:11:04:55.106 Primitive installers committed for repair
- 2018-12-31 12:04:55, Info CSI 00007a98 [SR] Verify complete
- 2018-12-31 12:04:55, Info CSI 00007a99 [SR] Repairing 1 components
- 2018-12-31 12:04:55, Info CSI 00007a9a [SR] Beginning Verify and Repair transaction
- 2018-12-31 12:04:55, Info CSI 00007a9b [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\MSWB7.dll from store
- 2018-12-31 12:04:55, Info CSI 00007a9c@2018/12/31:11:04:55.184 Primitive installers committed for repair
- 2018-12-31 12:04:55, Info CSI 00007a9d [SR] Repair complete
- 2018-12-31 12:04:55, Info CSI 00007a9e [SR] Committing transaction
- 2018-12-31 12:04:55, Info CSI 00007a9f Creating NT transaction (seq 1), objectname ‘(null)’
- 2018-12-31 12:04:55, Info CSI 00007aa0 Created NT transaction (seq 1) result 0x00000000, handle @0x63c
- 2018-12-31 12:04:55, Info CSI 00007aa1@2018/12/31:11:04:55.216 Beginning NT transaction commit…
- 2018-12-31 12:04:55, Info CSI 00007aa2@2018/12/31:11:04:55.231 CSI perf trace:
About The Author
