Windows 10 SDK will not be installed in Visual Studio

I have been trying to get Visual Studio and the Windows 10 SDK to work for more than a week. At first, I was unable to install Visual Studio. This problem was solved by removing EVERYTHING vaguely related to VS2015, thanks to the manual passage of everything, as well as Visual Studio "TotalUninstaller".

Scrolling: now that I have managed to install and run VS2015, I can’t install the SDK. I selected it with the installation process, tried to change VS after, tried to install it using the Standalone installer, but none of them work. Each time the installer does not notice anything, all the tools appear in the Start menu, a new folder “Program Files (x86) /WindowsKits/10.0” appears with all the correct files, but VS cannot open any UWP Projects, cannot create new ones, and The SDK does not appear in the Extensions list.

When I deleted everything, there was only one thing left that I could not get rid of: "Windows 10 for mobile image - 10.0.10240.0." It just opens, works for a second and closes, achieving nothing in this process. Since I could not get rid of this, I manually deleted any associated Windows Kits folder in Program Files, Program Files (x86), ProgramData and everything in the AppData folder. But this piece of fluffy garbage did not leave a list of installed programs. Could this be related to the fact that you cannot correctly install the Windows 10 SDK?

I looked through the installation 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 checkmark, or when I use the offline installer. I looked at C:\ProgramData\Package Cache and there is no folder {7a68448b-9cf2-4049-bd73-5875f1aa7ba2} , and none of the other folders contains "vsupdate_KB3022398.exe". This seems to be the root of the problem.

EDIT: I created a folder that was missing and added “vsupdate_KB3022398.exe” (found on the Internet, hosted on a Microsoft server), and there were no more errors. However, the problem is still not fixed. SDK just refuses to appear. I think I will need to do a clean install.

+6
source share
4 answers

I had a problem with Windows 10 SDK 14393, which could not be installed on Windows 7. This problem occurred during installation as part of Visual Studio 2015, as well as when running the standalone installer for Windows 10 SDK 14393. According to the logs, the SDK could not be installed Windows Desktop Extension.

In the process, I installed the Windows 10 SDK 10586 (successfully installed) Then I installed the Windows 10 SDK 14393 (successfully installed) Both versions of the Windows 10 SDK appear as options in the Target Platform Version for Visual Studio 2015 for me.

Apparently, the Windows 10 SDK 14393 installer is missing something that is required to run successfully in Windows 7. (Something that should be present in the previous version)

+2
source

Sorry for the difficulty. There are two known issues that cause a "Fatal Error" in installing the Windows SDK.
See the Windows SDK Problem Forum.

You probably had a preliminary release of the SDK, and one of the installed contracts causes MDMerge to crash during installation. When uninstalling the preliminary version of the SDK, you should avoid this problem.

Thanks Kevin

0
source

I had a problem with MDMerge, after uninstalling all the previous Windows 10 SDK toolkits, it still failed to install. Fixed by moving the contents: "C: \ Program Files (x86) \ Windows Kits \ 10", launched the installer again and installed it in order.

0
source

This is what I did, and it worked for me. Delete everything in the linker (PROJECT → LINKER → Input → Additional Dependencies, as seen in this screenshot

enter image description here

0
source

All Articles