Image windows-2022: Microsoft.VCToolsVersion.v143.default.props contains wrong version #9670
Closed
2 of 13 tasks
Labels
Area: Common Tools
bug report
bug
Something isn't working
investigate
Collect additional information, like space on disk, other tool incompatibilities etc.
OS: Windows
Description
As described in azure-pipelines-agent issue #4554 and this Developer Community post, the current windows-2022 runner image has a wrong toolset version in the
Microsoft.VCToolsVersion.v143.default.props
file, leading to linker errors in certain build configurations.Specifically, linking a static library calling
sleep_for
into an executable will cause a linker error such as this:One of my projects exposes the issue in a very reproducible way: https://github.com/kblaschke/frontend-sdl2/actions
There are lots of other reports on GitHub and elsewhere having the same issue, possibly caused by a broken Visual Studio update. Examples:
Platforms affected
Runner images affected
Image version and build link
Current runner version: '2.315.0'
Example failed build: https://github.com/kblaschke/frontend-sdl2/actions/runs/8619445446/job/23624147736
Is it regression?
2.311.0, https://github.com/kblaschke/frontend-sdl2/actions/runs/7588250886/job/20670360139
Expected behavior
The build should succeed, and the static library linked without an error.
Actual behavior
The build fails due to linker errors, most likely because the different builds steps select different toolset versions due to the broken .props files.
Repro steps
std::this_thread::sleep_for
inside a function. The Poco::File class from the POCO framework is the one exposing an issue in my builds for example.The text was updated successfully, but these errors were encountered: