none
VS2017 installation - Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install RRS feed

  • Question

  • When I install VS 2017 Enterprise (Workload UWP development) and it comes to Windows 10 SDK installation it fails everytime with "Recursion too deep; the stack overflowed." Installing the newest standalone package of the Win 10 SDK succeeds.

    This is the log of the installation:

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

    The product failed to install the listed workloads and components due to one or more package failures.

    Incomplete workloads
        Desktop development with C++ (Microsoft.VisualStudio.Workload.NativeDesktop,version=15.0.26228.0)

    Incomplete components
        Windows 10 SDK (10.0.14393.0) (Microsoft.VisualStudio.Component.Windows10SDK.14393,version=15.0.26208.0)

    You can search for solutions using the information below, modify your selections for the above workloads and components and retry the installation, or remove the product from your machine.

    Following is a collection of individual package failures that led to the incomplete workloads and components above. To search for existing reports of these specific problems, please copy and paste the URL from each package failure into a web browser. If the issue has already been reported, you can find solutions or workarounds there. If the issue has not been reported, you can create a new issue where other people will be able to find solutions or workarounds.

    Package 'Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install.
        Search URL: https://aka.ms/VSSetupErrorReports?q=PackageId=Win10SDK_10.0.14393.795;PackageAction=Install;ReturnCode=1001
        Impacted workloads
            Desktop development with C++ (Microsoft.VisualStudio.Workload.NativeDesktop,version=15.0.26228.0)
        Impacted components
            Windows 10 SDK (10.0.14393.0) (Microsoft.VisualStudio.Component.Windows10SDK.14393,version=15.0.26208.0)
        Log
            C:\Users\klh\AppData\Local\Temp\dd_setup_20170313080701_004_Win10SDK_10.0.14393.795.log
        Details
            Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NoLogo -NoProfile -ExecutionPolicy Unrestricted -InputFormat None -Command "& """C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.14393.795,version=10.0.14393.79501\WinSdkInstall.ps1""" -SetupExe sdksetup.exe -SetupLogFolder standalonesdk -PackageId Win10SDK_10.0.14393.795 -LogFile """C:\Users\klh\AppData\Local\Temp\dd_setup_20170313080701_004_Win10SDK_10.0.14393.795.log""" -SetupParameters """/features OptionId.AvrfExternal OptionId.WindowsSoftwareDevelopmentKit OptionId.WindowsSoftwareLogoToolkit OptionId.NetFxSoftwareDevelopmentKit /quiet /norestart"""; exit $LastExitCode"
            Return code: 1001
            Return code details: Recursion too deep; the stack overflowed.

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

    What can be done?

    Monday, March 13, 2017 8:11 AM

Answers

  • Hi,

    The Microsoft senior engineer did not contact me for more than half a year!

    In the meantime I was able to solve the problem: vs_installer.exe was running in compatibility mode for Windows Vista. After clearing this setting the installation succeeded.

    • Marked as answer by klh69 Monday, October 2, 2017 1:32 PM
    Monday, October 2, 2017 1:32 PM

All replies

  • Hi klh69,

    Welcome to MSDN forum.

    Please check if you are on a domain, and your domain account doesn’t have local admin rights. If it is, giving your domain account the local admin rights. Besides, run the installer of visual studio 2017 as an administrator.

    You have installed the standalone package of win 10 SDK, when you run visual studio 2017, it will be detected by vs2017. If there is no error message during the use of visual studio 2017, installing the standalone win 10 SDK is the current workaround.

    To get the cause of the issue you met, I need your help to collect the complete VS installation 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.

    Tuesday, March 14, 2017 6:06 AM
  • Hi Joyce,

    Thanks for your reply.

    I'm on a domain and my account has local admin rights. I've run the installer with my admin account. The vs2017 installer does not detect the win 10 SDK. It tries to install it again every time I run the vs2017 installer.

    The installation logs can be found here: https://1drv.ms/u/s!Ausdpezx9JUXbC4y5msGwMH5m18

    Cheers,

    Klaus

    Tuesday, March 14, 2017 7:27 AM
  • Hi klh69,

    Welcome to MSDN forum.

    >>Burn v3.7.3503.1, Windows v6.0 (Build 6000: Service Pack 0), path: C:\Users\klh\AppData\Local\Temp\Win10SDK_10.0.14393.795\sdksetup.exe,

    Please have a look at the system requirement for visual studio 2017: https://www.visualstudio.com/en-us/productinfo/vs2017-system-requirements-vs.

    Note: Windows 7 SP1 (with latest Windows Updates): Home Premium, Professional, Enterprise, Ultimate

    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.

    Tuesday, March 14, 2017 9:39 AM
  • Hi Joyce,

    But that's what I have.

    Please see .\Temp\StandaloneSDK\Windows_Software_Development_Kit___Windows_10.0.14393.795_20170313105925.log in vslogs.zip:

    >> Burn v3.7.3503.1, Windows v6.1 (Build 7601: Service Pack 1), path: C:\Users\klh\AppData\Local\Temp\Win10SDK_10.0.14393.795\sdksetup.exe

    Cheers,

    Klaus

    Tuesday, March 14, 2017 10:01 AM
  • .\Temp\CollectInfo.txt in vslogs.zip:

    [OSInfo]
    Version=6.1.7601
    Major=0x00000006  ;6
    Minor=0x00000001  ;1
    Build=0x00001db1  ;7601
    PlatformId=0x00000002  ;2
    CSDVer=Service Pack 1
    SPMajor=0x0001  ;1
    SPMinor=0x0000  ;0
    SuiteMask=0x0100  ;256
    ProductType=0x01  ;1
    ProductInfo=4
    ProductInfoName=Enterprise

    Tuesday, March 14, 2017 10:13 AM
  • Hi klh69,

    Thank you for your update.

    Please update your visual studio 2017 to the latest version or reinstall the latest version, refer to here: https://www.visualstudio.com/en-au/news/releasenotes/vs2017-relnotes#mar14

    After you installed visual studio 2017, if the issue('Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install) persists, downloading the standalone win10SDK. If vs2017 still doesn’t detect win10SDK, repairing visual studio to check if it could be detected. (the other who met the similar issue with you solved it by the solutions)

    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.


    Wednesday, March 15, 2017 6:03 AM
  • Hi Joyce,

    I completely uninstalled vs2017 and win10SDK. Then installed the latest version of vs2017. Same fault. Then installed standalone win10SDK. Repairing vs2017 didn't help. "Modify" vs2017 without changing any workloads shows the same fault.

    New vslogs: https://1drv.ms/u/s!Ausdpezx9JUXbltAO4oOFPtA3lI

    Cheers,

    Klaus

    Wednesday, March 15, 2017 12:12 PM
  • Hi

    I'm ready to explode :-0

    Three different kind of computers, three different setups, two different version of Visual Studio (two Enterprise and one Community Edition), all three computers running Windows 10 Enterprise - and I'm still not able to install Visual Studio 2017 on any computer.

    When I try to download and install the "Standalone win10 SDK" the installation stops.

    I have tried to uninstall everything that comes with Visual Studio 2017, delete everything in %temp%, restart the computer every time the installer says so -> still the same error. ('Win10SDK_10.0.14393.795,version=10.0.14393.79501' failed to install.)

    And I have no idea about how to solve this.

    Please - help me :-)

    Wednesday, March 15, 2017 1:30 PM
  • Hi,

    Thank you for your update.

    In some cases when installing on a version of Windows earlier than Windows 10, the install failure may be caused by a missing Universal C Runtime. You may install this by using KB2999226 for the Windows 10 1507 runtime, or KB3118401 for the Windows 10 1511 runtime.

    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.

    Thursday, March 16, 2017 9:22 AM
  • Hi,

    I installed both but it didn't help. Re-installed vs2017 but got the same fault again. The Windows Version is still incorrectly determined by the win10SDK installation if it's running under the vsInstaller.

    Klaus

    Thursday, March 16, 2017 1:39 PM
  • Hi Klh69,

    Thank you for your update.

    Since we tried many ways but still no help, I have invited Microsoft senior engineer to help you troubleshoot about this case.

    Please wait patiently.

    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.

    Friday, March 17, 2017 5:25 AM
  • Hi klh69,

    Since you mentioned that your OS is Win7 while the log file show v6.0, can you check "Property\Compatibility" of the setup file to see if it was set to run in compatibility mode?

    Friday, March 17, 2017 8:21 AM
  • Hi,

    It is not set to run in compatibility mode.

    Friday, March 17, 2017 8:25 AM
  • Hi,

    The Microsoft senior engineer did not contact me for more than half a year!

    In the meantime I was able to solve the problem: vs_installer.exe was running in compatibility mode for Windows Vista. After clearing this setting the installation succeeded.

    • Marked as answer by klh69 Monday, October 2, 2017 1:32 PM
    Monday, October 2, 2017 1:32 PM