Visual Studio 2005 Tools for the Microsoft Office System:

SUPPORT SOLUTION:
The ActionsPane ActiveX control of a Microsoft Visual Studio Tools for the Microsoft Office System (VSTO) solution may not load on a computer that is running a non-U.S. English version of Windows XP Service Pack 2 (SP2). When this occurs, an empty Document Actions pane is displayed in Microsoft Office Excel or in Microsoft Office Word..On certain non-U.S. English versions of Windows XP SP2, the Microsoft Internet Explorer ActiveX Compatibility kill bit setting may have been unintentionally set for the ActionsPane ActiveX control. When this occurs, Microsoft Office honors the kill bit settings that are applied for Internet Explorer and prevents the ActionsPane ActiveX control from loading..Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 

(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in WindowsTo work around this issue, remove the kill bit setting for the ActionsPane ActiveX control.
To manually remove the kill bit, follow these steps:
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{5F61F809-422A-4152-91F5-9EC1B935EFD7}Delete this subkey.
Developers who create and deploy VSTO applications that use the ActionsPane ActiveX control may want to consider one of the following options:
If you use a setup package to deploy the application, you may want to add a custom action to the setup project to check for and remove the kill bit registry key if it is found on the client. For more information about how to create a custom action, visit the following MSDN Web site:
Custom Actions Management in Deploymenthttp://msdn.microsoft.com/en-us/library/bbd7cck3(VS.80).aspx
(http://msdn.microsoft.com/en-us/library/bbd7cck3(VS.80).aspx)
If you do not use a setup package to deploy the application, you may want to add code to the Startup event of the document or workbook to check for the kill bit registry key and display a warning message to the user that the registry key will have to be deleted. For more information, visit the following MSDN Web sites. Accessing the Registry with Visual Basic .NEThttp://msdn.microsoft.com/en-us/library/aa289494.aspx
(http://msdn.microsoft.com/en-us/library/aa289494.aspx)
File System and the Registry (C# Programming Guide)http://msdn.microsoft.com/en-us/library/2kzb96fk.aspx
(http://msdn.microsoft.com/en-us/library/2kzb96fk.aspx)
.

For File Repair and Data Recovery, visit File Repair / Data Recovery