Is taiki-e/install-action@v2 enough to get this fix? I'm still seeing this.

Haven't seen this issue since updating to 2.71.2

@Darksonn
Thanks for the report! I checked the log:

• This PR's fix is included in the version you're using (eea29cf).
• The issue you encountered occurs after bash has started. (This PR fixed the issue with bash startup.)
• The issue you encountered seems to indicate that the windows-11-arm runner bug also exists when starting x86_64 binaries other than bash. In both cases, the root cause of the issue seems to be the same.
  • In the log, cargo location is displayed, but "installing " is not, so I think the startup of the command is failing due to one of dirname (1, 2) or jq (1, 2, and more).
    • dirname is likely installed in the same way as bash, so it’s the most suspicious.

I removed the use of dirname in 2.75.14 (6fc852a), so hopefully that will resolve or mitigate the issue you encountered.