Open fpribeiro opened 1 month ago
Hi @fpribeiro - Thank you for bringing this issue to our attention. We are looking into this issue and will update you on this issue after investigating.
Running into this right now, currently preventing building the app. Also tried using this action https://github.com/GuillaumeFalourd/setup-windows10-sdk-action to install it but the build still fails and says it can not find it.
I managed to get the sdk installed in the meanwhile though it takes about 10 minutes
- name: Download Visual Studio installer
run: |
Invoke-WebRequest -Uri "https://aka.ms/vs/17/release/vs_enterprise.exe" -OutFile vs_enterprise.exe
- name: Install WinSdk 26100 with VS
run: |
$process = Start-Process -FilePath vs_enterprise.exe -ArgumentList "modify", "--add", '"Microsoft.VisualStudio.Component.Windows11SDK.26100"', "--installPath", '"C:\Program Files\Microsoft Visual Studio\2022\Enterprise"', "--wait", "--quiet", "--force", "--norestart" -Wait -PassThru
Write-Output $process.ExitCode
@RaviAkshintala can you explain the classification of feature request instead of bug? Is there a deliberate choice to not include the latest Windows SDK in the Windows 2022 image, and if so, why?
Description
The Windows 2022 image has Windows Driver Kit (WDK) 26100 but does not contain SDK 26100 (the latest SDK included is 22621).
Platforms affected
Runner images affected
Image version and build link
windows-2022 20240929.1.1
Is it regression?
No
Expected behavior
Image contains SDK 26100 and WDK 26100
Actual behavior
Image contains SDK 22621 and WDK 26100
Repro steps
Build a project that requires APIs published in SDK 26100 and the build will fail.