Latest Visual C++ 2022 version in Windows images has a SIMD optimization bug that makes it unreliable

[lballabio]

Description

See https://developercommunity.visualstudio.com/t/Code-optimization-bug-SIMD-std::transf/10912292. A fix is pending release, but in the meantime it would help to downgrade to a working version.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

The problem started in windows-2022 version: 20250617.1.0, e.g. https://github.com/lballabio/QuantLib/actions/runs/15800989037/job/44539149267.

Is it regression?

The build worked in windows-2022 version 20250609.2.0, e.g. https://github.com/lballabio/QuantLib/actions/runs/15657466165

Expected behavior

The test suite should run without reporting any errors.

Actual behavior

The generated code is incorrect leading to test suite failures.

Repro steps

A simple C++ file and compilation command line is available at https://developercommunity.visualstudio.com/t/Code-optimization-bug-SIMD-std::transf/10912292.

[lballabio]

The working image had the MSVC toolset 14.43.34808 installed; the non-working image has 14.44.35207.

[vidyasagarnimmagaddi]

HI @lballabio , Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.

[cacti77]

Many of my Windows DevOps jobs have started failing since the upgrade from the 20250609.2.0 version of the 'windows-latest' image to the 20250617.1.0 one; see here. This may be related to what you're seeing too.

[cacti77]

in the meantime it would help to downgrade to a working version.

100% agree! We've currently reverted to 'windows-2019' as a temporary workaround ('windows-2025' seems to have the same issues as 'windows-2022') but that will apparently be withdrawn on 30 June!

[flomnes]

One of our CI jobs is failing, possibly because of this. Is there any workaround ? We tried disabling optimizations through /Od, but it didn't work.

[AniLeo]

I also tried /Od and it didn't work

We are also impacted at RPCS3 with RPCS3/rpcs3#17326

There should really be a runner image running on the previous msbuild version so we could switch to that while the issue gets addressed. We can't even go back to windows-2022 since the msbuild version is the same as windows-2025.