none
Visual Studio Enterprise 2015 "Incorrect Function" Error after installation

    Question

  • Have tried a couple of times but after installation VS2015 fails to load

    I have the log file as well but not sure where I can upload it for sharing. I have pasted a section that contains the error here http://pastebin.com/zbu35cfJ 

    I can upload the full log if someone can say where.

    This is VS2015 Ent on Windows 7

    This is a corporate laptop that has some symantec software that replaces the normal UAC popup but I can run things in admin mode.

    Am completely stuck on how to go about solving this.

    Tuesday, February 21, 2017 2:58 PM

Answers

  • Hi Paul,

    Welcome to MSDN forum.

    According to your log, please restart your computer before you repair or reinstall visual studio. After this, open visual studio to check if any error will occur.

    >>Applying execute package: VSSetupUtility_Complete_vs_enterprise, action: Install, path: C:\ProgramData\Package Cache\A9E5ED87-B06B-3F4F-AF25-B27A733D7CC1\packages\vs_enterprise\VSSetupUtility.exe, ……. C:\Users\2023310\AppData\Local\Temp\dd_vs_enterprise_20170221132553_156_VSSetupUtility_Complete_vs_enterprise.log /result 3010 /RebootNeeded 1'

    [0468:3E8C][2017-02-21T14:00:11]e000: Error 0x80070001: Process returned error: 0x1

    Meanwhile, please have a try with delete or rename the following folders:

    • C:\Users\<your users name>\AppData\Local\Microsoft\VisualStudio\14.0
    • C:\Users\<your users name>\AppData\Roaming\Microsoft\VisualStudio\14.0

    If this issue persists, I need your help to collect the completely log. Please use http://aka.ms/vscollect to gather the installation logs. After using it, you will find vslogs.zip under %temp% folder. Please upload the file to https://onedrive.live.com/ and share the link here.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Paul Busby Wednesday, February 22, 2017 10:28 AM
    Wednesday, February 22, 2017 7:31 AM

All replies

  • Hi Paul,

    Welcome to MSDN forum.

    According to your log, please restart your computer before you repair or reinstall visual studio. After this, open visual studio to check if any error will occur.

    >>Applying execute package: VSSetupUtility_Complete_vs_enterprise, action: Install, path: C:\ProgramData\Package Cache\A9E5ED87-B06B-3F4F-AF25-B27A733D7CC1\packages\vs_enterprise\VSSetupUtility.exe, ……. C:\Users\2023310\AppData\Local\Temp\dd_vs_enterprise_20170221132553_156_VSSetupUtility_Complete_vs_enterprise.log /result 3010 /RebootNeeded 1'

    [0468:3E8C][2017-02-21T14:00:11]e000: Error 0x80070001: Process returned error: 0x1

    Meanwhile, please have a try with delete or rename the following folders:

    • C:\Users\<your users name>\AppData\Local\Microsoft\VisualStudio\14.0
    • C:\Users\<your users name>\AppData\Roaming\Microsoft\VisualStudio\14.0

    If this issue persists, I need your help to collect the completely log. Please use http://aka.ms/vscollect to gather the installation logs. After using it, you will find vslogs.zip under %temp% folder. Please upload the file to https://onedrive.live.com/ and share the link here.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Paul Busby Wednesday, February 22, 2017 10:28 AM
    Wednesday, February 22, 2017 7:31 AM
  • Thanks you. This solved my issue. Had restarted a number of times but the trick was to rename those folders you indicated. Ran the installed in repair and all is good.
    Wednesday, February 22, 2017 10:28 AM