Error 0xC8000222 when trying to Install .NET Framework on Windows 7 64 bit RRS feed

  • Question

  • I am getting Error 0xC8000222 when trying to Install .NET Framework.  I recently had one of my HD's die on me and I found this thread

    I have followed all the steps described in the proper order and my issue was not resolved.  I have collected my logs and uploaded them to SkyDrive.!104&authkey=!AFDEAMySVhVHoCQ

    Any help would be appreciated.

    edit:  here are my logs from the installer

    OS Version = 6.1.7600, Platform 2
    OS Description = Windows 7 - x64 Home Premium Edition
    CommandLine = D:\b401ec5606b0eea40003866445\\Setup.exe /x86 /x64
    TimeZone = Pacific Daylight Time
    Initial LCID = 1033
    Using Simultaneous Download and Install mechanism
    Operation: Installing
    Package Name = Microsoft .NET Framework 4 Setup
    Package Version = 4.0.30319
    User Experience Data Collection Policy: AlwaysUploaded
    Number of applicable items: 11
    Exe (D:\b401ec5606b0eea40003866445\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    ServiceControl operation succeeded!
    ServiceControl operation succeeded!
    Exe (D:\b401ec5606b0eea40003866445\Windows6.1-KB958488-v6001-x64.msu) failed with 0xc8000222 - (null).
    Final Result: Installation failed with error code: (0xC8000222) (Elapsed time: 0 00:00:12).

    • Edited by SBurch Tuesday, September 18, 2012 5:55 AM
    Tuesday, September 18, 2012 5:49 AM


All replies

  • I cannot find an install log for .NET 4.0 in your vslogs. Is it possible that you cleared your %temp% directory after the last install attempt before you ran Collect.exe?

    Please try these steps:

    Follow ALL these steps exactly:

    Before trying to install .NET Framework 4.0, execute this command from an ELEVATED Command Prompt provided by the .NET Framework Team:

    "This issue is likely caused by a bad ACL on assembly\tmp folder. After installing updates, the ACL propagates to installed assembly folders in both 4.0 & legacy GAC.  If those updates were installed by WU or another user, the propagated ACL will prevent install of the same assembly by the current user.

    A work around would be to reset the ACL on GAC dirs.

    for /F %D in ('dir %WINDIR%\assembly %WINDIR%\Microsoft.NET\assembly /s /b /a:d') do takeown /F %D && icacls %D /reset /T"

    After running that command, follow these steps:

    Please follow these instructions exactly:

    1. Download a fresh copy of the standalone installer for .NET Framework 4.0:

    2. Also, clear your %temp% directory and disable your AV software.

    The %temp% directory is a reference to the Temp folder associated with the current user. To clear it, do the following:

    Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.

    3. Run the standalone installer from step 1 As Administrator.

    Note: Just using an administrator account is NOT enough. To activate full privileges, you must right-click the installer, then select Run as administrator.

    If the install fails, provide complete install logs as follows:

    Please collect your install logs with this:

    After you run Collect.exe, you'll find in your %temp% directory. Please upload to a public site, like SkyDrive, and post the link here.

    Tuesday, September 18, 2012 12:24 PM
  • Hi SBurch,

    Thanks for your post.

    I also haven't found .NET installation logs from your

    I noted you mentioned one of your HD is die. Have you installed any software on it?

    After my research of the error 0xC8000222, it seems the error was always occured when you used Windows Update.

    For example, here is a thread to fix related issue

    I would recommend you use a standalone installer after you have tried the solution I mentioned. If this cannot fix your problem. Since .NET installation requires healthy WU. I would recommend you ask how to fix your Windows Udpate here 

    Since WU may corrupt due to your corrupt HD. In my opinion, I recommend you repair or reinstall your OS after you can make sure your HD is healthy.


    Barry Wang [MSFT]
    MSDN Community Support | Feedback to us

    Wednesday, September 19, 2012 7:58 AM