WinSDK version 22000 in use is no longer supported or installable, warnings referencing it should be updated

[uint-nate]

https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes?tabs=allfeatures#17.14.11

The following Windows SDK versions have been removed from the Visual Studio 2022 installer: 10.0.18362.0, 10.0.20348.0 and 10.0.22000.0. If you previously installed one of these versions of the SDK using Visual Studio it will be uninstalled when you update. If your project targets any of these SDKs you may encounter a build error such as: The Windows SDK version 10.0.22000.0 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting "Retarget solution". To resolve this, we recommend retargeting your project to 10.0.26100.0, or an earlier supported version if necessary. For a complete list of supported SDK versions please visit: https://developer.microsoft.com/windows/downloads/sdk-archive/. If you need to install an unsupported version of the SDK, you can find it here: https://developer.microsoft.com/windows/downloads/sdk-archive/index-legacy.

There are multiple references to this legacy SDK version in this project, which give the following warnings when using the Microsoft.Windows.WinmdGenerator/0.63.31-preview build system:

 No VS installation detected that has all the required workloads installed (Microsoft.NetCore.Component.Runtime.8.0
 Microsoft.NetCore.Component.SDK Microsoft.VisualStudio.Component.VC.Tools.ARM64
 Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.Windows11SDK.22000). Use
 C:\Users\mulli\.nuget\packages\microsoft.windows.winmdgenerator\0.63.31-preview\scripts\Install-VS.ps1 to acquire VS
 with the required components.

Get-RequiredWorkloads.ps1

As noted in a later comment, this is just a warning, not a hard error as I originally thought, but it should be removed/updated probably.

[riverar]

That sample repo builds without 22000 SDK installed so COM > Rust workflows should be unaffected. Are you trying to build the win32metadata repository?

[uint-nate]

I am trying to use the Microsoft.Windows.WinmdGenerator/0.63.31-preview build system to build my own repo based off of the guide that you helpfully posted, and that's where I'm running into this issue 😅.

https://github.com/jonesnl/pluginrust is the repo I'm building.

Although now that I'm trying again to repro it, maybe that message is just a warning and not the error I thought it was?

PS C:\Users\mulli\projects\pluginrust\.metadata> dotnet clean

Build succeeded in 0.2s
PS C:\Users\mulli\projects\pluginrust\.metadata> dotnet build
Restore complete (0.3s)
  build succeeded (6.6s) →
    C:\Users\mulli\.nuget\packages\microsoft.windows.winmdgenerator\0.63.31-preview\Sdk\Sdk.targets(124,5): error :
      GetVcDirPath.ps1 failed: Set-ExecutionPolicy : The 'Set-ExecutionPolicy' command was found in the module 'Microsoft.PowerShell.Security', but
      the module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Security'.
      At line:1 char:4
      + & {Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted;  ...
      +    ~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : ObjectNotFound: (Set-ExecutionPolicy:String) [], CommandNotFoundException
          + FullyQualifiedErrorId : CouldNotAutoloadMatchingModule

      No VS installation detected that has all the required workloads installed (Microsoft.NetCore.Component.Runtime.8.0
      Microsoft.NetCore.Component.SDK Microsoft.VisualStudio.Component.VC.Tools.ARM64
      Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.Windows11SDK.22000). Use
      C:\Users\mulli\.nuget\packages\microsoft.windows.winmdgenerator\0.63.31-preview\scripts\Install-VS.ps1 to acquire VS
      with the required components.
      At C:\Users\mulli\.nuget\packages\microsoft.windows.winmdgenerator\0.63.31-preview\scripts\Get-VSPath.ps1:22 char:5
      +     throw "No VS installation detected that has all the required work ...
      +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : OperationStopped: (No VS installat...red components.:String) [], RuntimeException
          + FullyQualifiedErrorId : No VS installation detected that has all the required workloads installed (Microsoft.Net
         Core.Component.Runtime.8.0 Microsoft.NetCore.Component.SDK Microsoft.VisualStudio.Component.VC.Tools.ARM64 Microso
        ft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.Windows11SDK.22000). Use C:\Users\mull
       i\.nuget\packages\microsoft.windows.winmdgenerator\0.63.31-preview\scripts\Install-VS.ps1 to acquire VS with the r
      equired components.




Build succeeded in 7.2s

It still seems to be generating a winmd that I can consume with windows-bindgen alright. Maybe I was conflating that message with some other build issues I was seeing...

So I guess you're right, it's not a blocker, just an inaccurate warning. Updated the title to be less scary 😅 .

[riverar]

Interesting. Hmm, will take a closer look in ~1 hour. Glad you're not blocked at least!

[uint-nate]

Yep not blocked, just an FYI at this point

[riverar]

Strange, I can't reproduce this. I tried locking down PowerShell language mode and a few other things to no avail.

Set-ExecutionPolicy : The 'Set-ExecutionPolicy' command was found in the module 'Microsoft.PowerShell.Security', but the module could not be loaded.

Seems to indicate a local system lockdown or other problem with PowerShell?