For some reason the setup is blocked when trying to install VS2013 SDK on a Windows 10 machine.
Any ideas?
Here is a relevant part of the log file:
[5EB4:710C][2015-03-27T11:22:50]i052: Condition 'CompatibilityMode = 0' evaluates to true.
[5EB4:710C][2015-03-27T11:22:50]i052: Condition 'NOT((VersionNT > v6.1) OR (VersionNT = v6.1 AND ServicePackLevel >= 1))' evaluates to false.
[5EB4:710C][2015-03-27T11:22:50]i052: Condition '( NOT ((ProCheck_ProfessionalCore_DetectKey = 1) OR (ProCheck_VSCore_DetectKey = 1)) ) AND (CurrentOperation = "Install") ' evaluates to false.
[5EB4:710C][2015-03-27T11:22:50]i000: MUX: Stop Block: CompatibilityMode : Windows Program Compatibility mode is on. Turn it off and then try Setup again.
Found a way to install it. First, you should unpack the installer using command line:
vssdk_full.exe /layout
Choose a folder where you want the files to be extracted. Then press the “Download” button. Go to that folder and start the installer. It will bypass the check and install the SDK.
It does not look like it is supported on Windows 10 (yet).
Microsoft Visual Studio 2013 SDK
Supported Operating System
Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
I've got the same error.
Have you renamed the installer? Because I did, so I won't work until you rename it again to vssdk_full.exe.
Visual Studio 2013 require .Net 3.5 so, you need to install .Net framework 3.5 first, then block will be remove
One common cause of this problem is that Windows' built-in compatibility modes kick in (or don't) because of what seem like minor problems such as the setup executable not having the file name Windows is looking for.
For example, there are scenarios where a user has downloaded the setup package twice which leads to two different executables: vssdk_full.exe and vssdk_full (1).exe. If you launch the latter, you may run into the type of problem described in this thread. The easiest fix is to make it so Windows recognizes the filename but getting rid of the (1) suffix.
Related
Need to install Visual Studio for school, but run into this and one other error.
Visual Studio fails to install "Microsoft.Net.CoreUWP,version=1.1.32" and "Win10SDK_10.0.16299,version=10.0.16299.0".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log for "Microsoft.Net.CoreUWP,version=1.1.32" :
Package 'Microsoft.Net.CoreUWP,version=1.1.32' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.Net.CoreUWP;PackageAction=Install;ReturnCode=1316
Details
MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.CoreUWP,version=1.1.32\netfx_NETCoreUWP.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7"
Return code: 1603
Return code details: Fatal error during installation.
Message Id: 1316
Message Details: The specified account already exists.
Log
C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_162_Microsoft.Net.CoreUWP.log
Impacted workloads
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.27128.1)
Impacted components
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26906.1)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.27005.2)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.27005.2)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log for "Win10SDK_10.0.16299,version=10.0.16299.0" :
Package 'Win10SDK_10.0.16299,version=10.0.16299.0' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Win10SDK_10.0.16299;PackageAction=Install;ReturnCode=1316
Details
Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NonInteractive -NoLogo -NoProfile -ExecutionPolicy Bypass -InputFormat None "$ErrorActionPreference="""Stop"""; $VerbosePreference="""Continue"""; $CeipSetting="""on"""; $ScriptPath="""C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.16299,version=10.0.16299.0\WinSdkInstall.ps1"""; $SetupExe="""winsdksetup.exe"""; $SetupLogFolder="""windowssdk"""; $PackageId="""Win10SDK_10.0.16299"""; $LogFile="""C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_181_Win10SDK_10.0.16299.log"""; $SetupParameters="""/features OptionId.AvrfExternal OptionId.UWPManaged OptionId.WindowsSoftwareLogoToolkit OptionId.SigningTools OptionId.UWPLocalized OptionId.UWPCPP OptionId.DesktopCPPx64 OptionId.DesktopCPPx86 OptionID.DesktopCPPARM OptionID.DesktopCPPARM64 OptionId.MSIInstallTools /quiet /norestart"""; (gc $ScriptPath | out-string) | Invoke-Expression; if (!$?) { exit 1603 } elseif ($LastExitCode) { exit $LastExitCode }"
Return code: 1316
Return code details: The specified account already exists.
Log
C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_181_Win10SDK_10.0.16299.log
Impacted workloads
Desktop development with C++ (Microsoft.VisualStudio.Workload.NativeDesktop,version=15.0.27102.0)
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.27128.1)
Impacted components
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26906.1)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.27005.2)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.27005.2)
Visual C++ tools for CMake (Microsoft.VisualStudio.Component.VC.CMake.Project,version=15.0.27019.1)
Windows 10 SDK (10.0.16299.0) for Desktop C++ [x86 and x64] (Microsoft.VisualStudio.Component.Windows10SDK.16299.Desktop,version=15.0.27128.1)
Windows 10 SDK (10.0.16299.0) for UWP: C#, VB, JS (Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP,version=15.0.27128.1)
Windows 10 SDK (10.0.16299.0) for UWP: C++ (Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP.Native,version=15.0.27128.1)
Update:
In this page there is some info about Error 1316. the specified account already exists:
Are you installing with full administrative rights? To make certain
that you are, right-click the installer and select Run as
administrator.
The next most likely explanation is some bad registry entries:
Microsoft offers a tool to solve these sorts of install and uninstall
problems; please see Fix problems that block programs from being
installed or removed.
When the fix-it tool asks what you're trying to
install, select "not listed" unless you're installing the exact same
version that was previously installed. For example, both 7.5.0 and
7.5.1 would show up as 7.5 in the list in the fix-it tool, but they are different installers so you would select "not listed" if you're
installing 7.5.1 over 7.5.0.
Older Section:
If above solution dose not work for you, read this part:
Based on your provided log, It seems in this case » the Visual Studio Setup program need to uninstall netfx_NETCoreUWP.msi and Win10SDK from your computer but it can not do it, so you can help it with uninstalling them manually (with your risk):
Close Visual Studio Setup program
Go to C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.CoreUWP,version=1.1.32
Right click on netfx_NETCoreUWP.msi and select Uninstall.
For the second error I think you should open Programs and Features from Control Panel and uninstall Microsoft Software Development Kit - Windows 10.0.16299 from there.
Run Visual Studio Setup program again and go ahead..
I use the permission of Administrator to install vs_enterprise.exe.
But the install package don't work at all.
OS: win10 professional
The install log in appdata/local/temp/ is as follow:
dd_bootstrapper_20170313103210:
Beginning of the log. Start Time: 13/03/2017 10:32:10 VisualStudio Bootstrapper:13/03/2017 10:32:10: Current Optin root path does not
exists VisualStudio Bootstrapper:13/03/2017 10:32:11: Commandline
arguments =
dd_vs_enterprise_decompression_log.txt:
[3/13/2017, 10:32:4] === Logging started: 2017/03/13 10:32:04 === [3/13/2017, 10:32:4] Executable: D:\vs2017\vs_enterprise.exe
v15.0.26206.0 [3/13/2017, 10:32:4] --- logging level: standard ---
[3/13/2017, 10:32:4] Directory
'C:\Users\gary\AppData\Local\Temp\b012f31d56525c685e\' has been
selected for file extraction [3/13/2017, 10:32:4] Extracting files
to: C:\Users\gary\AppData\Local\Temp\b012f31d56525c685e\ [3/13/2017,
10:32:5] Extraction took 484 milliseconds [3/13/2017, 10:32:5]
Executing extracted package:
'vs_bootstrapper_d15\vs_setup_bootstrapper.exe ' with commandline ' '
[3/13/2017, 10:32:11] The entire Box execution exiting with result
code: 0x0 [3/13/2017, 10:32:11] Launched extracted application
exiting with result code: 0xc000000d [3/13/2017, 10:32:11] ===
Logging stopped: 2017/03/13 10:32:11 ===
Thank You~
I was having this exact problem, thought it was a services thing. The installer would start if I ran it as soon as Windows booted; if I waited, it didn't.
Turns out it was RivaTunerStatistics server that was running for my gaming overlays. Closed it, and voila, working again. Tried multiple times to confirm.
I had a similar issue, my Visual Studio Professional 2017 installer was closing before the installation starts. I solve the issue by following these steps:
1 - Open the prompt(CMD) with administration rights
2 - Check if you have the "InstallCleanup.exe" file inside the folder "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\". If the file is there then go to step 7
3 - Manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder
4 - Relaunch the newly downloaded visual studio installer
5 - Allow the first step to install the installer
6 - Once the installer comes up and you can see workload choices (.net desktop and the like), close it
7 - inside CMD navigate to the folder "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\"
3 - run this command: "InstallCleanup.exe -full"
4 - that's it. Just run the installer again.
It worked for me.
I had the same Problem on two different Pc's (both win10) and the only thing that worked for me, was reinstalling Windows's and rerun the visual studio installer. I know, that's not a good, fast or easy solution, but it works.
I had a similar issue with the VS 2017 installer (similar error message), and I was finally able to resolve my problem after 4 days of troubleshooting with Microsoft Support. I'm developing on a Dell laptop and the support technician believes one of the Dell services was causing issues with the winmgmt service.
Below is a command that failed to run during troubleshooting. After making sure we had an OS restore point saved, we issued the winmgmt /resetRepository command. After that, the VS 2017 Pro installer was able to execute without error.
Here are the exact steps taken by Microsoft Support:
Step 1: Create a Windows system restore point.
Step 2: From the command prompt with administrative rights or elevated privileges, execute the following command: net stop winmgmt
Step 3: Open a Windows Explorer and locate the path to C:\windows\system32\WBEM\ folder and rename the Repository folder to something else like RepositoryOLD (right click and choose 'Rename Folder').
Step 4: restart the computer
Step 5: From the command prompt with administrative rights or elevated privileges, execute the following command: net stop winmgmt
C:\>net stop winmgmt
The Windows Management Instrumentation service is stopping.
The Windows Management Instrumentation service could not be stopped.
Step 6: From the command prompt with administrative rights or elevated privileges, execute the following steps and execute the following this: winmgmt /resetRepository
C:\>winmgmt /resetRepository
WMI repository has been reset
Step 7: restart the computer.
Hope this helps someone else.
I had the same problem but it was solved by the answer #Ben Logan gave (Closing RivaTunerStatistics).
After trying all the suggested answers here (using VS 2017), I followed the instructions on the official Microsoft docs which worked for me. In summary:
Close the Visual Studio Installer.
Delete the Visual Studio Installer directory. Typically, the directory is C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Run the Visual Studio Installer bootstrapper. You may find the bootstrapper in your Downloads folder with a file name that follows a vs_[Visual Studio edition]__*.exe pattern. If you don't find that application, you can download the bootstrapper by going to the Visual Studio downloads page and clicking Download for your edition of Visual Studio. Run the executable to reset your installation metadata.
Try to install or update Visual Studio again. If the Installer continues to fail, go to the next step.
For anyone still having this problem:
One of my co-workers encountered the same problem. We spent 4 hours searching for solutions, uninstalling VS and other software that we thought might be the culprit.
In the end, THIS LINK helped us figure it out. The problem is somehow explained there and is linked to NODE_OPTIONS variable. If you have that variable set, remove it then restart your computer. This solved his problem.
Configuration:
Widows 10, Visual Studio 2017 Enterprise.
I hope this helps you
Copy vs_enterprise.exe to a USB and run. It will work.
try to run this file using console
example: c:/vs_community__556869458.1519050247.exe
I've been trying to get Visual Studio and the Windows 10 SDK to work for over a week now. First I couldn't install Visual Studio. That problem was resolved by uninstalling EVERYTHING vaguely related to VS2015, thanks to manually going through everything, but also the Visual Studio "TotalUninstaller".
Plot twist: Now that I've managed to get VS2015 installed and running, I can't get the SDK to install. I've selected it with the installation process, tried to modify VS after, tried to install it with the Standalone installer, but none of it works. Every time, the installer doesn't notice anything wrong, all the tools appear in the start menu, a new "Program Files (x86)/WindowsKits/10.0" folder appears, with all the correct files, but VS can't open any UWP projects, can't create new any, and the SDK doesn't appear in the Extensions list.
When I uninstalled everything, there was only one thing I couldn't get rid of: "Windows 10 for Mobile Image - 10.0.10240.0". It just opens, runs for a second, and closes, achieving nothing in the process. As I couldn't get rid of this, I manually deleted any "Windows Kits" related folder in Program Files, Program Files (x86), ProgramData, and anything in the AppData folder. But this piece of fluffy garbage didn't leave my installed programs list. Could this have something to do with not being able to install the Windows 10 SDK correctly?
I looked in the install logs, and this is the only error I saw:
[371C:398C][2016-08-08T21:13:35]i301: Applying execute package: {7a68448b-9cf2-4049-bd73-5875f1aa7ba2}, action: Install, path: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe, arguments: '"C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe" -quiet -burn.related.patch -burn.ignoredependencies={248fcd1e-5ee1-421d-893f-ec0a94dd7b01} -burn.ancestors={248fcd1e-5ee1-421d-893f-ec0a94dd7b01}'
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to create embedded process atpath: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to run embedded bundle.
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to run bundle as embedded from path: C:\ProgramData\Package Cache\{7a68448b-9cf2-4049-bd73-5875f1aa7ba2}\vsupdate_KB3022398.exe
[371C:398C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to execute EXE package.
[287C:137C][2016-08-08T21:13:35]e000: Error 0x80070003: Failed to configure per-machine EXE package.
It appears in every log when I try to install vs2015 with the right option ticked, or when I use the standalone installer. I've looked in C:\ProgramData\Package Cache and there is no {7a68448b-9cf2-4049-bd73-5875f1aa7ba2} folder, and none of the other folders contain "vsupdate_KB3022398.exe". It looks like this is the root of the problem.
EDIT: I've created the folder that was missing and added "vsupdate_KB3022398.exe" to it (found it online, hosted on a Microsoft server), and there are no more errors left. However, the problem still isn't fixed. The SDK simply refuses to show up. I think I'm going to have to do a clean install.
I had the issue of Windows 10 SDK 14393 failing to install on Windows 7 OS. This problem occurred when installing as part of Visual Studio 2015 and also running the Standalone Installer for the Windows 10 SDK 14393. According to the logs, the Windows Desktop Extension SDK failed to install.
As a work-around I installed Windows 10 SDK 10586 (Installed successfully)
Then I installed Windows 10 SDK 14393 (Installed successfully)
Both versions of the Windows 10 SDK appear as choices under Target Platform Version in Visual Studio 2015 for me.
Apparently the Windows 10 SDK 14393 installer is missing something which it requires to run successfully on Windows 7. (Something that must be present in the previous version)
Sorry for the difficulty. There are 2 known issues that are causing 'Fatal Error' in the Windows SDK install.
See the Windows SDK Tools Issues Forum.
You probably have (had) a pre-release of the SDK and one of the contracts installed is causing MDMerge to fail during setup. Uninstalling the prerelease version of the SDK should avoid this issue.
Thanks,
kevin
I had the MDMerge problem, after uninstalling all previous Windows 10 SDK toolkits, still couldn't install. Fixed it by moving the contents of: "C:\Program Files (x86)\Windows Kits\10", ran the installer again and it installed fine.
This is what I did and it kind of worked for me. Remove everything in the linker ( PROJECT -> LINKER -> Input -> Additional Dependencies, as can be seen in this screenshot
I am trying to install the Visual Studio 2015 Update 3, but I am receiving an error each time. I have tried both the web installer and the ISO, and I have also tried going into Control Panel/Programs and modifying the 2015 install. All of these result in the same error: "Setup Engine - The parameter is incorrect". I've read about some of the other issues with the installer, but I'm hoping somebody else might have seen this one or something similar. The logs always have the following error in them:
[1B10:1DA0][2016-07-18T11:39:28]e000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4}
[1B10:1DA0][2016-07-18T11:39:28]e151: Detect failed for package: Win10_Universal_CRT_SDK_Extension_SDK, error: 0x80070057
I have even tried to download the full installer for VS2015, but all installers seem to run through the same error. Any ideas on how I might repair this particular component so the installs will succeed?
Additional information, this is happening on a VM of Windows 10 running in Parallels 11.
Screen shot of installer failing
I found a similar issue here： https://connect.microsoft.com/VisualStudio/feedback/details/974081/visual-studio-update-3-installation-keeps-failing-error-message-setup-engine-the-parameter-is-incorrect
The reply from Heath[MSFT]:
The logs confirm that some of your Windows Installer product
registration is corrupt. For the first issue, open a command prompt
(preferably elevated to avoid multiple UAC prompts later) and run the
following:
start /wait msiexec /fomus {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} REINSTALL=ALL
That should get
you past the first problem. If it does not, manually remove the
product like so and re-install it from the package cache:
start /wait msiexec /x {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} IGNOREDEPENDENCIES=ALL
start /wait msiexec /i "C:\ProgramData\Package Cache\{A79F6653-6AF1-4AF2-BC15-F5D6C05E1E6A}v2.0.40326.0\packages\sptoolsDependencies\enu\WorkflowManagerTools_x64.msi" ADDLOCAL=ALL NOVSUI=1
(change the above file
WorkflowManagerTools_x64.msi according to your log file record) After
this, installing VS Update 3 should work.
I had a very similar problem which at its root exhibited the same issue identified above in the Visual Studio 2015 Update 3 setup error (I couldn't install SSMS 17.1 which uses the Visual Studio 2015 Isolated Shell). I tried the solution above which unfortunately did not work for me. I did some more digging through the vs_isoshell.exe log file and found lines similar to those below.
[6BE0:36E0][2017-07-13T13:05:36]i000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {9A7E3828-17FB-3E0C-9B28-48493E01937A}
The ProductCode refers to the "Microsoft Visual C++ 15 x86 Debug Runtime - 14.10.24269".
A perusal of my installed programs showed I did not have this installed, and I was unable to install it again due to a later version being present (it turns out it was upgraded, or removed, when I installed Visual Studio 2017).
I did some more searching and came across this page which had steps I adapted to my situation. I performed the same registry profiling of the installer with Process Monitor and the same key was missing. I added a key called DisplayVersion (string - REG_SZ) to the path below with a value of 14.10.24629 and that worked.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\8283E7A9BF71C0E3B9828494E31039A7\InstallProperties]
Adding the key/value pair allowed the installation of the VS 2015 Update 3 Isolated Shell to finish successfully which in turn allowed the SSMS 17.1 installation to complete successfully.
For various reasons, I have to install VS.Net 2003 on a 2012 R2 Server.
I was able to install the VS 2003 Pre-reqs when I tried to install the VS.net 2003 server itself, I am getting the following error:
Error 1309: Error reading from File D:............\adodb.dll.
Verify that the file exists and you have access to it.
I am able to see the file. I run the setup exe as administrator.Still getting this error.
If you have multiple CD-DVD ROM drives, you should turn off the extra drives and try again.
If you don't have a multiple CD-ROM system, try to copy the CD-DVD's contents to the Hard Disk Drive and run the installation from there.
you can try to download the file from internet and repleace the one from the folder, but first back up the old one
Download the file adodb.dll to your desktop.
Move the dll file to the program directory missing the file.
If step 2 doesn't work. Move adodb.dll to the system directory.
Windows XP,Vista, and Windows 7 - C:\Windows\System32
on 2012 R2 Server should be the same directory file
It seems under Win2K12 R2, the Installer of MSVS.Net 2003 does not pick up the short forms of the paths to the installation files... I even suspect that server doesn't support 8.3 forms of the paths.
For the case the 8.3 support is there, try to run the installer in Compatibility Mode (right-click on the setup executable and choose Properties, then tab "Compatibility", then either run the Compatibility Troubleshooter oder select the Checkbox "Run this program in compatibility mode for:" and choose from the dropdown Windows 7 oder Windows XP (SP 3)).