Win error 0xC0000142 since windows-2022 runner version 20240603.1.0

[lelegard]

Hi,

I have a build failure on runner windows-2022 since the upgrade

• from runner version 2.316.1, image version 20240514.3.0
• to runner version 2.317.0, image version 20240603.1.0

In the latter case, running an .exe that was just built, as part of the same job, now fails and exits with status -1073741502 (0xC0000142).

I cannot find an exact match for this error code. From Google, it seems to be a general error code when Windows is unable to start an application. Not very informative...

Context

The job is a "nightly build" of an open source project (https://github.com/tsduck/tsduck).

The executable is built and run inside the job. Its execution fails with status 0xC0000142.

It is a simple console application, a command-line tool named tsxml.exe. As the name implies, it manipulates XML files and outputs another XML file. The input XML files are part of the source files. The output XML file is part of the deliverables.

The command is run as part of the MSBuild project files as an AfterTargets='Build' for the executable tsxml.exe.

Works fine everywhere else

When the same build job is run on my Windows 11 system with Microsoft Visual Studio Community 2022 Version 17.10.1, it works fine.

This build job has been run for years on GitHub and on local systems, Windows 10 and 11.

The only key difference is the migration of the GitHub Windows runner. Any similar issue? Any idea?

Logs

Build logs from the Windows GitHub runners:

• Last successful run: https://github.com/tsduck/tsduck/actions/runs/9342975928/job/25711891614
• First failed run: https://github.com/tsduck/tsduck/actions/runs/9410344224/job/25921845384
• Workflow file: https://github.com/tsduck/tsduck/blob/master/.github/workflows/nightly-build.yml

The failed command has a very long command line. It appears in the log as:

2024-06-07T02:27:35.4596066Z          "D:\a\tsduck\tsduck\bin\Release-x64\tsxml.exe" --merge
<list if input XML files> --sort _tables --sort _descriptors --uncomment -o "D:\a\tsduck\tsduck\bin\Release-x64\tsduck.tables.model.xml"
2024-06-07T02:27:36.1844807Z    228>D:\a\tsduck\tsduck\scripts\msvc\msvc-build-tables-model.props(61,5): error MSB3073: The command
""D:\a\tsduck\tsduck\bin\Release-x64\tsxml.exe" ..." exited with code -1073741502. [D:\a\tsduck\tsduck\scripts\msvc\tsxml.vcxproj]
2024-06-07T02:27:36.1917382Z    228>Done Building Project "D:\a\tsduck\tsduck\scripts\msvc\tsxml.vcxproj" (default targets) -- FAILED.
2024-06-07T02:27:36.1918406Z    227>Done Building Project "D:\a\tsduck\tsduck\scripts\msvc\tsxml.vcxproj.metaproj" (default targets) --FAILED.
2024-06-07T02:27:36.1926225Z      1>Done Building Project "D:\a\tsduck\tsduck\scripts\msvc\tsduck.sln" ...) -- FAILED.
2024-06-07T02:27:36.1999204Z 
2024-06-07T02:27:36.1999519Z Build FAILED.

Any idea would be appreciated.

[lelegard]

After hours of debug and tests, it seems that the VC++ runtime has been broken in the upgraded windows-2022 image. I reported the bug as issue #10020

[lelegard]

This is definitely a bug in the windows-2024 runner. Many people complain in #10004 and #10020.
Let's close this thread.