none
Error 0xC8000222 installing .NET 4.0.30319 on Win7-64 Pro with 3.5.1 RRS feed

  • Question

  • After a recent HD problem, I had to start from a factory image on a new HD.  Most everything is now running except Windows Update (I have not yet figured out that problem either).  I downloaded the title .NET and it fails with ".NET Framework has not been installed because: HRESULT 0xC8000222."  The "Microsoft Error Reporting Service" just closed after searching (no results).  Here is the tail end of the Log File:

    Windows6.1-KB958488-v6001-x64.msu is now available to install
    [7/17/2012, 7:20:21]Creating new Performer for Exe item
    [7/17/2012, 7:20:22]Created new ExePerformer for Exe item
    [7/17/2012, 7:20:22]WU Service was already enabled or was running
    [7/17/2012, 7:20:22]WU Service: EnsureWUServiceIsNotDisabled succeeded
    [7/17/2012, 7:20:22]Launching CreateProcess with command line = wusa.exe "C:\fe076b9c4fd57ebb07201175589998\Windows6.1-KB958488-v6001-x64.msu" /quiet /norestart
    [7/17/2012, 7:20:22]Exe (C:\fe076b9c4fd57ebb07201175589998\Windows6.1-KB958488-v6001-x64.msu) failed with 0xc8000222 - (null).
    [7/17/2012, 7:20:22]PerformOperation on exe returned exit code 3355443746 (translates to HRESULT = 0xc8000222)
    [7/17/2012, 7:20:22] Action complete
    [7/17/2012, 7:20:22]Error 0xc8000222 is mapped to Custom Error:
    [7/17/2012, 7:20:22]OnFailureBehavior for this item is to Rollback.
    [7/17/2012, 7:20:22] Action complete
    [7/17/2012, 7:20:22] Action complete
    [7/17/2012, 7:20:22]Sending Manifest Report
    [7/17/2012, 7:20:22]Final Result: Installation failed with error code: (0xC8000222) (Elapsed time: 0 00:06:26).

    Any help would be appreciated.

    Thanks

    Tuesday, July 17, 2012 9:08 PM

Answers

  • Try this sequence of 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:

    http://www.microsoft.com/en-us/download/details.aspx?id=17718

    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:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=E0DA314F-6216-4A18-BC6B-7D29CF83AF20&displaylang=e&displaylang=en

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

    The complete log set is needed for analysis.

    Tuesday, July 17, 2012 9:26 PM
  • Hi DonAZ,

    "Most everything is now running except Windows Update (I have not yet figured out that problem either)."

    I'm regret to say we must solve Windows Update issue first.

    Please refer to this thread http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/windows-update-failing-0xc8000222/6d55c63a-316c-4e9d-97b2-538bc783cdad to repair WU first.

    So Which updates are failing? However, you may try these:

    1. Run  Windows update troubleshooter.

    2. Reset Windows Update Components.

    Also refer to “Troubleshoot problems with installing updates ,  http://windows.microsoft.com/en-us/windows7/Troubleshoot-problems-with-installing-updates

    Please let me know if you have fixed that update issue.

    Regards,


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

    Thursday, July 19, 2012 10:04 AM
    Moderator

All replies

  • Try this sequence of 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:

    http://www.microsoft.com/en-us/download/details.aspx?id=17718

    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:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=E0DA314F-6216-4A18-BC6B-7D29CF83AF20&displaylang=e&displaylang=en

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

    The complete log set is needed for analysis.

    Tuesday, July 17, 2012 9:26 PM
  • Hi DonAZ,

    "Most everything is now running except Windows Update (I have not yet figured out that problem either)."

    I'm regret to say we must solve Windows Update issue first.

    Please refer to this thread http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/windows-update-failing-0xc8000222/6d55c63a-316c-4e9d-97b2-538bc783cdad to repair WU first.

    So Which updates are failing? However, you may try these:

    1. Run  Windows update troubleshooter.

    2. Reset Windows Update Components.

    Also refer to “Troubleshoot problems with installing updates ,  http://windows.microsoft.com/en-us/windows7/Troubleshoot-problems-with-installing-updates

    Please let me know if you have fixed that update issue.

    Regards,


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

    Thursday, July 19, 2012 10:04 AM
    Moderator
  • Hi DonAZ,

    Since you haven't back. I'll close this thread.

    The right order to solve your issue is:

    1. Follow my setups to fix Windows Update first.

    2. If WU installed successfully, follow MVP's workaround to slove .NET error.

    Regards,


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

    Thursday, July 26, 2012 7:11 AM
    Moderator
  • Can you please verify my vslogs.cab

    https://skydrive.live.com/redir?resid=B1D26A0FFA3CD584!210

    Thank you

    Abe

    Tuesday, October 22, 2013 10:34 PM
  • Hello, Mersh01.

    From your logs "Windows6.1-KB958488-v6001-x64.msu) failed with 0xc8000222 - (null).
    [10/22/2013, 12:9:59]PerformOperation on exe returned exit code 3355443746 (translates to HRESULT = 0xc8000222)"

    The issue is that your OS is not up to date. You need to install SP1 for Windows 7 and subsequent updates, then for the steps I provided in an earlier post in this thread.

    See Barry Wang's answer in this thread about Error 0xc8000222:

    http://social.msdn.microsoft.com/Forums/vstudio/en-US/16fe6a54-3ae8-4799-8934-d98fe5816a8d/problem-while-installing-net-40-please-help?forum=netfxsetup

    • Proposed as answer by PARAG.WAGHELA Thursday, October 30, 2014 6:40 PM
    • Unproposed as answer by PARAG.WAGHELA Thursday, October 30, 2014 6:41 PM
    Wednesday, October 23, 2013 2:27 PM
  • 1.) open "cmd"

     2.) type in command "net stop "WuAuServ" (disable windows update)

     3.) Head over to Run ( Win+R ) and type in "%windir%" (this command line enable you to head over to your microsoft windows system folder)

    4.) Find the folder "SoftwareDistribution" and rename it as "SDold"

    5.) Then, go back the previous command prompt and also run the command line "net start WuAuServ"

    6.) At this point, try to install. NET Framework again.


    I hope this will help solve the problem if you have questions in mind please do comment it below the post I will be glad to answer them all.
    • Proposed as answer by PARAG.WAGHELA Thursday, October 30, 2014 6:41 PM
    Thursday, October 30, 2014 6:41 PM
  • 1.) open "cmd"

     2.) type in command "net stop "WuAuServ" (disable windows update)

     3.) Head over to Run ( Win+R ) and type in "%windir%" (this command line enable you to head over to your microsoft windows system folder)

    4.) Find the folder "SoftwareDistribution" and rename it as "SDold"

    5.) Then, go back the previous command prompt and also run the command line "net start WuAuServ"

    6.) At this point, try to install. NET Framework again.


    I hope this will help solve the problem if you have questions in mind please do comment it below the post I will be glad to answer them all.
    • Proposed as answer by PARAG.WAGHELA Thursday, October 30, 2014 6:42 PM
    Thursday, October 30, 2014 6:42 PM
  • It´s Greate!!!
    Monday, January 12, 2015 8:03 PM