One of my customer reported that in one of his machine, the exchange explorer (available part of Exchange SDK) stop responding. But the same work in his rest of the machines. During the research, we found the following known issues (stop responding, doesn’t display etc) with exchange explorer:

Cannot set member server schema scope using Exchange Explorer

On a computer where Microsoft Internet Explorer 6 is installed, the schema scope for a non-MAPI folder can only be set on the first server connected to the domain. The schema scope for non-MAPI folders cannot be changed for other servers that are members of that domain. Attempting to edit the schema-collection-ref or base schema fields can cause the Exchange Explorer to stop responding.

Exchange Explorer may stop responding when viewing a folder on a different server

When using the Exchange Explorer on a computer with Internet Explorer 6 installed, selecting a folder that is located on a different server in the domain may cause the Exchange Explorer to stop responding.

Exchange Explorer obtains the code page from the machine configuration

When using the Exchange Explorer on a computer running the US-English version of Microsoft Windows® server operating systems, the Exchange Explorer displays information using the code page setting of the machine. If the user has chosen a different locale for display, for example Japanese (JPN), the Exchange Explorer may incorrectly display characters from the user-specified locale as "??".

Exchange Explorer does not display all property namespaces

Exchange Explorer does not display schema properties in the http://schemas.microsoft.com/mapi/ Namespace.

Hope this helps.