Unfortunately, Outlook cannot explain why it disabled a utility however, the reason often has to do with an Outlook crash. Many admins may read the message and assume that mssphtb.dll has been disabled because it’s causing a larger problem. The Outlook 2010 error message indicates that mssphtb.dll has been disabled, but doesn't explain why. The message in the dialog box is a stock template (Figure 1).įigure 1. It states, “The items listed below were disabled because they prevented Outlook from functioning correctly.” This message does not apply to mssphtb.dll. Information in the Disabled Items dialog box, which is found in the Developer tab, doesn’t offer much help in understanding a failure. In most instances though, Windows Search failures have nothing to do with Outlook.

Other times, failures stem from more complicated issues. Windows Search can fail if the service that controls it has been disabled and needs to be reactivated. How you can fix something if you aren't sure of the cause in the first place? Even if you manually enable mssphtb.dll, it will show as disabled after you restart Outlook 2010.Īdmins often blame the mssphtb.dll when Windows Search doesn’t work. Outlook search add-ons like Lookeen and Xobni, forare just two examples.Įven though the reference to the mssphtb.dll component still exists in Outlook 2010's COM Add-Ins list, the utility is permanently disabled.

Disabling the component allows third-party search add-ons to snap into Outlook 2010 without corrupting the existing search system.

Outlook 2010 can no longer access Windows Search,.

I suspect that there are two reasons why Microsoft disabled mssphtb.dll: This change eliminated the need for a separate component. Microsoft changed how Outlook connects to the Windows search subsystem when it developed Outlook 2010.

Outlook 2010 can39t connect to server