https://bugs.winehq.org/show_bug.cgi?id=49802
--- Comment #6 from Brendan Shanks bshanks@codeweavers.com --- Steve Wishnousky posted on the Microsoft bug report that this issue should be fixed in the next Windows SDK version (presumably the next one released after the current 10.0.22000.0), and also that it should not happen with the older 10.0.14393.0 SDK.
" I’ve recently took another look and it appears an unrelated change has resolved this issue.
Since this is an issue in the Universal C Runtime, updates to the static library are shipped in the Windows SDK and updates to the DLL are delivered via Windows Update in new OS versions. The next major version of the Windows SDK and Windows will contain a Universal C Runtime that does not exhibit this behavior.
Until the new SDK is released, a workaround is to use an older Windows SDK to build with. I believe the 10.0.14393.0 Windows 10 SDK is the most recent SDK without this issue. It looks like this UCRT still references gs:60h, but not in the code path mentioned in the bug report. "