none
Issues with M. Net Framework 4 RRS feed

  • Question

  • Trying to use a new updated version of udk that requires frame 4. I get a fatal error every time I try to install. I already tried several strategies.
    Uninstalling all frameworks, using the clean up kit, doing a fresh install. Short of a reformat I've done everything I could find on it.

    Not the least of which:
    http://support.microsoft.com/kb/976982

    Though, 1 point of confusion is that
    "Note The cleanup tool does not let you remove the .NET Framework 2.0 in Windows Vista or later versions because the .NET Framework is installed as an operating system component."

    Any info would be appreciated. I really hate reformatting.

    ============================================================
    Action: Performing Action on Exe at C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.0-KB956250-v6001-x64.msu...
    [12/29/2011, 15:25:58]Launching CreateProcess with command line = wusa.exe "C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.0-KB956250-v6001-x64.msu" /quiet /norestart[12/29/2011, 15:26:2]Exe (C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.0-KB956250-v6001-x64.msu) failed with 0x1 - Incorrect function. .[12/29/2011, 15:26:2]PerformOperation on exe returned exit code 1 (translates to HRESULT = 0x1)
    [12/29/2011, 15:26:2] Action complete
    [12/29/2011, 15:26:2]Error 0x1 is mapped to Custom Error: Success[12/29/2011, 15:26:2]Overwrite the current error to S_OK.[12/29/2011, 15:26:2]Wait for Item (Windows6.1-KB958488-v6001-x64.msu) to be available[12/29/2011, 15:26:2]Windows6.1-KB958488-v6001-x64.msu is now available to install[12/29/2011, 15:26:2]Created new DoNothingPerformer for File item[12/29/2011, 15:26:2]No CustomError defined for this item.[12/29/2011, 15:26:2]Wait for Item (SetupUtility.exe) to be available[12/29/2011, 15:26:2]SetupUtility.exe is now available to install[12/29/2011, 15:26:2]Creating new Performer for Exe item[12/29/2011, 15:26:2]Created new ExePerformer for Exe item
    [12/29/2011, 15:26:2] Action: Performing Action on Exe at C:\242904aaa4d4b7538cadd179a6\SetupUtility.exe...
    [12/29/2011, 15:26:2]Launching CreateProcess with command line = SetupUtility.exe /screboot[12/29/2011, 15:26:2]Exe log file(s) :[12/29/2011, 15:26:2]C:\Users\Michael\AppData\Local\Temp\dd_SetupUtility.txt[12/29/2011, 15:26:2]Log File C:\Users\Michael\AppData\Local\Temp\dd_SetupUtility.txt exists and will be added to the Watson upload list[12/29/2011, 15:26:2]Exe (C:\242904aaa4d4b7538cadd179a6\SetupUtility.exe) succeeded.[12/29/2011, 15:26:2]Exe Log File: dd_SetupUtility.txt
    [12/29/2011, 15:26:2] Action complete
    [12/29/2011, 15:26:2]Error 0 is mapped to Custom Error: [12/29/2011, 15:26:2]Wait for Item (netfx_Extended.mzz) to be available[12/29/2011, 15:26:2]netfx_Extended.mzz is now available to install[12/29/2011, 15:26:2]Created new DoNothingPerformer for File item[12/29/2011, 15:26:2]No CustomError defined for this item.[12/29/2011, 15:26:2]Wait for Item (netfx_Extended_x64.msi) to be available[12/29/2011, 15:26:2]netfx_Extended_x64.msi is now available to install[12/29/2011, 15:26:2]Creating new Performer for MSI item
    [12/29/2011, 15:26:2] Action: Performing Action on MSI at C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\netfx_Extended_x64.msi...
    [12/29/2011, 15:26:2]Log File C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_20111229_152550255-MSI_netfx_Extended_x64.msi.txt does not yet exist but may do at Watson upload time[12/29/2011, 15:26:2]Calling MsiInstallProduct(C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\netfx_Extended_x64.msi, EXTUI=1[12/29/2011, 15:26:29] Returning IDOK. INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ][12/29/2011, 15:26:34]MSI (C:\Users\Michael\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\netfx_Extended_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20111229_152550255-MSI_netfx_Extended_x64.msi.txt[12/29/2011, 15:26:34]PerformOperation returned 1603 (translates to HRESULT = 0x80070643)
    [12/29/2011, 15:26:34] Action complete
    [12/29/2011, 15:26:34]OnFailureBehavior for this item is to Rollback.
    [12/29/2011, 15:26:34] Action: Performing actions on all Items...

    [12/29/2011, 15:26:34] Action complete
    [12/29/2011, 15:26:34] Action complete
    [12/29/2011, 15:26:34]Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:00:44).[12/29/2011, 15:26:42]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus   

    Thursday, December 29, 2011 9:17 PM

Answers

  • I managed to put a bandaid on my problem thanks to this guys idea.

     

    I FIGURED IT OUT AND I GOT IT WORKING!!!!!!

    After about 10 hours trying all different things. Looking at all different threads. I found a solution that I did not see anywhere and it worked!

    I went to "C:\Windows\Microsoft.NET" there is a directory called "assembly".

    I looked in the directory and found some subdirectories with lots of old dot net 4 files. I renamed the directory assembly2 and tried to install Dot Net 4 and it worked!!!!

    (You can't delete the assembly directory unless you take ownership of it but you can rename it.)

    It seems that something was in the old "assembly" directory.

    Everything is working fine now. How come that is not mentioned anywhere? I bet many people are having this problem.

    Thank you for all of your help.

    Ira


    -------------------------

     

    I say bandaid as it doesnt completely fix the problem. After this windows update crops up with updates for .framework 4. When I install those I'm back to where I started.  Works fine as long as I don't update.

    The bandaid is good enough. This is just too much a pain to deal with anymore.

     

     

    Saturday, December 31, 2011 7:31 PM

All replies

  • First, your problems with .NET Framework 4.0 have NOTHING to do with other frameworks on your system, embedded or not.

    What is your Windows version and service pack level?

    If you have Vista, is SP1 (and, preferably SP2) installed? You must have SP1 installed on Vista, or .NET Framework 4.0 cannot be installed.

    There is no point of confusion on embedded frameworks in Vista and Windows 7. You CANNOT remove .NET Frameworks that come as part of the OS. For Vista, versions 2.0 and 3.0 are embedded. For Win 7, 2.0, 3.0 and 3.5 are embedded. If you have attempted to manually remove files or edited your registry trying to remove these frameworks, you will have to repair or reinstall your OS.

    Here are the steps I recommend:

    Follow 'irarab's solution in his answer in this thread:

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/3cc78f3c-d782-4f90-9035-1b6675890af7/

    Download the standalone installer for .NET Framework 4.0:

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718

    Clear your %temp% directory. Disable your AV software.

    Run the .NET Framework 4.0 standalone installer As Administrator.

    If the install fails again, supply full 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.

     


    • Edited by pvdg42 Friday, December 30, 2011 12:55 AM
    • Proposed as answer by Cathy KongModerator Monday, January 2, 2012 6:27 AM
    Friday, December 30, 2011 12:52 AM
  • I managed to put a bandaid on my problem thanks to this guys idea.

     

    I FIGURED IT OUT AND I GOT IT WORKING!!!!!!

    After about 10 hours trying all different things. Looking at all different threads. I found a solution that I did not see anywhere and it worked!

    I went to "C:\Windows\Microsoft.NET" there is a directory called "assembly".

    I looked in the directory and found some subdirectories with lots of old dot net 4 files. I renamed the directory assembly2 and tried to install Dot Net 4 and it worked!!!!

    (You can't delete the assembly directory unless you take ownership of it but you can rename it.)

    It seems that something was in the old "assembly" directory.

    Everything is working fine now. How come that is not mentioned anywhere? I bet many people are having this problem.

    Thank you for all of your help.

    Ira


    -------------------------

     

    I say bandaid as it doesnt completely fix the problem. After this windows update crops up with updates for .framework 4. When I install those I'm back to where I started.  Works fine as long as I don't update.

    The bandaid is good enough. This is just too much a pain to deal with anymore.

     

     

    Saturday, December 31, 2011 7:31 PM
  • Yes, that's irarab's procedure I linked for you.

    I'm glad all is well now. Happy New Year!

    Sunday, January 1, 2012 12:33 AM