How to install packages with mingw triplet wihout pwsh7(if possible)

[kasytano (catnoteafish)]

For some reasons, I have no way to apply windows update for my pc, and I got the result.

PS E:\NyaDB> $env:VCPKG_DEFAULT_TRIPLET="x64-mingw-static"
PS E:\NyaDB> $env:VCPKG_DEFAULT_HOST_TRIPLET="x64-mingw-static"
PS E:\NyaDB> cat .\vcpkg.json
{
  "name": "nyadb",
  "version": "0.1.0",
  "dependencies": [
    "libuv",
    "flatbuffers"
  ]
}

PS E:\NyaDB> vcpkg install
Detecting compiler hash for triplet x64-mingw-static...
-- Automatically setting %HTTP(S)_PROXY% environment variables to "127.0.0.1:7897".
A suitable version of powershell-core was not found (required v7.6.2).
Extracting powershell-core...
error: "E:\vcpkg\downloads\tools\powershell-core-7.6.2-windows\pwsh.exe" --version failed with exit code 2148734214
Fatal error.
Your Windows doesn't fully support CET. Please install all available Windows updates.
E:\vcpkg\downloads\tools\powershell-core-7.6.2-windows\pwsh.exe: note: failed to run to determine the powershell-core version

I tried to install pwsh 7 manually, but I got the same dialog box: Unknown hardware error. So, is there any way to avoid use pwsh7?(msvc doesn't suit other dependencies what will use in this project).

[kasytano (catnoteafish)]

System information:
OS Name: Microsoft Windows 10 Pro
Version: 10.0.19045 Build 19045

[VectorPeak (VectorPeak)]

There isn't a supported switch to make current vcpkg use Windows PowerShell 5.1 instead of pwsh for this path. The dialog in the screenshot is pwsh.exe itself crashing with “Unknown Hard Error”, so vcpkg never gets far enough to use it.

One thing to change: don't set the host triplet to MinGW unless you specifically need host tools built with MinGW. Use MinGW only for the target packages:

$env:VCPKG_DEFAULT_TRIPLET="x64-mingw-static"
Remove-Item Env:VCPKG_DEFAULT_HOST_TRIPLET -ErrorAction SilentlyContinue

vcpkg install --triplet x64-mingw-static --host-triplet x64-windows

That may avoid some unnecessary MinGW host-tool work, but it will not bypass pwsh if vcpkg needs it to acquire/use the MinGW/MSYS2 tooling. If pwsh.exe cannot run on this machine, the practical options are to use an older vcpkg commit from before this powershell-core-7.6.2 tool requirement, or run vcpkg on a different/updated Windows install/VM.

[Aleksandr Kovalko (gistrec)]

That crash isn't about the mingw triplet — it's vcpkg's bundled pwsh.exe (PowerShell 7.6.2) failing to start. It's a .NET 9 app, and since .NET 9 the app host is compiled /CETCOMPAT (Intel CET / shadow stack) by default. On a machine whose Windows lacks full CET support (yours, without the updates), the runtime aborts at startup — exactly your exit 0x80131506 / "Your Windows doesn't fully support CET". A hand-installed pwsh 7 dies the same way for the same reason.

You can't rebuild the binary (the other documented opt-out, <CetCompat>false</CetCompat>, needs a recompile), so disable the shadow-stack mitigation for that exe via Exploit Protection.

GUI: Windows Security → App & browser control → Exploit protection → Program settings → add pwsh.exe → turn off "Hardware-enforced stack protection".

Scriptable, from an elevated Windows PowerShell:

Set-ProcessMitigation -Name pwsh.exe -Disable UserShadowStack

Then vcpkg's pwsh launches and vcpkg install proceeds (the override is by image name, so it also covers your manually-installed pwsh). Note it turns off an exploit mitigation for pwsh specifically — a minor tradeoff, but it's Microsoft's documented workaround when the Windows updates aren't an option.