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.
- Remove From My Forums
-
Question
-
I am not able to install Windows 10 SDK (14393) . I have tried several times
the last three days from different desktops on different networks, so i am pretty sure that the problem is not related to poor network connections. I have tried installation through visual studion 2015 and visual studio 2017. And also by sdksetup, where i
tried both installation and only downloading (to different locations).The log indicate a problem with a specific file/cab:
[24F8:0EF4][2016-12-21T11:16:51]i000: payA059C4F9394E47AFD81C08AB201AB7C4
[24F8:0EF4][2016-12-21T11:16:51]i000: payA059C4F9394E47AFD81C08AB201AB7C4 to http://download.microsoft.com/download/6/3/B/63BADCE0-F2E6-44BD-B2F9-60F5F073038E/standalonesdk/Installers/77db8ab55a0b236db83c55ced6e8a9a3.cab
[24F8:0EF4][2016-12-21T11:16:51]i338: Acquiring package: package_WindowsSDKDesktopHeadersLibsMetadata_x86_en_us, payload: payA059C4F9394E47AFD81C08AB201AB7C4, download from: http://download.microsoft.com/download/6/3/B/63BADCE0-F2E6-44BD-B2F9-60F5F073038E/standalonesdk/Installers/77db8ab55a0b236db83c55ced6e8a9a3.cab
[2C08:0B7C][2016-12-21T11:17:00]e000: Error 0x80091007: Hash mismatch for path: C:\Users\npg\AppData\Local\Temp\{f23f94c5-8bba-4202-85ad-c83d4402cdc1}\payA059C4F9394E47AFD81C08AB201AB7C4, expected: 775D63042EFB64FD0997032A4FF347A856EB5FD1, actual: 9914D211EABA9AFFD1E8B320EB8C4D0A58826F79
[2C08:0B7C][2016-12-21T11:17:00]e000: Error 0x80091007: Failed to verify payload hash: C:\Users\npg\Downloads\Windows Kits\10\StandaloneSDK\Installers\77db8ab55a0b236db83c55ced6e8a9a3.cab
[2C08:0B7C][2016-12-21T11:17:00]e000: Error 0x80091007: Failed to layout payload from cached payload: C:\Users\npg\Downloads\Windows Kits\10\StandaloneSDK\Installers\77db8ab55a0b236db83c55ced6e8a9a3.cab
[2C08:0B7C][2016-12-21T11:17:00]e000: Error 0x80091007: Failed to layout payload from: C:\Users\npg\AppData\Local\Temp\{f23f94c5-8bba-4202-85ad-c83d4402cdc1}\payA059C4F9394E47AFD81C08AB201AB7C4 to C:\Users\npg\Downloads\Windows Kits\10\StandaloneSDK\
[24F8:0EF4][2016-12-21T11:17:00]i000: ERROR: Failed to verify the integrity of payload [payA059C4F9394E47AFD81C08AB201AB7C4] for Package package_WindowsSDKDesktopHeadersLibsMetadata_x86_en_us
[24F8:0EF4][2016-12-21T11:17:00]i000: RetryManager: No more retry for cache verification error on payload [payA059C4F9394E47AFD81C08AB201AB7C4]
[24F8:0EF4][2016-12-21T11:17:00]e317: Failed to layout payload: payA059C4F9394E47AFD81C08AB201AB7C4 to layout directory: C:\Users\npg\Downloads\Windows Kits\10\StandaloneSDK\, error: 0x80091007.I hope sombody can helping me find a solution
Regards npgm
-
Moved by
Thursday, December 22, 2016 1:48 AM
Installation related
-
Moved by
Answers
-
Hi Lana,
Thanks — however this did not help in my case, same SDK download/integrity failure errors were observed after I had uninstalled all versions of Windows SDKs from my machine, and exactly the same errors were seen when I tried installing standalone SDK
on clean Windows installation, it does not look to be related to VS 2017 RC or to existing installations of Windows SDK.However I found a workaround that solved my problem — I created Azure VM with region Japan East, and tried downloading SDK for offline installation, and that succeeded. I then copied over installation files from VM to my machine and successfully installed
SDK. It seems to be something geographically-related, e.g. could be something with Microsoft download servers configured for region of Denmark, or something with Danish internet gateways.
// best regards
Vlad Nagorny-
Edited by
Vlad Nagorny
Sunday, January 1, 2017 11:20 PM -
Proposed as answer by
宝宝徐
Monday, January 2, 2017 2:34 AM -
Marked as answer by
npgm
Monday, January 9, 2017 11:50 AM
-
Edited by
-
Hi upgm,
Thank you for your update.
Glad to hear you have had your issue resolved. And thanks for sharing us your result here.
You could mark Vlad’s reply and your reply as the answer, it will benefit to other community members who have the same issue. and be easier for them to search the solution.
Happy New Year:)
Best Regards,
MSDN Community Support
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.-
Edited by
宝宝徐
Monday, January 9, 2017 7:45 AM -
Marked as answer by
npgm
Monday, January 9, 2017 11:50 AM
-
Edited by
I’m a software developer with a Windows 10 PC. I have to support some older software written in Visual Studio 2010 using Windows SDK 7.1
In trying to set up the development environment, I have successfully installed VS2010, and come to install Windows SDK 7.1, however the installer gives the error:
Some components cannot be installed
Some Windows SDK components require the RTM .NET Framework 4. Setup detected a pre-release version of the .NET Framework 4. If you continue with Setup, these components will not be installed. If you want to install these components, click Cancel, then install the .NET Framework 4 from http://go.microsoft.com/fwlink/?LinkID=187668 and then rerun Setup.
However, Windows 10 comes with .NET 4.5, so as far as I can tell there is yet another version check problem.
This would not worry me so much, but in attempting to install the Visual Studio 2010 compiler update, this fails, saying
cannot install because windows sdk 7.1 is not found
Attempting to install .NET 4 fails because it detects a later version of .NET.
Wai Ha Lee
8,60885 gold badges57 silver badges92 bronze badges
asked Aug 19, 2015 at 9:28
2
I stumbled across another workaround, which I’ve also posted on a msdn thread:
-
Uninstall any Visual C++ 2010 Redistributables from the control panel first.
-
Download the corresponding offline ISO image from the Windows SDK archive. This lists which ISO is which.
-
After mounting the image, open F:\Setup\SDKSetup.exe directly.
answered Sep 12, 2015 at 1:11
Jeremy WongJeremy Wong
1,0301 gold badge10 silver badges9 bronze badges
8
I just ran into this same problem. No idea how safe this actually is to do, but I was able to work around it by temporarily fooling the installer into thinking I had a different version of .NET 4.0 installed. I opened Process Monitor and used it to monitor everything that setup.exe was doing in order to find out how it was determining that I had a «pre-release» version of .NET 4.0.
It turns out that it looks at these two strings in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Client\VersionHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full\Version
On my Windows 10 machine, these currently are both 4.6.00079. The installer doesn’t seem to like this value. I temporarily replaced both of them with the string 4.0.30319 in regedit to match the value from InstallPath, and that seemed to do the trick. And of course, when I was finished, I put them back the way they originally were.
However, I did not have permission to change those values, so it was a bit tricky. I right-clicked on the Client key, chose Permissions, and clicked Advanced. Then I changed the owner to my user account instead of TrustedInstaller. This allowed me to add permissions for Full Control for myself so I could modify the Version value. I repeated the same process on the Full key. After the installer completed successfully, I put the original version values back in (4.6.00079), deleted the permissions I added for myself, and restored the owner to TrustedInstaller (to do that, type NT SERVICE\TrustedInstaller as the username).
There might be a safer/easier way of intercepting the registry reads than actually modifying the registry, but this was simple enough for me!
answered Sep 1, 2015 at 3:08
dougg3dougg3
1,24911 silver badges9 bronze badges
4
@dougg3’s answer scripted:
First install SubInAcl,can be downloaded from Microsoft here. You may need to add it to your PATH, ex: set PATH=%PATH%;C:\Program Files (x86)\Windows Resource Kits\Tools
Then run these commands in an elevated cmd prompt:
for /f "tokens=2*" %%a in ('reg query "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client" /v Version /reg:32') do set "CurrentNDPv4ClientVersion=%%~b"
for /f "tokens=2*" %%a in ('reg query "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version /reg:32') do set "CurrentNDPv4FullVersion=%%~b"
subinacl.exe /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4" /setowner="%username%"
subinacl.exe /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4" /grant="%username%"=f
reg ADD "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version /t REG_SZ /d 4.0.30319 /reg:32 /f
reg ADD "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client" /v Version /t REG_SZ /d 4.0.30319 /reg:32 /f
echo start your installer now
pause
reg ADD "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client" /v Version /t REG_SZ /d %CurrentNDPv4ClientVersion% /reg:32 /f
reg ADD "HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version /t REG_SZ /d %CurrentNDPv4FullVersion% /reg:32 /f
subinacl.exe /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4" /revoke="%username%"
subinacl.exe /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4" /setowner="NT SERVICE\TrustedInstaller"
Ray Jasson
4222 gold badges9 silver badges23 bronze badges
answered Feb 12, 2016 at 7:59
janv8000janv8000
1,5692 gold badges19 silver badges33 bronze badges
8
Great answer by Dougg3 above. Just so it helps others, I went through the process and took some screen shots in case it helps anybody. I do have 64 bit Windows 10.
This is the reg edit file path that Dougg referenced.
Here click on Advanced button
Where it says Owner on the top click the Change link
The next image has two steps — first click on Advanced from «Select User or Group» then click on Find Now button on next dialogue which has the same title.
Find the user you want to change owner to then click ok
Click ok on the next page
Go to your user you just selected on previous dialogues then select Allow Full Control, then click OK
Now you’re able to edit the version.
After you’re finished with this revert the version number to what it was before and undo giving yourself the Full Control for that registry.
answered Sep 30, 2017 at 19:14
CAMD_3441CAMD_3441
2,5642 gold badges25 silver badges38 bronze badges
2
download the exe. change the extension from ‘exe’ to ‘zip’. extract the file now. run SDKSetup.exe from within the /Setup directory
answered Mar 23, 2017 at 6:00
0
If your here trying to install psycopg2 make sure your pip is up-to-date or you’ll get these errors.
pip install -U pip
pip install psycopg2-binary
See — http://initd.org/psycopg/docs/install.html
answered Jun 14, 2019 at 4:46
Andrew AllenAndrew Allen
6,5885 gold badges31 silver badges73 bronze badges
После обновления VS 2022 RC до LTSC возникла проблема со сборкой консольных приложений С++ — исчезла папка C:\Program Files (x86)\Windows Kits\10 . Такая проблема была и раньше на VS 2019 и VS 2022 RC и я решал ее путем копирования папки Windows Kits с другой машины (виртуальной), а также создания ветки v10.0 в реестре.
В случае с VS 2022 LTSC этот метод не сработал и тогда я по совету MS попробовал установить SDK самостоятельно.
При установке Windows SDK 10.0.22000.0 получаю нулевой результат ( как при выборе рабочей нагрузки в VS Installer, так и при online/offline). При этом в случае offline установки видно, что процесс идет нормально, но на 60% начинается откат и удаление установленных перед этим файлов в C:\Program Files (x86)\Windows Kits\10.
Удаление Студии как средствами самой Студии (с помощью Installer, и InstallCleanup.exe) , так и чистка реестра и дисков вручную не дали положительного результата.
Как решить эту проблему?
-
Вопрос задан
-
318 просмотров
If you’ve stumbled upon this post, it most likely means that you’re trying to install or update Visual Studio 2017 Community or Enterprise using the Visual Studio Installer tool. As you can easily notice, the installation phase is splitted into 2 steps: the download, which happen first, and the actual install.
The issue we’re talking about is related to the installation phase of the Win10SDK module, precisely Win10SDK_10.0.17763 at the time of writing — but we know that the issue also happened before and will most likely happen with future versions of the Win10SDK package as well.
The problem
The issue can be easily summarized with the following screenshot:
When this happens, the window GUI appear to be still responding and not locked up: however, pressing the Cancel button does nothing and basically hangs the tool undefinitely until its process is manually killed using Task Manager.
Such scenario can be troublesome, especially if you’re performing a «standard» VS2017 update, because you will be basically unable to launch Visual Studio until you fix that.
The setup for this installation of Visual Studio is not complete. Please run the Visual Studio Installer again to correct the issue.
needless to say, restarting and re-running the Visual Studio Installer will bring the same result: when it will try installing the Win10SDK, the tool will become stuck again.
The fix(es)
As this post from the VS developer community explains, the problem’s cause is related to a silent PowerShell script that gets executed during the Windows App Certification Kit installation phase that
Workaround #1
Luckily enough, the workaround for such issue is actually rather simple:
- Navigate to the Microsoft Windows 10 SDK official web page.
- Download the Win10SDK installer executable (or the ISO image if you prefer).
- Run it manually using administrative priviledges (very important).
- After the setup is done, launch the Visual Studio Installer and install (or update) Visual Studio 2017.
As you can see, installing the SDK with administrative priviledges is the key to work around the Windows App Certification permissions issue without having to mess with the existing Local Group Policies. If you don’t do that, you’ll most likely get the following:
Workaround #2
If running the Windows 10 SDK installer with administrative priviledges is not enough to fix your issue, you can try to temporarily enable the Local Group Policy using the Windows built-in Group Policy Editor in the following way:
- Launch the Group Policy Editor: Start > Run > gpedit
- Navigate through Computer Configuration > Administrative Templates > Windows Components > Windows Powershell (see screenshot below)
- Set the Turn on Script Execution switch to Enabled, then sets its execution policy to Run all scripts.
Once done, try install or update Visual Studio again.
IMPORTANT: Remember to revert this change right after installing or updating Visual Studio, as leaving it like that will pose a non-trivial security issue on your machine.
Workaround #3
If none of the above workarounds worked, the last thing you can do is to uninstall and reinstall Visual Studio from scratch using the Visual Studio Installer tool: such procedure can be time-consuming, but is 100% guarranteed to work and will bring you back a clean installation of the latest version of VS2017.
Conclusion
That’s it, at least for now: we sincerely hope that this post will help other Visual Studio developers to work around this nasty issue, hoping that Microsoft and the VS team will fix it soon enough. If you have additional workarounds to suggest, feel free to leave a comment and we’ll be more than happy to add them to the list.