none
Error when installing VS 2012 Update 3 - The pipe is being closed.

    Frage

  • Hi,

    I'm trying to install VS2012 Update 3 on a brand new fresh Windows 8. I've installed Visual Studio 2012 Premium with no problems, but when I apply Update 3 it fails with:

     

    Setup Engine
    The pipe is being closed.

    KB2770057
    The pipe is being closed.

    Windows App Certification Kit x64 Patch
    User cancelled installation.

    I've tried uninstalling, rebooting etc., but with the same result.

    Can anyone give me a clue to what is wrong?

    Some of the log file is attached below:

    [0C68:017C][2013-07-04T13:33:04]: Prompt for source of package: WinACK_native_x64_en, payload: WinACK_native_x64_en, path: C:\Users\caj\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\020TT3LT\packages\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    [0C68:017C][2013-07-04T13:33:04]: MUX:  Next Source: Web, Attempted: 1, Limit:3
    [0C68:017C][2013-07-04T13:33:04]: MUX:  Source retrieved: Web
    [0C68:017C][2013-07-04T13:33:04]: MUX:  Package:WinACK_native_x64_en, PayloadId:WinACK_native_x64_en Url: http://go.microsoft.com/fwlink/?LinkId=302996&clcid=0x409, Attempting count: 1
    [0C68:017C][2013-07-04T13:33:04]: MUX:  Existing last unconfirmed source: Web
    [0C68:017C][2013-07-04T13:33:04]: Acquiring package: WinACK_native_x64_en, payload: WinACK_native_x64_en, download from: http://go.microsoft.com/fwlink/?LinkId=302996&clcid=0x409
    [0414:0C5C][2013-07-04T13:33:05]: Error 0x800b0003: Failed to get signer chain from authenticode certificate.
    [0C68:017C][2013-07-04T13:33:06]: MUX:  Source confirmed
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Installation size in bytes for package: msp_kb2770057 MaxAppDrive: 0  MaxSysDrive: 130510848  AppDrive: 0  SysDrive: 130510848
    [0C68:017C][2013-07-04T13:33:06]: Prompt for source of package: WinACK_x64_x86_en, payload: WinACK_x64_x86_en, path: C:\Users\caj\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\020TT3LT\packages\WinACK\Windows App Certification Kit x64-x86_en-us.msp
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Return Code:0x0 Msi Messages:0 Result Detail:InstallFiles Restart:None
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Reset execution Result
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Reset Result
    [0C68:017C][2013-07-04T13:33:06]: MUX:  Next Source: Web, Attempted: 1, Limit:3
    [0C68:017C][2013-07-04T13:33:06]: MUX:  Source retrieved: Web
    [0C68:0FE0][2013-07-04T13:33:06]: Applied execute package: msp_kb2770057, result: 0x0, restart: None
    [0C68:017C][2013-07-04T13:33:06]: MUX:  Package:WinACK_x64_x86_en, PayloadId:WinACK_x64_x86_en Url: http://go.microsoft.com/fwlink/?LinkId=302998&clcid=0x409, Attempting count: 1
    [0C68:017C][2013-07-04T13:33:06]: MUX:  Existing last unconfirmed source: Web
    [0C68:017C][2013-07-04T13:33:06]: Acquiring package: WinACK_x64_x86_en, payload: WinACK_x64_x86_en, download from: http://go.microsoft.com/fwlink/?LinkId=302998&clcid=0x409
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_MSP_PACKAGE message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to configure per-machine MSP package.
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Installation size in bytes for package: msp_kb2770057 MaxAppDrive: 0  MaxSysDrive: 0  AppDrive: 0  SysDrive: 0
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Return Code:0x800700E8 Msi Messages:0 Result Detail:0 Restart:None
    [0C68:0FE0][2013-07-04T13:33:06]: MUX:  Set Result: Return Code=-2147024664 (0x800700E8), Error Message=, Result Detail=, Vital=False, Package Action=Install, Package Id=msp_kb2770057
    [0C68:0FE0][2013-07-04T13:33:06]: Applied non-vital package: msp_kb2770057, encountered error: 0x800700e8. Continuing...
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to register the dependency on per-machine package.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to execute dependency action.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to register the dependency on per-machine package.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_DEPENDENCY message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:06]: Error 0x800700e8: Failed to register the dependency on per-machine package.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: UX aborted on download progress.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: UX aborted on cache progress.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: Failed while reading from internet and writing to: C:\Users\XXXX\AppData\Local\Temp\{29828f33-4679-462a-8c98-1c3507678922}\WinACK_x64_x86_en
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: Failed to download URL: http://go.microsoft.com/fwlink/?LinkId=302998&clcid=0x409
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: Failed attempt to download URL: 'http://go.microsoft.com/fwlink/?LinkId=302998&clcid=0x409' to: 'C:\Users\XXXX\AppData\Local\Temp\{29828f33-4679-462a-8c98-1c3507678922}\WinACK_x64_x86_en'
    [0C68:017C][2013-07-04T13:33:07]: MUX:  Set Result: Return Code=-2147023294 (0x80070642), Error Message=, Result Detail=, Vital=False, Package Action=Download_WinInet, Package Id=WinACK_x64_x86_en
    [0C68:017C][2013-07-04T13:33:07]: Error 0x80070642: Failed to acquire payload from: 'http://go.microsoft.com/fwlink/?LinkId=302998&clcid=0x409' to working path: 'C:\Users\XXX\AppData\Local\Temp\{29828f33-4679-462a-8c98-1c3507678922}\WinACK_x64_x86_en'
    [0C68:017C][2013-07-04T13:33:07]: Failed to acquire payload: WinACK_x64_x86_en to working path: C:\Users\XXXX\AppData\Local\Temp\{29828f33-4679-462a-8c98-1c3507678922}\WinACK_x64_x86_en, error: 0x80070642.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CLEAN_PACKAGE message to per-machine process.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:017C][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send BURN_ELEVATION_MESSAGE_TYPE_CACHE_CLEANUP message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to end session in per-machine process.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write message type to pipe.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to write send message to pipe.
    [0C68:0FE0][2013-07-04T13:33:07]: Error 0x800700e8: Failed to send message to per-machine process.
    [0C68:0FE0][2013-07-04T13:33:07]: MUX:  Apply Complete: Disk Space Used in bytes for Installation:  MaxAppDrive: 0  MaxSysDrive: 532635648  AppDrive: 0  SysDrive: 544120832
    [0C68:0FE0][2013-07-04T13:33:07]: MUX:  Free Disk Space after install:  SystemDrive C:\ 133321719808 bytes  AppDrive C:\ 133321719808 bytes
    [0C68:0FE0][2013-07-04T13:33:07]: MUX:  Set Result: Return Code=-2147024664 (0x800700E8), Error Message=, Result Detail=, Vital=True, Package Action=Install, Package Id=Apply Failure
    [0C68:0FE0][2013-07-04T13:33:07]: MUX:  Go to Finished page.
    [0C68:0FE0][2013-07-04T13:33:07]: Apply complete, result: 0x800700e8, restart: None, ba requested restart:  No
    

    Thanks!

    Casper

    Donnerstag, 4. Juli 2013 11:41

Antworten

  • These steps were successful for me:

    1.        Download ISO (used link above)
    2.        Unzip
    3.        Open command prompt as admin and navigate to the folder with vs2012.3.exe
    4.        Run and fail
    5.        Run .\VS2012.3\package\WinACK\Windows App Certification Kit x64-x86_en-us.msp
    6.        Run .\VS2012.3\package\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    7.        Run VS2012.3.exe again and … hopefully … succeed like I did after a great while.

    Montag, 15. Juli 2013 13:17
  • Hi Casper,

    Thanks for your post.

    Based on the error "The pipe is being closed" and the error list on your logs. It seems the issue was due to you are using a web installer. Could you please download the iso instead: http://go.microsoft.com/fwlink/?LinkId=301705

    If the issue cannot be solved. Please provide full logs with this tool http://aka.ms/vscollect  

    After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/   and share the link here.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Freitag, 5. Juli 2013 06:30
    Moderator
  • Installing the Windows App Certification Kit corrected this and allowed me to installed the IOS image successfully.

    http://msdn.microsoft.com/en-us/windows/apps/jj572486.aspx

    Donnerstag, 11. Juli 2013 14:38
  • Hi All,

    This problem still seems to be current. But after hours and hours and hours - I've got it working!

    Here is what I found:

    -- Installing this file: VS2012.3.iso - I get the The pipe is being closed error!

    -- Installing this file: mu_visual_studio_2012_update_3_x86_dvd_2364556.iso - It works!!

    Note: These were two separate downloads from the microsoft site, both containing 661 files and 2,185,338KB (2.08GB) - Only 1 works for me.

    I hope this helps.

    Cheers

    Donnerstag, 25. Juli 2013 01:01
  • Check Your Hash!

    I've been trying to get update 3 installed since it was announced.  I've tried all the suggestions in the other messages to no avail.  I did discover in the process that the previous updates did not install correctly either.

    Finally, I went back and tested the SHA1 on the .iso download link on http://www.microsoft.com/en-us/download/details.aspx?id=39305 and found it did not match.  I downloaded the .iso from MSDN subscriber downloads and verified the SHA1 was correct and it installed with no problem.

    Hope this saves some headaches and time (and maybe the downloads can be updated),

    John

    Dienstag, 30. Juli 2013 21:10

Alle Antworten

  • Hi Casper,

    Thanks for your post.

    Based on the error "The pipe is being closed" and the error list on your logs. It seems the issue was due to you are using a web installer. Could you please download the iso instead: http://go.microsoft.com/fwlink/?LinkId=301705

    If the issue cannot be solved. Please provide full logs with this tool http://aka.ms/vscollect  

    After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/   and share the link here.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Freitag, 5. Juli 2013 06:30
    Moderator
  • Hi Berry

    Thank you for the quick reply. I've already tried installing from the offline installer, but i gave me the exact same error.

    I've collected the logs and placed them here: http://sdrv.ms/13p379V

    Thanks!

    Casper

    Freitag, 5. Juli 2013 08:33
  • i have successfully completed installation from downloaded ISO file.

    BR Stanko

    Freitag, 5. Juli 2013 14:09
  • I have same issue with update 3
    Samstag, 6. Juli 2013 08:36
  • I am using the offline installer and having the same error
    Montag, 8. Juli 2013 09:38
  • I am getting the same error but in the error message I see Microsoft Visual Studio Team Foundation Server 2012 Object instead of KB2770057.
    Montag, 8. Juli 2013 15:28
  • Hello,

    I had this problem too after my system crashed in the middle of my first attempt to apply the update using the web installer.

    Here is what fixed it for me:

    1. Go to program manager (add/remove programs)

    2. Go to Installed Updates

    3. Uninstall Visual Studio 2012 Update 3

    4. Repair Install Visual Studio 2012

    5. Install Visual Studio 2012 Update 3 with the ISO installer

    Montag, 8. Juli 2013 19:39
  • I'm getting the errors too. Uninstall, repair, and reinstall did not work.

    See log. http://sdrv.ms/16lBOIu

    thx.


    ratman

    Dienstag, 9. Juli 2013 06:36
  • I too am getting this error.
    Dienstag, 9. Juli 2013 12:12
  • I am getting the same error. I used the web install for update 3. I am going to try uninstalling VS2012 and start from scratch, using the iso for the update. I will post my results when I am finished.
    Dienstag, 9. Juli 2013 18:32
  • Hi all,

    Thank you for report your problems here.

    This issue seems to be a hot issue which still do not have a solid answer. Could u please report this issue on: https://connect.microsoft.com/VisualStudio/feedback/CreateFeedbackForm.aspx?FeedbackFormConfigurationID=5303&FeedbackType=1

    Then paste the connect link back so that others can vote on it?

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Mittwoch, 10. Juli 2013 07:59
    Moderator
  • I'm getting this error as well. Installing from the iso makes no difference.

    
    Mittwoch, 10. Juli 2013 18:20
  • Same problem here using downloaded ISO file.
    Donnerstag, 11. Juli 2013 13:19
  • Installing the Windows App Certification Kit corrected this and allowed me to installed the IOS image successfully.

    http://msdn.microsoft.com/en-us/windows/apps/jj572486.aspx

    Donnerstag, 11. Juli 2013 14:38
  • Same here.  I was getting the "pipe is closed" error with both the online and ISO installs.  After install the App Certification Kit the install from the ISO was successful.  Thanks for sharing.

    Jon

    Donnerstag, 11. Juli 2013 15:51
  • These steps were successful for me:

    1.        Download ISO (used link above)
    2.        Unzip
    3.        Open command prompt as admin and navigate to the folder with vs2012.3.exe
    4.        Run and fail
    5.        Run .\VS2012.3\package\WinACK\Windows App Certification Kit x64-x86_en-us.msp
    6.        Run .\VS2012.3\package\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    7.        Run VS2012.3.exe again and … hopefully … succeed like I did after a great while.

    Montag, 15. Juli 2013 13:17
  • Installing the Windows App Cert Kit worked for me as well.  After installing it, the Web Installer version of the VS2012 Update 3 successfully installed (whereas previously it failed with the pipe error above).  This was on a Windows 7 machine.
    Montag, 15. Juli 2013 19:15
  • FYI, I had same issue and tried the solutions suggested in this thread.  Uninstall update, repair VS2012, install from ISO did *NOT* do the trick for me, but using the manual install of the two Windows App Certification Kit msp files did.

    Montag, 15. Juli 2013 21:20
  • Hi All,

    This problem still seems to be current. But after hours and hours and hours - I've got it working!

    Here is what I found:

    -- Installing this file: VS2012.3.iso - I get the The pipe is being closed error!

    -- Installing this file: mu_visual_studio_2012_update_3_x86_dvd_2364556.iso - It works!!

    Note: These were two separate downloads from the microsoft site, both containing 661 files and 2,185,338KB (2.08GB) - Only 1 works for me.

    I hope this helps.

    Cheers

    Donnerstag, 25. Juli 2013 01:01
  • Also wanted to add, nothing else worked for me I tried everything else on this forum and did tons of research - this is the only thing that worked for me

    Donnerstag, 25. Juli 2013 01:41

  • -- Installing this file: VS2012.3.iso - I get the The pipe is being closed error!

    -- Installing this file: mu_visual_studio_2012_update_3_x86_dvd_2364556.iso - It works!!

    Note: These were two separate downloads from the microsoft site, both containing 661 files and 2,185,338KB (2.08GB) - Only 1 works for me.


    John, where did you get that second version of the update? I have tried everything else described above and still getting the error so I'd like to try that version but I'm only seeing the VS2012.3.iso one.
    Samstag, 27. Juli 2013 08:14
  • Check Your Hash!

    I've been trying to get update 3 installed since it was announced.  I've tried all the suggestions in the other messages to no avail.  I did discover in the process that the previous updates did not install correctly either.

    Finally, I went back and tested the SHA1 on the .iso download link on http://www.microsoft.com/en-us/download/details.aspx?id=39305 and found it did not match.  I downloaded the .iso from MSDN subscriber downloads and verified the SHA1 was correct and it installed with no problem.

    Hope this saves some headaches and time (and maybe the downloads can be updated),

    John

    Dienstag, 30. Juli 2013 21:10
  • Same here - VS2012 Update 3 is doing my head in!

    VS2012.3.exe sporadically crashes which interrupts the update installation.

    The root cause appears to be a double free in VS2012.3.exe:

    0:003> !gflag
    Current NtGlobalFlag contents: 0x00000000
    0:003> !heap
    **************************************************************
    *                                                            *
    *                  HEAP ERROR DETECTED                       *
    *                                                            *
    **************************************************************

    Details:

    Heap address:  00670000
    Error address: 0071ce58
    Error type: HEAP_FAILURE_BLOCK_NOT_BUSY
    Details:    The caller performed an operation (such as a free
                or a size check) that is illegal on a free block.
    Follow-up:  Check the error's stack trace to find the culprit.


    Stack trace:
                    77dcdff5: ntdll!RtlFreeHeap+0x00000064
                    76df14dd: kernel32!HeapFree+0x00000014
                    01361b77: VS2012_3+0x00031b77
                    01351fc4: VS2012_3+0x00021fc4
                    013526d9: VS2012_3+0x000226d9
                    01352bba: VS2012_3+0x00022bba
                    01349cc6: VS2012_3+0x00019cc6
                    0134aa00: VS2012_3+0x0001aa00
                    0133d5ab: VS2012_3+0x0000d5ab
                    0134b43d: VS2012_3+0x0001b43d
                    76df33aa: kernel32!BaseThreadInitThunk+0x0000000e
                    77d89ef2: ntdll!__RtlUserThreadStart+0x00000070
                    77d89ec5: ntdll!_RtlUserThreadStart+0x0000001b

    If anyone at MSFT wants to look into this - I have 7 crash dumps so far and counting...


    • Bearbeitet Baz Freitag, 2. August 2013 13:29
    Freitag, 2. August 2013 13:19
  • It was the same for me; the Windows App Cert Kit did the trick.
    Samstag, 3. August 2013 01:27
  • It was the same for me; the Windows App Cert Kit did the trick.

    I'm also getting the pipe being closed, but for another reason.... 

    I couldn't paste the image but the error notice me about "Javasctipt Tooling"

    Perhaps some Javascript library missing??

    Someone get this already?

    Mittwoch, 7. August 2013 14:06
  • Montag, 23. September 2013 17:15
  • Ok, I finally got my install to work only had to open a command prompt as administrator and run tfs_server.exe from the command prompt.  My company has everything locked down as far as server security so I am not surprised that the issue ended up being security related.  I was logged in as an administrator from the beginning and still had problems till I did what I explained above.
    Mittwoch, 2. März 2016 19:13