MSI (s) (00:C4) : This following file was not removed, because it is protected by Windows: D:WINDOWSwinsxsPoliciesx86_policy.8.0._1fc8b3b9a1e18e3b_x-ww_Īfter rollback completes, a policy is now redirecting applications that, in this case, link to the CRT 8.0 assembly including msvcm80.dll, msvcp80.dll, and msvcr80.dll to another version that does not exist (7.762).
This is confirmed in the following log lines. If an error occurs between the time when the policy file is installed, and the binaries and manifest for an assembly are installed, the policy is not removed because of Windows File Protection. Because of a problem in the native fusion library sxs.dll on those two platforms, using the MsiAssembly and MsiAssemblyName tables do not yield correct results when files are on use, typically during servicing scenarios.
On Windows XP where Windows side-by-side assemblies were introduced, and on Windows Server 2003, the VC merge modules (MSMs) install the policy, catalogs, manifest, and binaries directly using the Directory and File tables.
The policy file that controls to which version of a Windows side-by-side assembly an application is bound, and is used to update all applications using a particular assembly to the updated version, is sequenced to be installed before the updated binaries.
What causes this issue is Windows File Protection and how files are sequenced in the patch to be installed. You may need to install the VC redistributable package from a machine where SP1 successfully installed if you see an error like 25007 above when attempting to reinstall SP1. To work around this issue, remove orphaned Windows Installer packages and free additional disk space to meet the recommended minimum requirements to install SP1 depending on which applications you have installed, as documented on the download page for each patch package. Setup could not load fusion with LoadLibraryShim(). NET Framework 2.0, you might see an error that reads,Įrror 25007.Error occurred while initializing fusion. If you attempt to repair Visual Studio 2005 or the. Click on OK to terminate the application.
The application failed to initialize properly (0xc0150004). When attempting to start an application, you might see a dialog entitled “Application Error” that reads, Such applications include Windows Live Messenger and even Visual Studio 2005 itself. The arguments are: Īfter rollback, applications that depend on Visual C/C++ (VC) runtimes including ATL, MFC, CRT, and OpenMP may not run anymore. This may indicate a problem with this package. The installer has encountered an unexpected error installing this package.
Free some disk space and click Retry, or click Cancel to exit.Īnother common error code is Windows Installer error 2908, which indicates that Windows Installer could not register a particular component. You might see an error like the following that reads,Įrror 1307.There is not enough disk space to install this file: D. When installing Visual Studio 2005 Service Pack 1, there are a number of errors that might occur due to insufficient disk space.