Possible causes of Windows Vista hotfix install failures

The .NET Framework 3.5 beta 2 includes updates for the .NET Framework 2.0 and 3.0.  Since the .NET Framework 2.0 and 3.0 are installed as OS components on Windows Vista, the updates are delivered as Windows Vista hotfix packages.  We have seen some issues related to the installation of these .NET Framework 2.0 and 3.0 updates during .NET Framework 3.5 beta 2 setup that have turned out to be caused by known bugs with the Windows Vista hotfix installation engine.  The following items describe the issues we have seen so far with the Windows Vista hotfix installation engine and how to work around them to unblock .NET Framework 3.5 beta 2 installation:

Issue 1 - Installer encountered an error 0x8007177f. This machine is disabled for file encryption.

Aaron Ruckman described this issue in this blog post.  If you encounter this issue during .NET Framework 3.5 setup, the .NET Framework 2.0 update package will fail with error code 6015.  If you are running the .NET Framework 3.5 setup directly, you will see an error like the following in the setup error log:

[07/01/07,11:30:00] Microsoft .NET Framework 2.0SP1 (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 6015

If you are running VS 2008 setup (which chains the .NET Framework 3.5 as a prerequisite), you will see an error like the following in the setup error log:

[07/01/07,11:30:00] Microsoft .NET Framework v3.5: [2] Error code 6015 for this component means "This machine is disabled for file encryption."

This error means that there is a domain policy in effect that prevents file encryption using the Encrypting File System (EFS) from working.  There is a Windows Vista hotfix available to correct this issue, and information about obtaining it can be found in the knowledge base article located at http://support.microsoft.com/kb/933595.

Issue 2 - Installer encountered an error 0x80073712.

On some Windows Vista systems, it is possible that the OS component store has gotten into a corrupt state.  When this happens, the Windows Features control panel will be empty, and any Windows Vista hotfixes that you attempt to install will indicate that they are not applicable.  If you are running the .NET Framework 3.5 setup directly, you will see an error like the following in the setup error log:

[07/01/07,11:30:00] Microsoft .NET Framework 2.0SP1 (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1

If you are running VS 2008 setup (which chains the .NET Framework 3.5 as a prerequisite), you will see an error like the following in the setup error log:

[07/01/07,11:30:00] Microsoft .NET Framework v3.5: [2] Error code 1 for this component means "Incorrect function."

There are steps in the knowledge base article at http://support.microsoft.com/kb/931712 that can be used to update the registry in order to repair the Windows Vista component store in order to work around this error.  To summarize the steps listed in that knowledge base article, you can do the following:

  1. Open an administrative command prompt by clicking on the Start menu, choosing All Programs, then Accessories, then right-clicking on the Command Prompt item and choosing Run as administrator
  2. Type the following command:  reg delete HKLM\COMPONENTS /v StoreDirty /f

After running this command, you can re-run .NET Framework 3.5 or VS 2008 setup and hopefully resolve this error.

Note that return code 1 from a Windows Vista hotfix package means that the package is not applicable on the system.  However, this StoreDirty registry value is not the only possible cause of this error for .NET Framework 2.0 and 3.0 hotfixes.  The same error can appear in the setup logs if you previously had the beta 1 version or some pre-beta 2 CTP version of the .NET Framework 3.5 installed on your Windows Vista system and the old beta was not uninstalled prior to installing beta 2.  If the above workaround does not help, you can try the following to remove any pre-beta 2 versions of the .NET Framework 2.0 and 3.0 update packages for Windows Vista:

  1. Go to the Programs and Feature control panel
  2. Click the link at the top left labeled View installed updates
  3. Locate any updates named Hotfix for Microsoft Windows (KB110806), Hotfix for Microsoft Windows (KB929300) and Hotfix for Microsoft Windows (KB930264), right-click on them and choose Uninstall if they are present on your system
  4. Reboot and try to install the .NET Framework 3.5 beta 2 again
Comments (12)
  1. Laughing.John says:

    On my vista machine I cannot remove KB929300 – there are no errors, but it just keeps coming back. It appears in the hotfix list despite me no longer having 3.5 beta installed.

    I have been able to remove KB110806 and KB930264 doesn’t appear to exist.

    I cannot install .Net 2.0 SP1 directly as I am not allowed and 3.5 will not install because of:

    The Windows update "Update for Windows (KB929300)" could not be installed because of an error: 2149842978 "" (Command line: ""C:Windowssystem32WUSA.exe" "C:UsersNWhymarkAppDataLocalTempdotnetfx3521022.081033dotnetmspx86NetFX3.0-KB929300-v6000-x86.msu" /quiet /norestart")

    I have mailed my logs to the setup team but not heard back – I expect they’re very busy!

  2. Hi Laughing.John – I’m not sure how to explain why the beta version of KB929300 will not uninstall correctly on your system.  The log file c:windowslogscbscbs.log might have more detailed information about the cause of this failure.  I can try to take a look if you’d like to send it to me at Aaron.Stebner (at) microsoft (dot) com.

    It might also help to try to reinstall the beta of the .NET Framework 3.5 in order to reinstall that beta version of KB929300 and then try again to uninstall it.

    If that doesn’t help, I’m afraid you may have to try to repair/re-install your OS to resolve this issue.

  3. こんにちは! 少しの間落ち着いた天気が続いていたかと思いきや、今日は台風 13 号の接近に伴って、夜は激しい雨が降るところが多いようです。 皆さん、くれぐれも気をつけてくださいね! さて、今回は久々にまた

  4. Grams says:

    I keep getting error code 80070645 when installing an Microsoft .NET Framework 3.5 Family Update (KB959209) x86

    Download size: 1.4 MB

    You may need to restart your computer for this update to take effect.

    Update type: Important

    This update is applicable to Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2. The Microsoft .NET Framework 3.5 Family Update provides compatibility roll-up updates for customer reported issues found after the release of Microsoft .NET Framework 3.5 SP1. This update is provided to you and licensed under the Windows Vista and Windows Server 2008 License Terms.

    More information:


    Help and Support:


    Can someone please help me and tell me if this is a crucial update that I need and why it won't install.

  5. Hi Grams – Can you please use the tool described at blogs.msdn.com/…/6458047.aspx to gather all of your .NET Framework setup log files, upload the file named %temp%vslogs.cab that is produced by that tool to a file server (such as http://skydrive.live.com), then reply here with a link I can use to download the log files so I can take a further look?

  6. Frank says:

    Wonder if you can help, at wits end.  When installing on my Vista machine the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update (http://www.microsoft.com/…/details.aspx) all I get is a 1935 error.  Complete error is:

    Product: Microsoft Visual C++ 2005 Redistributable — Error 1935.An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.ATL,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x80073712. assembly interface: IAssemblyCacheItem, function: Commit, component: {66332652-9C28-58B1-A01F-C8B3B9A1E18E}

    I've installed Vista SP1 and SP2 and didn't help.  I ran the System Update Readiness Tool for Windows Vista, and in its logs I see the following errors:

    Checking System Update Readiness.

    Binary Version 6.0.6002.22359

    Package Version 8.0

    2010-06-19 15:49

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    (f) CBS Catalog Corrupt 0x800B0100 servicingPackagesPackage_75_for_KB958481~31bf3856ad364e35~x86~~

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    (f) CSI Unexpected Failure 0x00000000 winsxsManifestsx86_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_8e053e8c6967ba9d.manifest x86_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_8e053e8c6967ba9d

    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxsManifestsx86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.manifest x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c


    Seconds executed: 2187

    Found 3 errors

     CSI Unexpected Failure Total count: 1

     CSI Manifest Failed Catalog Check Total count: 1

     CBS Catalog Corrupt Total count: 1

    Unavailable repair files:





    I REALLY don't want to have to re-install Vista to fix this.  Is there anything I can do?  Is it possible to get these repair files in place and have the readiness tool fix the problem?  Thank you for any help you can give at all!!!

  7. Hi Frank – I'd suggest trying the steps listed at the end of the blog post at blogs.msdn.com/…/9303167.aspx and/or the steps listed at http://www.raymond.cc/…/fix-blank-or-empty-list-in-vista-turn-windows-features-on-or-off-optionalfeaturesexe to see if they help in this scenario.

Comments are closed.

Skip to main content