Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes an update rollup that is available for Visual Studio 2010 Tools for Microsoft Office Runtime 4.0. The release date for this update is November 13, 2012. 

Issues that the update rollup fixes:

  • Issue 1Assume that a Word document has embedded objects. When you try to delete a Windows Forms control from the document, you receive an error message that resembles the following:

    Object is not connected to server (Exception from HRESULT: 0x800401FD (CO_E_OBJNOTCONNECTED))at Microsoft.Office.Interop.Word.OLEFormat.get_Object()at Microsoft.Office.Tools.Word.Adapter.ShapeHelpers.GetOLEFormatObject(OLEFormat oleFormat)at Microsoft.Office.Tools.Word.Adapter.DocumentControlCollectionAdapter.Microsoft.Office.Tools.Word.Contract.IDocumentControlCollectionContract.DestroyWrapper(String cookie)at Microsoft.VisualStudio.Tools.Office.Word.Internal.IDocumentControlCollectionProxy.DestroyWrapper(String cookie)at Microsoft.Office.Tools.Word.ControlCollection.InternalRemove(Int32 index, Boolean deleteContent)at Microsoft.Office.Tools.Word.ControlCollection.Remove(Object control)

  • Issue 2When you try to use an SSL-based Universal Naming Convention (UNC) path to access a Web Distributed Authoring and Versioning (WebDAV) share, you receive an error message that resembles the following:

    Invalid URI: The hostname could not be parsed.System.UriFormatException: Invalid URI: The hostname could not be System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)at System.Uri..ctor(String uriString)at Microsoft.VisualStudio.Tools.Office.Runtime.OfficeAddInDeploymentManager.OnAddInInstalling(AddInInstallingArgs args, Boolean& cancel)at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.RaiseOnAddInInstallingEvent(IClickOnceAddInInstaller addInInstaller, Uri deploymentManifestUri, AddInInstallationStatus addinSolutionState, String productName, Boolean alreadyInstalled)at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()

  • Issue 3You cannot store data in cached data islands that are in protected documents in a Microsoft .NET Framework 4.0-based application.

  • Issue 4Consider the following scenarios:

    • You call the ServerDocument.IsCustomized function in order to check the customization for a Microsoft Word 2010 document that uses Ink.

    • You call the ServerDocument.AddCustomization function in order to customize a Word 2010 document that uses Ink.

    When one of the scenarios is true, you receive an error message that resembles the following:

    Office Open XML Formats document is invalid: it contains no manifest of the requested type.Source: Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0Stack:at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo.GetPartId(Package package, PackagePart part)at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo.EnsureMaps()at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo..ctor(Package package)at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.EnsureAppInfo()at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.Microsoft.VisualStudio.Tools.Applications.Runtime.IAppInfoDocument.SetDocument(String fileName, Byte[] data, FileAccess fileAccess)at Microsoft.VisualStudio.Tools.Applications.AppInfoDocumentFactory.GetAppInfoDocument(String documentPath, Byte[] bytes, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.Initialize(Byte[] bytes, String documentPathOrFileType, FileAccess access, Boolean throwOnPreviousVersion)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.Initialize(Byte[] bytes, String documentPathOrFileType, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument..ctor(String documentPath, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.IsCustomized(String documentPath)

  • Issue 5Microsoft Visual Studio Tools for Office 2005 Second Edition add-ins do not work after you install build 31125 of the Visual Studio Tools for Office 2010 runtime.

    This issue occurs when you install Microsoft Visual Studio 2012 or Microsoft Office 2013, as both products install the version of the Visual Studio Tools for Office runtime that has the problem.

More Information

This update rollup is available from the following Microsoft website:

Windows UpdateYou can download the update rollup from the Microsoft Download Center. The following files are available for download from the Microsoft Download Center:
DownloadDownload the vstor_redist package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.


To apply this update rollup, you must have Visual Studio 2010 Tools for Office Runtime 4.0 installed.

Restart requirement

You may have to restart the computer if the affected files are being used or are locked. To reduce the probability of a restart, you should close all applications before you install the update.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!