locked
Installation of Visual Studio 2010 SP1 fails (NDP40-KB2468871.exe returned exit code 1603) RRS feed

  • Question

  • HI,

    I currently have SP1 BETA installed and tried an upgrade to the final version of SP1, but failed. The log file gives the following information:

    Action: Performing Action on Exe at J:\NDP40-KB2468871.exe...

    [3/14/2011, 10:11:29]In PreCreateProcess
    [3/14/2011, 10:11:29]Launching CreateProcess with command line = NDP40-KB2468871.exe /q /norestart /pipe SectionName_3566521041 /log "C:\Users\FLORIN~1\AppData\Local\Temp"
    [3/14/2011, 10:13:32]Internal error from callee is0
    [3/14/2011, 10:13:32]J:\NDP40-KB2468871.exe - Exe installer does not provide a log file name
    [3/14/2011, 10:13:32]Exe (J:\NDP40-KB2468871.exe) failed with 0x80070643 - Fatal error during installation..
    [3/14/2011, 10:13:32]PerformOperation on exe returned exit code 1603 (translates to HRESULT = 0x80070643)
    [3/14/2011, 10:13:32] Action complete

    [3/14/2011, 10:13:32]Error 1603 is mapped to Custom Error:
    [3/14/2011, 10:13:32]OnFailureBehavior for this item is to Rollback.

    Monday, March 14, 2011 10:06 AM

All replies

  • Same here
    Simone Busoli
    Tuesday, March 15, 2011 11:59 AM
  • Sorry for the problems you're having.

    It would help us to see the rest of the logs. You can download and run the Visual Studio and .NET log collection utility from http://go.microsoft.com/?LinkId=8967043 and save %TEMP%\vslogs.cab to the Internet. If you need file hosting space, SkyDrive.com offters 25GB free with a Microsoft Live ID, such as the one you used for these forums.

    Please send me the URL privately via http://blogs.msdn.com/b/heaths/contact.aspx and I can take a look at the internet error causing this.

    Thank you.


    Visual Studio Professional Deployment Experience Team http://blogs.msdn.com/heaths
    Tuesday, March 15, 2011 7:37 PM
  • Hi Heath, thanks for you reply. I was able to solve it, I will post it here in case it's useful to anyone.

    The install package failed deterministically when installing NDP40-KB2468871, which is the update package for framework 4.0. The logs apparently didn't contain valuable information.

    Then I tried installing the above NDP alone (http://support.microsoft.com/kb/2468871) and it kept failing, this time the MSI logs showed that there were issues in writing registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Security\ServiceModel 4.0.0.0. I don't know the reason since I was running the installer with an admin user account, but changing the key permissions to give full control to administrators solved the problem.


    Simone Busoli
    Tuesday, March 15, 2011 10:05 PM
  • The log collection utility will actually capture all VS and .NET logs including the .NET GDR (KB2468871), as well as pertinent event logs. This will be helpful in determining the root cause of the issue, which is how the ACLs got changed on the registry key.

    Thank you.


    Visual Studio Professional Deployment Experience Team http://blogs.msdn.com/heaths
    Tuesday, March 15, 2011 11:31 PM
  • Heath, I have already submitted them during the failed installation process using the standard log collection mechanisms. I'm not sure I can now replicate the problem and thus forward you that information.
    Simone Busoli
    Tuesday, March 15, 2011 11:33 PM
  • I have two systems, sp1 fails on both as above.  On one, I was actually able to get NDP40-KB2468871 to install manually, but not on the other, and even on that first on, sp1 still fails.
    Wednesday, March 16, 2011 3:04 PM
  • Sorry for the problems you're having.

    We're investigating why the ACLs are incorrect. In the meantime, can you see my first reply above for instructions to collect logs from both machines and post them so I can have a look. This will give us more information as to what is changing and perhaps why. Dont' worry that on the first system it installed now, the logs should still be there in %TEMP% and our log collection tool will grab them.

    Thank you.


    Visual Studio Professional Deployment Experience Team http://blogs.msdn.com/heaths
    Wednesday, March 16, 2011 7:43 PM
  • As a data point, we have the exact same problem when installing SP1 on one of our systems here (fails trying to install NDP40). I haven't tried the suggested registry fix yet. SP1 installed fine on several of our other systems. What is particularly painful about this failure is that it occurs near the end of the install (eg. 40 minutes in), and then it rolls back the SP1 install (which takes another 40 minutes).
    Thursday, March 17, 2011 8:14 PM
  • We've facing the same problem which can't install VS2010 SP1 into OS Win7 with 64bit. 
    Below is the sample log which we try to run the NDP alone.
    Pleaes help. We managed to install in WinVista.
    OS Version Information: ...
    
    [3/18/2011, 14:10:20]OS Version = 6.1.7601, Platform 2, Service Pack 1
    [3/18/2011, 14:10:20]OS Description = Windows 7 - x64 Service Pack 1
    
    [3/18/2011, 14:10:20] OS Version Information 
    
    [3/18/2011, 14:10:20] Environment details: ...
    
    [3/18/2011, 14:10:20]CommandLine = N:\3ad56b1a0318027a52cf34\\Setup.exe 
    
    [3/18/2011, 14:10:20] Environment details 
    
    [3/18/2011, 14:10:20]Loading localized engine data for language 1033 from N:\3ad56b1a0318027a52cf34\1033\LocalizedData.xml
    [3/18/2011, 14:10:20] Entering Function: LocalizedData::CreateLocalizedData...
    
    [3/18/2011, 14:10:20] exiting function/method
    
    [3/18/2011, 14:10:20] succeeded
    
    [3/18/2011, 14:10:20] Entering Function: EngineData::CreateEngineData...
    
    [3/18/2011, 14:10:20]Current SetupVersion = 1.0
    [3/18/2011, 14:10:20]SetupVersion specified in ParameterInfo.xml is '1.0'
    [3/18/2011, 14:10:20]patch NDP40-KB2468871.msp added
    [3/18/2011, 14:10:20]Adding Item type "Patches", local path (not applicable)
    [3/18/2011, 14:10:20]No ProcessBlock element
    [3/18/2011, 14:10:20]No ServiceBlock element
    [3/18/2011, 14:10:20]Using Simultaneous Download and Install mechanism
    [3/18/2011, 14:10:20] exiting function/method
    
    [3/18/2011, 14:10:20] succeeded
    
    [3/18/2011, 14:10:20] MaintenanceMode determination: evaluating EnterMaintenanceModeIf...
    
    [3/18/2011, 14:10:20]evaluating EnterMaintenanceModeIf:
    [3/18/2011, 14:10:20]returning false
    
    [3/18/2011, 14:10:20] MaintenanceMode determination evaluates to 'not in maintenance mode'
    
    [3/18/2011, 14:10:20] Operation Type: ...
    
    [3/18/2011, 14:10:20]Operation: Installing
    
    [3/18/2011, 14:10:20] Operation Type 
    
    [3/18/2011, 14:10:20] Package details: KB2468871...
    
    [3/18/2011, 14:10:20]Package Name = KB2468871
    [3/18/2011, 14:10:20]Package Version = 10.0.30319
    
    [3/18/2011, 14:10:20] Package details 
    
    [3/18/2011, 14:10:20] User Experience Data Collection Policy: ...
    
    [3/18/2011, 14:10:20]User Experience Data Collection Policy: Disabled
    
    [3/18/2011, 14:10:20] User Experience Data Collection Policy 
    
    [3/18/2011, 14:10:20] Entering Function: UiDataT::CreateUiDataT...
    
    [3/18/2011, 14:10:20]Loading file - N:\3ad56b1a0318027a52cf34\UiInfo.xml
    [3/18/2011, 14:10:20]Add to schema collection schema file - N:\3ad56b1a0318027a52cf34\SetupUi.xsd
    [3/18/2011, 14:10:20]Successfuly found file N:\3ad56b1a0318027a52cf34\1033\SetupResources.DLL 
    [3/18/2011, 14:10:21]Successfuly found file N:\3ad56b1a0318027a52cf34\Strings.xml 
    [3/18/2011, 14:10:21] exiting function/method
    
    [3/18/2011, 14:10:21] succeeded
    
    [3/18/2011, 14:10:21] Global Block Checks: Checking for global blockers...
    
    [3/18/2011, 14:10:21] Global Block Checks no blocking conditions found
    
    [3/18/2011, 14:10:21]OpenFileMapping fails with last error: 6
    [3/18/2011, 14:10:21]The handle to the section is Null
    [3/18/2011, 14:10:21]OpenFileMapping fails with last error: 6
    [3/18/2011, 14:10:21]The handle to the section is Null
    [3/18/2011, 14:10:21] Applicability for Installing: evaluating each item...
    
    [3/18/2011, 14:10:21] Determining state: of N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp...
    
    [3/18/2011, 14:10:21]evaluating ApplicableIf:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiXmlBlob: this patch is applicable
    
    [3/18/2011, 14:10:21] Exists evaluated to true
    
    [3/18/2011, 14:10:21]evaluating IsPresent:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed
    
    [3/18/2011, 14:10:21] Exists evaluated to false
    
    [3/18/2011, 14:10:21] Determining state of N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp - available but not verified yet
    
    [3/18/2011, 14:10:21]evaluating ApplicableIf:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiXmlBlob: this patch is applicable
    
    [3/18/2011, 14:10:21] Exists evaluated to true
    
    [3/18/2011, 14:10:21]evaluating IsPresent:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed
    
    [3/18/2011, 14:10:21] Exists evaluated to false
    
    [3/18/2011, 14:10:21] Applicability for Installing determination is complete
    
    [3/18/2011, 14:10:21] Applicability Result Count: ...
    
    [3/18/2011, 14:10:21]Number of applicable items: 1
    
    [3/18/2011, 14:10:21] Applicability Result Count 
    
    [3/18/2011, 14:10:21]evaluating ApplicableIf:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiXmlBlob: this patch is applicable
    
    [3/18/2011, 14:10:21] Exists evaluated to true
    
    [3/18/2011, 14:10:21]evaluating IsPresent:
    [3/18/2011, 14:10:21] Exists: evaluating...
    
    [3/18/2011, 14:10:21]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed
    
    [3/18/2011, 14:10:21] Exists evaluated to false
    
    [3/18/2011, 14:10:21]
    Summary Information:
    1.Microsoft .NET Framework 4 Client Profile
    2.Microsoft .NET Framework 4 Extended
    
    [3/18/2011, 14:10:23]Successfuly found file N:\3ad56b1a0318027a52cf34\1033\EULA.rtf 
    [3/18/2011, 14:10:26] Action: System Requirement Checks...
    
    [3/18/2011, 14:10:26] Action: Disk space check for items being downloaded...
    
    [3/18/2011, 14:10:26]Drive:[C:\] Bytes Needed:[192231424] Bytes Available:[54306508800]
    
    [3/18/2011, 14:10:26] Action complete
    
    [3/18/2011, 14:10:26] Action: Enumerating incompatible processes...
    
    [3/18/2011, 14:10:26]No Blocking Processes
    
    [3/18/2011, 14:10:26] Action complete
    
    [3/18/2011, 14:10:26] Action: Enumerating incompatible services...
    
    [3/18/2011, 14:10:26]No Blocking Services
    
    [3/18/2011, 14:10:26] Action complete
    
    [3/18/2011, 14:10:26] Action complete
    
    [3/18/2011, 14:10:26]Launching Download and Install operations simultaneously.
    [3/18/2011, 14:10:26] Action: Downloading and/or Verifying Items...
    
    [3/18/2011, 14:10:26]Verifying Digital Signatures: N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp
    [3/18/2011, 14:10:26] N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp: Verifying signature for NDP40-KB2468871.msp...
    
    [3/18/2011, 14:10:27]N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp - Signature verified successfully for NDP40-KB2468871.msp
    
    [3/18/2011, 14:10:27] N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp Signature verified successfully for NDP40-KB2468871.msp
    
    [3/18/2011, 14:10:27]Signature verification succeeded for NDP40-KB2468871.msp
    [3/18/2011, 14:10:27]File N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp, locked for install. 
    [3/18/2011, 14:10:27]Verifying Digital Signatures: N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp Success
    
    [3/18/2011, 14:10:27] Action complete
    
    [3/18/2011, 14:10:27]evaluating IsPresent:
    [3/18/2011, 14:10:27] Exists: evaluating...
    
    [3/18/2011, 14:10:27]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed
    
    [3/18/2011, 14:10:27] Exists evaluated to false
    
    [3/18/2011, 14:10:27]Starting install of item 'NDP40-KB2468871' at tickCount = 2228458
    [3/18/2011, 14:10:26]calling PerformAction on an installing performer
    [3/18/2011, 14:10:26] Action: Performing actions on all Items...
    
    [3/18/2011, 14:10:26]Wait for Item (NDP40-KB2468871.msp) to be available
    [3/18/2011, 14:10:27]NDP40-KB2468871.msp is now available to install
    [3/18/2011, 14:10:27]Creating new Performer for Patches item
    [3/18/2011, 14:10:27] Entering Function: BaseMspInstallerT >::PerformAction...
    
    [3/18/2011, 14:10:27] Action: Performing Install on MSP: N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp targetting Product: Microsoft .NET Framework 4 Client Profile...
    
    [3/18/2011, 14:10:27]Successfully called MsiEnableLog with log file set to C:\Users\CLGan\AppData\Local\Temp\KB2468871_20110318_141020933-Microsoft .NET Framework 4 Client Profile-MSP0.txt
    [3/18/2011, 14:10:27]Log File C:\Users\CLGan\AppData\Local\Temp\KB2468871_20110318_141020933-Microsoft .NET Framework 4 Client Profile-MSP0.txt does not yet exist but may do at Watson upload time
    [3/18/2011, 14:10:27]about to call MsiInstallProduct with PATCH="N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp" on product {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}(C:\Windows\Installer\75e99.msi) to install patches.
    [3/18/2011, 14:10:27]Patch (N:\3ad56b1a0318027a52cf34\NDP40-KB2468871.msp) Install failed on product (Microsoft .NET Framework 4 Client Profile). Msi Log: 
    [3/18/2011, 14:10:27]MSI returned 0x663
    [3/18/2011, 14:10:27] Entering Function: MspInstallerT >::Rollback...
    
    [3/18/2011, 14:10:27] exiting function/method
    
    [3/18/2011, 14:10:27] 
    
    [3/18/2011, 14:10:27] Action Rollback changes
    
    [3/18/2011, 14:10:27]PerformMsiOperation returned 0x663
    [3/18/2011, 14:10:27] exiting function/method
    
    [3/18/2011, 14:10:27] PerformMsiOperation returned 0x663
    
    [3/18/2011, 14:10:27]OnFailureBehavior for this item is to Rollback.
    
    [3/18/2011, 14:10:27] Action complete
    
    [3/18/2011, 14:10:27]Final Result: Installation failed with error code: (0x80070663), "This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package. " (Elapsed time: 0 00:00:07).
    [3/18/2011, 14:10:47]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
    
    Friday, March 18, 2011 6:15 AM
  • Same to us. Tried many times and approaches.
    Friday, March 18, 2011 6:16 AM
  • Sorry for the issues you're experiencing.

    Please run the VS and .NET log collection utility from http://go.microsoft.com/?LinkId=8967043 and save %TEMP%\vslogs.cab that it creates to someplace on the Internet we can download it, like SkyDrive.com,w hcih gives you 25GB free with the same Live ID you use for forums. Please post the URL here or send a private message with the URL if you prefer.

    From those logs we can determine the root cause of the issue. The specific error you cite just means the package cannot be opened. Without seeing more log information, the issue could be this: http://bit.ly/hGUWlh.

    I've also sent notification to the .NET team and will follow up with them on this specific issue.

    Thank you.


    Visual Studio Professional Deployment Experience Team http://blogs.msdn.com/heaths
    Friday, March 18, 2011 10:28 PM
  • Dear Heath,

    Please check the following link for details.

    http://cid-a044775eb051566b.office.live.com/self.aspx/VS2010/vslogs.cab

    Hope can help out of problem we faced in Win7 64bit with VS2010 installation. Computer is fully patched.

     

    Sunday, March 20, 2011 9:32 AM
  • I have another exit codу of NDP40-KB2468871.exe - 1642

    Launching CreateProcess with command line = NDP40-KB2468871.exe /q /norestart /pipe SectionName_979633174 /CEIPconsent /log "C:\Users\aemanov\AppData\Local\Temp"
    [3/15/2011, 14:13:53]Internal error from callee is0
    [3/15/2011, 14:13:53]D:\Sp1\NDP40-KB2468871.exe - Exe installer does not provide a log file name
    [3/15/2011, 14:13:53]Exe (D:\Sp1\NDP40-KB2468871.exe) failed with 0x8007066a - The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade..
    [3/15/2011, 14:13:53]PerformOperation on exe returned exit code 1642 (translates to HRESULT = 0x8007066a)
    [3/15/2011, 14:13:53] Action complete

    Beside that I can't install 2 updates:
    1) Security Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2416472)

    2) Security Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2160841)

    May be these things are depends one on another.

     

    Running NDP40-KB2468871.exe separately give me:

    KB2468871 does not apply, or is blocked by another condition on your computer.

     

    When trying to setup SP1 after fail it want to setup:

    SetupUtility
    Dotfuscator Software Services - Community Edition
    VSTO 4.0 Runtime x64
    Microsoft Visual C++ Compilers 2010 Standard x86 - 10.0.40219
    Microsoft Visual C++ Compilers 2010 Standard x64 - 10.0.40219
    NDP40-KB2468871.exe

     


    -- Alexei

    Monday, March 21, 2011 8:34 AM
  • The problem solved after removing .NET4 with this utility:

    http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

    and installing .NET 4. Those two KB installed successfully, and VS2010SP1 too. Thanks.


    -- Alexei
    Monday, March 21, 2011 9:52 AM
  • What version of .NET 4 did you have installed before? Did you install 4.0 separate from VS2010 RTM, or did it get installed with VS2010 RTM?
    Visual Studio Professional Deployment Experience Team http://blogs.msdn.com/heaths
    Monday, March 21, 2011 6:38 PM
  • Hello Heath,

    I too am having similar problems with VS 2010 SP1. I also tried installing ASP.Net MVC 3 from the Web Platform Installer but get a 1603 error. I've uploaded the vslogs.cab file here:

    http://dl.dropbox.com/u/17133472/vslogs.cab

    I ran the setreg 3 & 9 to false which cured a problem I was having with File Transfer Manager not working, but not the VS issues. I'd be most grateful if you can check the vslogs and see if there is anything there.

    Thanks

    Here's the error from the Web Platform Installer:

    Action: Performing Action on Exe at c:\temp\ext47334\VS10-KB2483190-x86.exe...

    [4/7/2011, 16:17:56]Launching CreateProcess with command line = VS10-KB2483190-x86.exe /q /norestart
    [4/7/2011, 16:18:11]c:\temp\ext47334\VS10-KB2483190-x86.exe - Exe installer does not provide a log file name
    [4/7/2011, 16:18:11]Exe (c:\temp\ext47334\VS10-KB2483190-x86.exe) failed with 0x80070643 - Fatal error during installation. .
    [4/7/2011, 16:18:11]PerformOperation on exe returned exit code 1603 (translates to HRESULT = 0x80070643)
    [4/7/2011, 16:18:11] Action complete

    [4/7/2011, 16:18:11]Error 1603 is mapped to Custom Error:
    [4/7/2011, 16:18:11]OnFailureBehavior for this item is to Rollback.

    Thursday, April 7, 2011 3:13 PM
  • From the logs,

    MSI (s) (C4:70) [16:20:12:894]: Executing op: AssemblyCopy(SourceName=7ft5izgb.dll|FSharp.Compiler.Server.Shared.dll,SourceCabKey=FSharp_Compiler_Server_Shared_Dll_GAC_File,DestName=FSharp.Compiler.Server.Shared.dll,Attributes=16896,FileSize=26488,PerTick=65536,,VerifyMedia=1,,,,,ComponentId={01F15BE3-6853-36D3-746E-5D8163CDAFC3},IsManifest=1,,,AssemblyMode=0,)
    DEBUG: Error 2902:  Operation ixfAssemblyCopy called out of sequence.

    Try this solution to see if that works for you: http://sourcecodebean.com/archives/mvc-3-rtm-install-error-after-upgrading-to-vs2010-sp1/977/comment-page-1#comment-8806.


    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment
    Friday, April 8, 2011 9:49 PM
  • Hi

    I am having the same issue on two XP machines here. Both of these machines had the Beta of SP1.

    Both get the Exe (E:\tmp\mu_visual_studio_2010_sp1_x86_dvd_651704\NDP40-KB2468871.exe) failed with 0x8007066a - The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
    d that you have the correct upgrade patch.

    I have tried all the suggestions here an non are working.

    Regards

    Daniel

    Wednesday, April 13, 2011 5:55 AM
  • Sorry to hear you're having problems.

    To better understand the root cause, we're going to need a bit more information about your system (specifically, about the 4.0 Framework). To gather this infomation, can you run the collection utility from http://go.microsoft.com/?LinkId=8967043 and save %TEMP%\vslogs.cab that it creates to someplace on the Internet from where we can download it, such as SkyDrive.com, which gives you 25GB free with the same Live ID you use for forums. Please post the URL here or send a private message with the URL if you prefer.

    Wednesday, April 13, 2011 10:51 PM
  • thanks for your time,

    I have the same problem. Tried to install SP1 AND now

    only KB2468871 which gave me below log. I'm not able to interpret the file ...!

    Hope the log helps somebody to help me

    thanks for your time
    ed

    PS: how would I attach this file!?

    Installation Log

    Message Types:

    Errors   Verbose   Messages  

    Message Details:

    Date Time  

      
    © 2009 Microsoft Corporation. All rights reserved. Terms of Use.


    [4/13/2011, 16:23:50] OS Version Information:


    [4/13/2011, 16:23:50]OS Version = 6.1.7601, Platform 2, Service Pack 1
     [4/13/2011, 16:23:50]OS Description = Windows 7 - x64 Ultimate Edition Service Pack 1


    [4/13/2011, 16:23:50] OS Version Information


    [4/13/2011, 16:23:50] Environment details:


    [4/13/2011, 16:23:50]CommandLine = D:\dca6883d84efe32ffab04384e9\\Setup.exe
    [4/13/2011, 16:23:50]TimeZone = Romance Daylight Time
     [4/13/2011, 16:23:50]Initial LCID = 1031


    [4/13/2011, 16:23:50] Environment details

    [4/13/2011, 16:23:50]Loading localized engine data for language 1033 from D:\dca6883d84efe32ffab04384e9\1033\LocalizedData.xml
     
    [4/13/2011, 16:23:50] Entering Function: LocalizedData::CreateLocalizedData


     [4/13/2011, 16:23:50] exiting function/method


    [4/13/2011, 16:23:50] succeeded


    [4/13/2011, 16:23:50] Entering Function: EngineData::CreateEngineData


     [4/13/2011, 16:23:50]Current SetupVersion = 1.0
     [4/13/2011, 16:23:50]SetupVersion specified in ParameterInfo.xml is '1.0'
     [4/13/2011, 16:23:50]patch NDP40-KB2468871.msp added
     [4/13/2011, 16:23:50]Adding Item type "Patches", local path (not applicable)
     [4/13/2011, 16:23:50]No ProcessBlock element
     [4/13/2011, 16:23:50]No ServiceBlock element
     [4/13/2011, 16:23:50]Using Simultaneous Download and Install mechanism
     [4/13/2011, 16:23:50] exiting function/method


    [4/13/2011, 16:23:50] succeeded


    [4/13/2011, 16:23:50] MaintenanceMode determination: evaluating EnterMaintenanceModeIf


     [4/13/2011, 16:23:50]evaluating EnterMaintenanceModeIf:
     [4/13/2011, 16:23:50]returning false


    [4/13/2011, 16:23:50] MaintenanceMode determination evaluates to 'not in maintenance mode'


    [4/13/2011, 16:23:50] Operation Type:


    [4/13/2011, 16:23:50]Operation: Installing


    [4/13/2011, 16:23:50] Operation Type


    [4/13/2011, 16:23:50] Package details: KB2468871


     [4/13/2011, 16:23:50]Package Name = KB2468871
     [4/13/2011, 16:23:50]Package Version = 10.0.30319


    [4/13/2011, 16:23:50] Package details


    [4/13/2011, 16:23:50] User Experience Data Collection Policy:


    [4/13/2011, 16:23:50]User Experience Data Collection Policy: AlwaysUploaded


    [4/13/2011, 16:23:50] User Experience Data Collection Policy


    [4/13/2011, 16:23:50] Entering Function: UiDataT::CreateUiDataT


     [4/13/2011, 16:23:50]Loading file - D:\dca6883d84efe32ffab04384e9\UiInfo.xml
     [4/13/2011, 16:23:50]Add to schema collection schema file - D:\dca6883d84efe32ffab04384e9\SetupUi.xsd
     [4/13/2011, 16:23:50]Successfuly found file D:\dca6883d84efe32ffab04384e9\1033\SetupResources.DLL
    [4/13/2011, 16:23:50]Successfuly found file D:\dca6883d84efe32ffab04384e9\Strings.xml
    [4/13/2011, 16:23:50] exiting function/method


    [4/13/2011, 16:23:50] succeeded


    [4/13/2011, 16:23:50] Global Block Checks: Checking for global blockers

     

    [4/13/2011, 16:23:50] Global Block Checks no blocking conditions found

    [4/13/2011, 16:23:50]OpenFileMapping fails with last error: 6
     [4/13/2011, 16:23:50]The handle to the section is Null
     [4/13/2011, 16:23:50]OpenFileMapping fails with last error: 6
     [4/13/2011, 16:23:50]The handle to the section is Null
     
    [4/13/2011, 16:23:50] Applicability for Installing: evaluating each item


     
    [4/13/2011, 16:23:50] Determining state: of D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp


     [4/13/2011, 16:23:50]evaluating ApplicableIf:
     
    [4/13/2011, 16:23:50] Exists: evaluating


     [4/13/2011, 16:23:51]MsiXmlBlob: this patch is applicable


    [4/13/2011, 16:23:51] Exists evaluated to true

    [4/13/2011, 16:23:51]evaluating IsPresent:
     
    [4/13/2011, 16:23:51] Exists: evaluating


     [4/13/2011, 16:23:51]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed


    [4/13/2011, 16:23:51] Exists evaluated to false

     
    [4/13/2011, 16:23:51] Determining state of D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp - available but not verified yet

    [4/13/2011, 16:23:51]evaluating ApplicableIf:
     
    [4/13/2011, 16:23:51] Exists: evaluating


     [4/13/2011, 16:23:51]MsiXmlBlob: this patch is applicable


    [4/13/2011, 16:23:51] Exists evaluated to true

    [4/13/2011, 16:23:51]evaluating IsPresent:
     
    [4/13/2011, 16:23:51] Exists: evaluating


     [4/13/2011, 16:23:51]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed


    [4/13/2011, 16:23:51] Exists evaluated to false

     
    [4/13/2011, 16:23:51] Applicability for Installing determination is complete


    [4/13/2011, 16:23:51] Applicability Result Count:


    [4/13/2011, 16:23:51]Number of applicable items: 1


    [4/13/2011, 16:23:51] Applicability Result Count

    [4/13/2011, 16:23:51]evaluating ApplicableIf:
     
    [4/13/2011, 16:23:51] Exists: evaluating


     [4/13/2011, 16:23:51]MsiXmlBlob: this patch is applicable


    [4/13/2011, 16:23:51] Exists evaluated to true

    [4/13/2011, 16:23:51]evaluating IsPresent:
     
    [4/13/2011, 16:23:51] Exists: evaluating


     [4/13/2011, 16:23:51]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed


    [4/13/2011, 16:23:51] Exists evaluated to false

    [4/13/2011, 16:23:51]
    Summary Information:
    1.Microsoft .NET Framework 4 Client Profile
    2.Microsoft .NET Framework 4 Extended

     [4/13/2011, 16:23:54]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
     [4/13/2011, 16:23:59]Successfuly found file D:\dca6883d84efe32ffab04384e9\1033\EULA.rtf

    [4/13/2011, 16:24:6] Action: System Requirement Checks


     
    [4/13/2011, 16:24:6] Action: Disk space check for items being downloaded


     [4/13/2011, 16:24:6]Drive:[C:\] Bytes Needed:[192231424] Bytes Available:[64409493504]


    [4/13/2011, 16:24:6] Action complete


    [4/13/2011, 16:24:6] Action: Enumerating incompatible processes


     [4/13/2011, 16:24:6]No Blocking Processes


    [4/13/2011, 16:24:6] Action complete


    [4/13/2011, 16:24:6] Action: Enumerating incompatible services


     [4/13/2011, 16:24:6]No Blocking Services


    [4/13/2011, 16:24:6] Action complete

     
    [4/13/2011, 16:24:6] Action complete

    [4/13/2011, 16:24:6]Launching Download and Install operations simultaneously.
     
    [4/13/2011, 16:24:6] Action: Downloading and/or Verifying Items


     [4/13/2011, 16:24:6]Verifying Digital Signatures: D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp
     
    [4/13/2011, 16:24:6] D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp: Verifying signature for NDP40-KB2468871.msp


     [4/13/2011, 16:24:7]D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp - Signature verified successfully for NDP40-KB2468871.msp


    [4/13/2011, 16:24:7] D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp Signature verified successfully for NDP40-KB2468871.msp

    [4/13/2011, 16:24:7]Signature verification succeeded for NDP40-KB2468871.msp
     [4/13/2011, 16:24:7]File D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp, locked for install.
    [4/13/2011, 16:24:7]Verifying Digital Signatures: D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp Success

    [4/13/2011, 16:24:7] Action complete

    [4/13/2011, 16:24:7]evaluating IsPresent:
     
    [4/13/2011, 16:24:7] Exists: evaluating


     [4/13/2011, 16:24:7]MsiGetCachedPatchPath with patch code {F353B50F-0400-3F6A-A7DE-3A28538B8F48} failed


    [4/13/2011, 16:24:7] Exists evaluated to false

    [4/13/2011, 16:24:7]Starting install of item 'NDP40-KB2468871' at tickCount = 2889122
     [4/13/2011, 16:28:34]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
     [4/13/2011, 16:29:10]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
     [4/13/2011, 16:32:48]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
     [4/13/2011, 16:24:6]calling PerformAction on an installing performer
     
    [4/13/2011, 16:24:6] Action: Performing actions on all Items


     [4/13/2011, 16:24:6]Wait for Item (NDP40-KB2468871.msp) to be available
     [4/13/2011, 16:24:7]NDP40-KB2468871.msp is now available to install
     [4/13/2011, 16:24:7]Creating new Performer for Patches item
     
    [4/13/2011, 16:24:7] Entering Function: BaseMspInstallerT >::PerformAction


     
    [4/13/2011, 16:24:7] Action: Performing Install on MSP: D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp targetting Product: Microsoft .NET Framework 4 Client Profile


     [4/13/2011, 16:24:7]Successfully called MsiEnableLog with log file set to C:\Users\admin\AppData\Local\Temp\KB2468871_20110413_162350834-Microsoft .NET Framework 4 Client Profile-MSP0.txt
     [4/13/2011, 16:24:7]Log File C:\Users\admin\AppData\Local\Temp\KB2468871_20110413_162350834-Microsoft .NET Framework 4 Client Profile-MSP0.txt does not yet exist but may do at Watson upload time
     [4/13/2011, 16:24:7]about to call MsiInstallProduct with PATCH="D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp" on product {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}(C:\Windows\Installer\10d0769.msi) to install patches.
     [4/13/2011, 16:31:3]Patch (D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp) Install succeeded on product (Microsoft .NET Framework 4 Client Profile). Msi Log:
    [4/13/2011, 16:31:3]MSI returned 0x0: no error


    [4/13/2011, 16:31:3] Action


    [4/13/2011, 16:31:3] Action: Performing Install on MSP: D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp targetting Product: Microsoft .NET Framework 4 Extended


     [4/13/2011, 16:31:3]Successfully called MsiEnableLog with log file set to C:\Users\admin\AppData\Local\Temp\KB2468871_20110413_162350834-Microsoft .NET Framework 4 Extended-MSP1.txt
     [4/13/2011, 16:31:3]Log File C:\Users\admin\AppData\Local\Temp\KB2468871_20110413_162350834-Microsoft .NET Framework 4 Extended-MSP1.txt does not yet exist but may do at Watson upload time
     [4/13/2011, 16:31:3]about to call MsiInstallProduct with PATCH="D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp" on product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}(C:\Windows\Installer\10d076f.msi) to install patches.
     [4/13/2011, 16:32:2] Returning IDOK. INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
     [4/13/2011, 16:32:7]Patch (D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp) Install failed on product (Microsoft .NET Framework 4 Extended). Msi Log:
    [4/13/2011, 16:32:7]MSI returned 0x643
     
    [4/13/2011, 16:32:7] Entering Function: MspInstallerT >::Rollback


     [4/13/2011, 16:32:7]about to call MsiInstallProduct with MSIPATCHREMOVE="D:\dca6883d84efe32ffab04384e9\NDP40-KB2468871.msp" on product {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}(C:\Windows\Installer\10d0769.msi) to remove patches.
     [4/13/2011, 16:34:13]MsiInstallProduct returned 0x0
     [4/13/2011, 16:34:13] exiting function/method


    [4/13/2011, 16:34:13]


    [4/13/2011, 16:34:13] Action Rollback changes

    [4/13/2011, 16:34:13]PerformMsiOperation returned 0x643
     [4/13/2011, 16:34:13] exiting function/method

    [4/13/2011, 16:34:13] PerformMsiOperation returned 0x643

    [4/13/2011, 16:34:13]OnFailureBehavior for this item is to Rollback.

    [4/13/2011, 16:34:13] Action complete

    [4/13/2011, 16:34:13]Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:10:23).
     [4/13/2011, 16:34:45]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus

     

    Thursday, April 14, 2011 6:15 AM
  • Please download and run http://bit.ly/vscollect and upload %TEMP%\vslogs.cab to a web share after it completes. Please send me the URL via http://blogs.msdn.com/b/heaths/contact.aspx and be sure to reference this thread in the subject or body somewhere so I can easily associate the two.
    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment
    • Proposed as answer by edkaufmann Friday, April 15, 2011 11:55 AM
    Thursday, April 14, 2011 5:55 PM
  • Hi Heath,

    I sent according to your instruction

    thanks for your time, ed

    Friday, April 15, 2011 11:55 AM
  • What is going on with this?

    I am having the same error.

    I have tried the .Net Framework cleanup tool and reinstall the 4.0 framework but that did not help.

    Here is my log file but I don't think it gives you any new information.

    =================================================================

     

    Installation Log

    Message Types: <input id="errCB" type="checkbox" /> <label class="pointer" for="errCB">Errors</label>   <input id="vbeCB" type="checkbox" /> <label class="pointer" for="vbeCB">Verbose</label>   <input id="msgCB" type="checkbox" /> <label class="pointer" for="msgCB">Messages</label>  
    Message Details: <input id="tCB" type="checkbox" /> <label class="pointer" for="tCB">Date Time</label>        
    © 2009 Microsoft Corporation. All rights reserved. Terms of Use. <form id="messages" class="messages">
    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x86 Enterprise Edition Service Pack 1
    OS Version Information
    CommandLine = C:\cca4f43f0008b99c485524c58a\\Setup.exe
    TimeZone = Eastern Daylight Time
    Initial LCID = 1033
    Environment details
    exiting function/method
    succeeded
    Current SetupVersion = 1.0
    SetupVersion specified in ParameterInfo.xml is '1.0'
    patch NDP40-KB2468871.msp added
    No ProcessBlock element
    No ServiceBlock element
    Using Simultaneous Download and Install mechanism
    exiting function/method
    succeeded
    MaintenanceMode determination evaluates to 'not in maintenance mode'
    Operation: Installing
    Operation Type
    Package Name = KB2468871v2
    Package Version = 10.0.30319
    Package details
    User Experience Data Collection Policy: AlwaysUploaded
    User Experience Data Collection Policy
    Loading file - C:\cca4f43f0008b99c485524c58a\UiInfo.xml
    Add to schema collection schema file - C:\cca4f43f0008b99c485524c58a\SetupUi.xsd
    Successfuly found file C:\cca4f43f0008b99c485524c58a\1033\SetupResources.DLL
    Successfuly found file C:\cca4f43f0008b99c485524c58a\Strings.xml
    exiting function/method
    succeeded
    Global Block Checks no blocking conditions found
    OpenFileMapping fails with last error: 6
    The handle to the section is Null
    OpenFileMapping fails with last error: 6
    The handle to the section is Null
    Exists evaluated to true
    Exists evaluated to false
    Determining state of C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp - available but not verified yet
    Exists evaluated to true
    Exists evaluated to false
    Applicability for Installing determination is complete
    Number of applicable items: 1
    Applicability Result Count
    Exists evaluated to true
    Exists evaluated to false

    Summary Information:

    1. Microsoft .NET Framework 4 Client Profile
    2. Microsoft .NET Framework 4 Extended

    WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
    Successfuly found file C:\cca4f43f0008b99c485524c58a\1033\EULA.rtf
    Action complete
    Launching Download and Install operations simultaneously.
    C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp - Signature verified successfully for NDP40-KB2468871.msp
    C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp Signature verified successfully for NDP40-KB2468871.msp
    File C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp, locked for install.
    Action complete
    Exists evaluated to false
    Starting install of item 'NDP40-KB2468871' at tickCount = 12994508
    WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
    calling PerformAction on an installing performer
    Wait for Item (NDP40-KB2468871.msp) to be available
    NDP40-KB2468871.msp is now available to install
    Creating new Performer for Patches item
    Successfully called MsiEnableLog with log file set to C:\Users\weavert\AppData\Local\Temp\KB2468871v2_20110727_150838834-Microsoft .NET Framework 4 Client Profile-MSP0.txt
    Log File C:\Users\weavert\AppData\Local\Temp\KB2468871v2_20110727_150838834-Microsoft .NET Framework 4 Client Profile-MSP0.txt does not yet exist but may do at Watson upload time
    about to call MsiInstallProduct with PATCH="C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp" on product {3C3901C5-3455-3E0A-A214-0B093A5070A6}(C:\WINDOWS\Installer\b5e6c3.msi) to install patches.
    Patch (C:\cca4f43f0008b99c485524c58a\NDP40-KB2468871.msp) Install failed on product (Microsoft .NET Framework 4 Client Profile). Msi Log:
    exiting function/method
    Action Rollback changes
    exiting function/method
    PerformMsiOperation returned 0x643
    Action complete
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:35).
    </form>

     

    Wednesday, July 27, 2011 7:20 PM
  • We'd need to see all the logs. Please download and run http://bit.ly/vscollect and upload the share somewhere we can access.
    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment
    Wednesday, July 27, 2011 10:56 PM
  • Here you go.

    CollectInfo.txt      https://www.sugarsync.com/pf/D227437_78_6564429580
    MsiInv.txt        https://www.sugarsync.com/pf/D227437_78_6564486284
    vslogs.cab     https://www.sugarsync.com/pf/D227437_78_6564438736
    Thanks for your help.
    -
    I am trying to remember how all this started.  Here is the best I recall.
    • I installed VS2010
    • I installed VS2010 SP1 (all is well, works for months)
    • I installed Window Phone 7 SDK
    • Started VS2010 and it comes up with a cryptic message about a partial install.
    • Stop VS2010 and try to install SP1 again, fails on KB2468871

    A complete removal of the Window Phone 7, VS2010 SP1, VS2010, .Net Framework 4 did not resolve the problem.

    All development has stopped until this is resolved.

     

    Friday, July 29, 2011 2:30 PM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed.

     

    • Proposed as answer by edkaufmann Saturday, July 30, 2011 6:37 AM
    Friday, July 29, 2011 9:07 PM
  • thanks a million,

    adding that file worked for me as well

    PS: I gave up 3 months ago .... what a surprise, thanks!

    ed

    Saturday, July 30, 2011 6:39 AM
  • I'm seeing this 66A installation failure for .NET updates on two fresh installs with minimal software installed - and no Visual Studio.One machine is a sysprepped clone of the other, so they are genetically identical and are failing on the same updates dated 8/9/2011. I've tried the solutions in this thread as well as other fixes but to no avail.

    I'll send Heath my log file link and hope there is another solution.

    Friday, August 12, 2011 2:34 PM
  • From the logs you sent me, this appears to be a different problem than those above. The patch chainer - the application responsible for installing a single or multiple products, error handling, retry logic,e tc. - reports that the patch doesn't apply. In the cases above, the chainer though the patch applied but when Windows Installer attempt to install it the patch didn't (this was typically a problem with registry corruption for that patch).

    It's possible that a superseding patch is installed. Can you check Programs and Features in your control panel, click View Installed Updates, and see if other patches are already applied to .NET Framework 4 Client Profile.


    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment
    Friday, August 12, 2011 11:59 PM
  • Thanks a lot it worked like a charm.
    Monday, August 15, 2011 12:56 PM
  • Hi Heath. Thanks for taking a look at the system logs I posted. There are two .NET 4 client profile patches already installed on this machine:

    KB2518870

    KB2478663

     

    The remaining updates that won't install are:

    KB2416472

    KB2468871

    KB2468871

    KB2533523

    Those above in bold are commonly failing on two separate but nearly identical computers.


    Tuesday, August 16, 2011 3:09 PM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed. 

     

    This solution worked for me as well. I too also question why this file wasn't already present since I used the .NET Cleanup Utility and re-install .NET4. Doesn't really make any sense.
    Wednesday, August 17, 2011 1:48 PM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed. 

     

     

    This is the same fix that worked for me with the one additional step: I was also missing the file C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Xml.Serialization.dll.  I copied that file from another machine in addition to the one listed above and then the update worked.  This was after many many attempts to uninstall, run the cleanup tool, reinstall, etc.  I fail to understand how this file could still be missing after so many uninstalls/reinstalls.

    Thanks very much for your help with this though!

    Ken

    Tuesday, August 23, 2011 6:19 PM
  • On my XP machine, the cleanup tool whilst running in minimum startup mode via msconfig, got it working.

    Not so on my W7 32. 

    But thanks to weaver4, copying System.Xml.Serialization.dll did it (found a copy in C:\Program Files\Windows Live\Mesh).


    • Edited by d.duck.esq Friday, September 9, 2011 4:32 AM
    Friday, September 9, 2011 4:32 AM
  • Thanks Heath for putting me in touch with Peter. After gathering more log files and regmon output he found a solution for my problem, which seemed to be caused by the Windows installer being unable to update .NET because the registry was telling it components existed which did not:

    Delete the REG_SZ alphanumeric values under this key:

     

    HKEY_CLASSES_ROOT\Installer\Products\DFC90B5F2B0FFA63D84FD16F6BF37C4B

    Leave the REG_MULTI_SZ value named "Patches", but clear out the contents of the value. Then completely uninstall the .NET components and reinstall.

    Friday, September 9, 2011 1:36 PM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed. 

     

     

    This is the same fix that worked for me with the one additional step: I was also missing the file C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Xml.Serialization.dll.  I copied that file from another machine in addition to the one listed above and then the update worked.  This was after many many attempts to uninstall, run the cleanup tool, reinstall, etc.  I fail to understand how this file could still be missing after so many uninstalls/reinstalls.

    Thanks very much for your help with this though!

    Ken

    This solved the installation for me as well.  I didn't have another machine to draw from, but the files are in the patch itself.  I downloaded the x64 version of the patch from http://www.microsoft.com/download/en/details.aspx?id=3556 and used 7-zip to extract several layers of exe and cab til I found System.Xml.Serialization.dll.x86 and System.Xml.Serialization.dll.amd64 and copied them respectively to the Framework and Framework64 directories with that final extension stripped.

    Thanks.

    Sunday, September 18, 2011 11:06 PM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed. 

     


    After trying a gazillion fixes (uninstalls, reinstalls, repairs, etc. etc.) obtaining the System.Xml.Serialization.dll file was the one that finally worked! I did not have another computer from which to copy it, so I downloaded the file from this freeware site: http://dllcentral.com/System.Xml.Serialization.dll/3.0.40818.0/download/

    I placed placed the file in two directories:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\

    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\

    Thanks so much for sharing the information!

    • Proposed as answer by elTorito Wednesday, October 5, 2011 7:44 AM
    • Unproposed as answer by elTorito Wednesday, October 5, 2011 7:45 AM
    Wednesday, September 21, 2011 12:23 AM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed. 

     

    Hey, this works for me , 3 days i tried to install KB2468871... i found the System.XML.Serialisation.dll in a Directory on my PC , i copied it to:
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Xml.Serialization.dll

    After this i can install the KB2468871

    Thanks
    Wednesday, October 5, 2011 7:48 AM
  • Hi Guys,

     

    Had the same problem in the following constellation:

    - Win7 Ultimate x64, fully patched up (apart from KB2468871, which I could not install of course)

    - Office 2010 x64

    - Visual Studio 2010 incl. SP1 

     

    Tried about everything else for about 1 full day that looked to be even remotely related to this problem (Uninstall/Reinstall .NET with/without Cleanup tool from Aaron Stebner, Uninstall/Reinstall VS2010 with/without Cleanup utility for VS.NET installation, web-install KB2468871, redistributable install KB2468871, even Uninstall/reinstall Office 2010 etc. etc. etc.). All to no avail.

     

    I was about ready to give up (huh, where can we find that in the dictionary of a programmer....) and continue more important work than solving problems that are to be solved by MS.

    Then as a last resort, found this thread, and I tried placing the (obviously) missing System.Xml.Serialization.dll file in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 and C:\Windows\Microsoft.NET\Framework64\v4.0.30319  (In my case, I found a copy in C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Xml.Serialization\v4.0_4.0.0.0__b77a5c561934e089, version 4.0.30319.450 to be exact)

    That proved to clear the path for KB2468871, and it successfully installed without a single glitch (No need to turn of antivirus, UAC, whatsoever, it installed the update as always) !

    Thanks for the solution / spread the word !

    I surely hope Microsoft picks up this one (How difficult can it be to release V3 of KB2468871 and include a step to make sure that the DLL is present and if not, place a fresh copy before commencing the patch install itself ?) Given the large number of people experiencing problems with this one, I would consider this a wise investment on MS-behalf, although I do realize they are doing their best , but are limited in terms the effort and time that can be spent on non-crtitical errors like these as well....

    Monday, October 17, 2011 11:29 AM
  • Thank you, this solved an issue.
    • Proposed as answer by echoeo Monday, November 21, 2011 12:04 AM
    Saturday, November 5, 2011 8:04 PM
  • It works for me either. I lost Sunday, looking for any resolution, trying to fix this and I didn't give up ! I'm  so happy now.
    Monday, November 21, 2011 12:06 AM
  • I am having the same issues in 2 different machines. I will send you my cab link as well if you are still addressing these issues.
    Friday, January 6, 2012 4:35 AM
  • I installed windows installer 4.5 and that resolved the problem. server 2003 x86. thanks to this post: http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/21154aaf-7e0e-4241-b38e-67995a20ba45/
    Sunday, January 22, 2012 6:03 AM
  • I think I found the issue.

    This file must exist for the install to succeed:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Xml.Serialization.dll

    I did not have this file in that directory.  I copied it over from another system and the install went properly.

    The question is:  Why was it not there?  I did an install of the 4.0 framework (that was on MSDN) and then did the KB2468871 patch immediately afterwords and it failed.

     

    It worked as hell!!! you made my day. Thank you a lot.

    If it is not a secret, how could you managed to find that solution?

    I started hate that "true MVP" professionals, which never helped but asked for logs and then disappeared from the topic. From my experience almost all "strange" errors were solved by some other guys instead of Microsoft tech-s.

    Wednesday, February 15, 2012 11:38 AM
  • Hi ,

    I had faced almost all problems as mentioned above in the post. Repairing .Net Framework Client profile solved the issue. After this I installed VS2010 SP1 image from ISO file and The installation goes thru fine , I get message that VS2010 SP1 installed suceessfully. But it is not shown up in th elist of installed programs. Running Silverlight5_tools says that this machine does not have SP1 installed.

    I have uploaded 2 files at https://skydrive.live.com/?cid=463B631DDD5B05C9&id=463B631DDD5B05C9%21120

    1. VSlogs.cab

    2. VSlogs_AfterInstallingSP1.cab.

    Let me know if you need any other details.

    Thanks in advace.


    sodesh

    Monday, April 16, 2012 1:17 PM
  • What does the Help->About dialog in Visual Studio 2010 show you? This will be in the top-left corner.

    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment

    Tuesday, April 17, 2012 7:37 PM
  • I have the same problem.  Tried downloading  VS SP1 standalone and it failed because it could not find the silverlight_sdk.msi (which should be part of the SP), then ran it from Windows Update and it still failed.   This is a waste of time and hard to believe that it is not fixed yet by Microsoft...really starting to loose faith in you guys.
    Sunday, May 27, 2012 12:42 PM
  • It may not be searching for that silverlight_sdk.msi that ships in the SP, which is included. Windows Installer often needs source locations for the original (RTM) products when repairing or sometimes even uninstalling (like as part of an upgrade to a newer version).

    If you run http://bit.ly/vscollect and share the resulting vslogs.cab on a share (like http://skydrive.com, which works with your Live ID and gives you 7GB free) we can take a look.


    - Heath @ http://blogs.msdn.com/heaths; Visual Studio Professional Deployment

    Tuesday, May 29, 2012 5:48 PM
  • Good News ...:)

    After doing a LOT of R&D I found that the Visual Studio Test Agent and Visual Studio Test Agent Controller services were the responsible for this error.

    I was able to instal after I stoped those 2 services from Task Manager.

    HAPPPY INSTALATION

    Friday, June 1, 2012 11:01 AM
  • This worked for me, too.  Thanks, mroset.   I just have one further question.  System.xml.serialization.dll is a 32 bit DLL.  Leaving a copy on ...Framework64\v4.0.30319 seems dangerous.   Is it?  Or is there a 64 bit variant somewhere?   Or should I just remove it after the install works.

    Max

    Wednesday, October 3, 2012 1:41 PM
  • I thought this was the answer, the install ran through very quickly, then I looked away for a second and when I came back it was rolling back...  *sigh*  Back to the drawing board.

    Thanks, Mike Devenney

    Tuesday, March 12, 2013 5:30 PM
  • May Allah bless you Roset.

    I have tried your solution and just copy the "System.Xml.Serialization.dll"  file from our another Developer's PC and paste it here "C:\Windows\Microsoft.NET\Framework\v4.0.30319". And I am able to Install Visual Studio 2010 SP1. You save my lots of time.

    may Allah bless you and thank you very much.

    Mohammad Saiful Islam

    Dhaka, Bangladesh.

    Thursday, June 20, 2013 7:29 AM
  • Setting the DWORD value of WOW64 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver to "0" on a x64 Win7 solved this problem for me.
    Saturday, August 17, 2013 9:29 PM