Continual failure to install any Windows 11 SDK on a specific machine - does not complete

Question

Continual failure to install any Windows 11 SDK on a specific machine - does not complete

GlenF-5353 15

In this Visual Studio issue, I describe my ongoing attempts (and failures) to install the latest Windows 11 SDK, either through the VS installer or using the standalone WinSDK installer. In that issue, I was finally told to open a new issue here, since it appears not to be related to VS, but seems to be entirely an issue with the WinSDK installer.

I have been unable to install any of the Windows 11 SDK versions (10.0.22621 or 10.0.22000) on a specific machine. The installer stops when it gets to "Windows SDK for UWP C++ Apps" (roughly 80% progress through the install) and then it never completes. Eventually, after 15 or more minutes waiting, I kill it. There is no CPU activity on the winsdksetup.exe processes.

I have not had this problem on other machines, where the latest Windows 11 SDKs install fine. The machine in question is running Windows 11 Pro (Version 10.0.22621 Build 22621). It is able to install Windows 10 SDK versions, such as 10.0.20348, without problems.

Hopefully you can help me sort this out so that I can "clean" whatever is preventing the proper install on this machine... ideally without requiring a full clean reinstall of Windows.

As requested in the other (VS) issue, I can attach the WinSDK installer logs from my most recent attempt.

Thank you.

GlenF-5353 15

I don't really know how to interpret the SDK installer log files. However, if I open (what appears to be) the main log file, then search for "UWP C++", I find it. A bit lower down, I find this in the log -- though I don't know if that's why it failed. Presumably, the installer should pop up a message, or exit with some failure code, rather than just freezing.

Is it possible the lack of .NET Framework or KB 3118401 is actually causing the installer to freeze? According to the Add & Remove Programs, I do have Microsoft .NET Framework 4.8.1. SDK installed. I don't seem to have KB 3118401 installed (but I see it's a very old update -- from Windows 7, from 2016 -- so I expect Windows 11 to contain whatever fixes would be required from it!).

From line 3334 of the file in %TEMP%\windowssdk\Windows_Software_Development_Kit___Windows_10.0.22621.2428_20231109115524.log:

  <CustomStrings>
    <String Id="WarningPageTitle">Important Information!</String>
    <String Id="WarningPageParagraph1">Some features of the Windows 10 Software Development Kit (SDK) are not supported on this version of Windows. The Windows 10 SDK supports some versions of Windows as a targeting platform only, not as a development platform.  For detailed information, see the Release Notes for the Windows 10 SDK.</String>
    <String Id="WarningPageParagraph2">If you continue with this installation, only those components that are supported on this version of Windows will be available to install.</String>
    <String Id="WarningPageParagraph3">To continue with setup, choose Next.</String>
    <String Id="SecondWarningPageTitle">Important Information!</String>
    <String Id="SecondWarningPageParagraph1">The .NET Framework 4.6.1 is not installed. You cannot install the .NET Framework 4.8.1 Software Development Kit (SDK) feature of the Windows 10 SDK unless the .NET Framework 4.6.1 is installed prior to running setup.</String>
    <String Id="SecondWarningPageParagraph2">To ensure that you install all of the features of the Windows 10 SDK, close setup now, install the .NET Framework 4.6.1, and then run setup again.</String>
    <String Id="SecondWarningPageParagraph3">To proceed with the installation without the .NET Framework 4.8.1 SDK, choose Next.</String>
    <String Id="ThirdWarningPageTitle">Windows Software Development Kit Cannot Install</String>
    <String Id="ThirdWarningPageParagraph1">Setup has detected that KB 3118401 is not installed.</String>
    <String Id="ThirdWarningPageParagraph2">This version of the Windows SDK requires the Windows update known as "Update for Universal C Runtime in Windows, KB 3118401". Please run Windows Update and make sure your installation includes all the recommended updates or install the KB directly and try setup again.</String>
    <String Id="ThirdWarningPageParagraph3">Click here to view </String>
    <String Id="ThirdWarningPageHyperlinkStatement">KB 3118401</String>
  </CustomStrings>

Luke Westendorf 0 Reputation points Microsoft Employee

2023-11-10T22:56:47.7566667+00:00

Corresponding Visual Studio ticket: https://developercommunity.visualstudio.com/t/No-Windows-SDK-is-available-or-visible/10438447
GlenF-5353 15 Reputation points

2023-11-16T11:24:42.1733333+00:00
Just tried again, same result. Where it freezes is installing "Windows SDK for UWP C++ Apps". In particular, in the log, the last thing it logged before getting stuck is this:

[1240:2C50][2023-11-16T12:17:03]i301: Applying execute package: package_WindowsSDKforWindowsStoreAppsHeaders_x86_en_us, action: Install, path: C:\ProgramData\Package Cache\{6D937291-8DF8-992B-06F6-7DDE18A06D4E}v10.1.22621.2428\Installers\Windows SDK for Windows Store Apps Headers-x86_en-us.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" KITSROOT="C:\Program Files (x86)\Windows Kits\10\" KITSOPTION="OptionId.UWPCPP" ARPSYSTEMCOMPONENT="1" UserLocale="en-gb"'

I don't know why it sets UserLocale to "en-gb", whereas it's trying to load the ...Headers_x86_en_us.msi package, don't know if that's a problem. My Windows settings region is actually Spain, and my Windows display language is English (Canada). I have no idea if that is related to the problem, but these are the same on other PCs where the SDK installs fine, so I suspect it's not the problem.

GlenF-5353 15

I noticed this error, too, in the log file Windows_Software_Development_Kit___Windows_10.0.22621.2428_20231116121330_001_package_WindowsSDKforWindowsStoreAppsHeaders_x86_en_us.log:

Product: Windows SDK for Windows Store Apps Headers -- Error 1714. The older version of Windows SDK for Windows Store Apps Headers cannot be removed. Contact your technical support group. System Error 1612.

A bit more context just before that point:

           ******* Product: {A7121C79-6CAF-F5A2-065C-6545C1226756}
           ******* Action: 
           ******* CommandLine: **********
MSI (s) (80:9C) [12:17:03:847]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (80:9C) [12:17:03:847]: User policy value 'DisableMedia' is 0
MSI (s) (80:9C) [12:17:03:847]: Machine policy value 'AllowLockdownMedia' is 1
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Looking for sourcelist for product {A7121C79-6CAF-F5A2-065C-6545C1226756}
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Adding {A7121C79-6CAF-F5A2-065C-6545C1226756}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Now checking product {A7121C79-6CAF-F5A2-065C-6545C1226756}
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Trying source C:\ProgramData\Package Cache\{A7121C79-6CAF-F5A2-065C-6545C1226756}v10.1.22621.755\Installers\.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{A7121C79-6CAF-F5A2-065C-6545C1226756}v10.1.22621.755\Installers\Windows SDK for Windows Store Apps Headers-x86_en-us.msi 3: -2147287037 
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1706 2: -2147483647 3: Windows SDK for Windows Store Apps Headers-x86_en-us.msi 
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Processing net source list.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1706 2: -2147483647 3: Windows SDK for Windows Store Apps Headers-x86_en-us.msi 
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Processing media source list.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 2203 2:  3: -2147287037 
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1706 2: -2147483647 3: Windows SDK for Windows Store Apps Headers-x86_en-us.msi 
MSI (s) (80:9C) [12:17:03:847]: SOURCEMGMT: Processing URL source list.
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1402 2: UNKNOWN\URL 3: 2 
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1706 2: -2147483647 3: Windows SDK for Windows Store Apps Headers-x86_en-us.msi 
MSI (s) (80:9C) [12:17:03:847]: Note: 1: 1706 2:  3: Windows SDK for Windows Store Apps Headers-x86_en-us.msi 
MSI (s) (80:9C) [13:57:09:592]: SOURCEMGMT: Failed to resolve source
MSI (s) (80:C0) [13:57:09:608]: Note: 1: 1714 2: Windows SDK for Windows Store Apps Headers 3: 1612 
MSI (s) (80:C0) [13:57:09:608]: Product: Windows SDK for Windows Store Apps Headers -- Error 1714. The older version of Windows SDK for Windows Store Apps Headers cannot be removed.  Contact your technical support group.  System Error 1612.

Again, when there is an error, it should not just freeze, it should report an error of some sort, and stop the install.

Can someone please suggest how I can get my machine into a state where the Windows SDK install can succeed (without doing full Windows reinstall)?

Thanks.

Никита Юрчик 0 Reputation points

2023-12-29T13:00:20.29+00:00

Hello, Glen

Have you got luck solving this issue (or the previous)?
GlenF-5353 15 Reputation points

2024-01-05T17:29:28.8333333+00:00

No, I've not had any replies or further help since posting here, other than the earlier help from the VS team, who persisted with me for a number of months until realizing this was totally a WinSDK issue, not related to VS.

Any suggestions are welcome (although read the other ticket to see all the things I've already tried).
KEROUMI HIBA 0 Reputation points

2025-03-21T03:23:07.6733333+00:00

Hy GlenF-5353 , Please I wanna ask why you search for another sdk while the 10.0.20348.0 worked fine for you?

1 answer

Your answer

Luke Westendorf 0 Reputation points Microsoft Employee

2023-11-10T22:56:47.7566667+00:00

Corresponding Visual Studio ticket: https://developercommunity.visualstudio.com/t/No-Windows-SDK-is-available-or-visible/10438447
GlenF-5353 15 Reputation points

2023-11-16T11:24:42.1733333+00:00

Just tried again, same result. Where it freezes is installing "Windows SDK for UWP C++ Apps". In particular, in the log, the last thing it logged before getting stuck is this:

[1240:2C50][2023-11-16T12:17:03]i301: Applying execute package: package_WindowsSDKforWindowsStoreAppsHeaders_x86_en_us, action: Install, path: C:\ProgramData\Package Cache\{6D937291-8DF8-992B-06F6-7DDE18A06D4E}v10.1.22621.2428\Installers\Windows SDK for Windows Store Apps Headers-x86_en-us.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" KITSROOT="C:\Program Files (x86)\Windows Kits\10\" KITSOPTION="OptionId.UWPCPP" ARPSYSTEMCOMPONENT="1" UserLocale="en-gb"'

I don't know why it sets UserLocale to "en-gb", whereas it's trying to load the ...Headers_x86_en_us.msi package, don't know if that's a problem. My Windows settings region is actually Spain, and my Windows display language is English (Canada). I have no idea if that is related to the problem, but these are the same on other PCs where the SDK installs fine, so I suspect it's not the problem.
Никита Юрчик 0 Reputation points

2023-12-29T13:00:20.29+00:00

Hello, Glen

Have you got luck solving this issue (or the previous)?
GlenF-5353 15 Reputation points

2024-01-05T17:29:28.8333333+00:00

No, I've not had any replies or further help since posting here, other than the earlier help from the VS team, who persisted with me for a number of months until realizing this was totally a WinSDK issue, not related to VS.

Any suggestions are welcome (although read the other ticket to see all the things I've already tried).
KEROUMI HIBA 0 Reputation points

2025-03-21T03:23:07.6733333+00:00

Hy GlenF-5353 , Please I wanna ask why you search for another sdk while the 10.0.20348.0 worked fine for you?

Answer 1

I just ran into this problem as well. From what I can tell it is trying to uninstall an old component of the SDK that isn't on the machine anymore and isn't handling that case well. If you are comfortable with registry edits, here is how I got past it:

Referring to the last log you attached referencing "C:\ProgramData\Package Cache{GUID}", copy out the GUID (I just used general GUID here as it was a different one in my case and expect it will still apply here). Search for GUID in the registry and remove those references. In cases where it was a piece of data in a node, I removed the node. I expect you may only need to remove the one that relates to information about uninstallers but I removed them all. After that the install proceeded just fine.

Also, before doing this, I would recommend running any SDK uninstalls that show up either in the control panel uninstall or apps uninstall as that may clean up some stuff for you. Hopefully this helps!

Share via

Continual failure to install any Windows 11 SDK on a specific machine - does not complete

1 answer

Your answer