Visual Studio 2010 Service Pack 1 installing for over 2 hours could be a sign of a problem

On average customers are experience ~45 minute installs for Visual Studio 2010 SP1. Based on machine performance, even seeing install times of a little over an hour isn’t unexpected. But if VS2010 SP1 is taking more than a couple hours to install, there could be a problem and in the case described below requires user… Read more

A patch may take as long or longer to install than the target product

Often I’m asked why installing a Windows Installer patch (MSP) takes as long or longer to install than the target product (MSI). While this isn’t always the case for every patch, it’s certainly possible for a number of reasons. It may also come as a surprise that the size of the patch can have little… Read more

Installation sequence restrictions for multi-package transactions

Windows Installer 4.5 introduced a feature to install multiple packages in a single transaction. Multi-package transactions allow setup developers to install multiple packages as an atomic unit that are installed together, or rolled back completely. You can also apply patches to multiple products or even repair multiple products – any maintenance mode installation – within… Read more

Patch Applicability

When installing a patch package, Windows Installer first determines if the patch is applicable. Depending on how the patch is installed, this happens a little differently. Windows Installer can determine the list of applicable products, or it can be told to which products the patch should be applied. Possible products To have Windows Installer determine… Read more

Microsoft .NET 1.x and Visual Studio 7.x patches may fail to uninstall

When attempting to uninstall a patch from the products listed in the Applies To section below, the following error may occur. Internal Error 2771. M953297 The last part of the error message will vary with each patch, where the last 6 digits are the knowledge base article related to the patch. Applies To Microsoft .NET… Read more

Changes to Package Caching in Windows Installer 5.0

Windows Installer 5.0 is shipping in Windows 7 as part of the operating system. To address the issue where the User Account Control consent dialog is displayed with an “Unidentified Publisher”, the .msi package is cached in its entirety. Prior to Windows Installer 5.0, installation packages, or .msi files, were stripped of their embedded cabinets… Read more

Another Possible Workaround for Error 1330

When installing Visual Studio 2008, you might run into an error dialog that reads, Error 1330.A file that is required cannot be installed because the cabinet file D:\cab1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. The path and name of the cabinet may be different, but might often… Read more

VS 2008 SP1 fails to install because of missing packages from the cache

Some customers are reporting that Microsoft Visual Studio 2008 SP1 is failing to install with the following error in the HTML log you can view from the error dialog. Patch (C:UsersheathsAppDataLocalTEMPWebDesignerCore_KB950278.msp) install failed on product (Microsoft Office Enterprise 2007). Msi Log: Microsoft Visual Studio 2008 SP1_20080816_141317516-Microsoft Office Enterprise 2007-MSP0.txt Final Result: Installation failed with error… Read more

Visual Studio 2008 Service Pack 1 Released

Microsoft .NET Framework 3.5 Service Pack 1, Visual Studio 2008 Service Pack 1, and Team Foundation Server 2008 Service Pack 1 have been released. This is a big release on the heals of SQL Server 2008 which has a dependency on .and includes NET Framework 3.5 SP1. This is a big release with many new… Read more

Enable BITS Logging

Microsoft Visual Studio 2008 Service Pack 1 uses a new bootstrap application that chains several packages together for a seamless installation experience. Because VS2008 SP1 contains a lot of fixes and new features, it is also quite large – almost 3 times as large as VS2005 SP1. To download all this data, we use the… Read more