hatch run does fail on all commands

[OlafHaag]

Hey! My problem is simple: hatch run does not work for me anymore on any command and I'm having trouble figuring out why that is. I'm using version 1.7.0.
I created a minimal example, starting with hatch new:

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "runscripts"
version = "0.1.0"
description = 'test to run scripts with hatch'
readme = "README.md"
requires-python = "~=3.10.0"
license = "MIT"

[tool.hatch.envs.test]
skip-install = true
detached = true

[tool.hatch.envs.test.scripts]
ignore-fail = "- true"
check-fail = "true"
hello = "echo 'hello world'"

Then in powershell on Windows I activated my conda environment that has hatch installed, and ran hatch -v run test:hello, getting this output:

──────────────────────────────────────────────── test ────────────────────────────────────────────────
Finished creating environment: test
Finished checking dependencies
cmd [1] | echo 'hello world'

which exited with code 1.
While hatch -v run ignore-fail exits successfully as expected with code 0.
Still it seems that whatever I put into a command, it fails to even start execution. I also tried setting shell="powershell" in hatch's config.toml file.

I also tried with a fresh conda environment with hatch installed.
What can be causing this and is there an option for even more verbose output?

[ofek]

On Windows the commands will run with the default shell cmd so single quotes don't work and true is not a built-in (same for powershell)

[OlafHaag]

Thanks for the info! I fail to set the shell to something different. I tried setting it in the config.toml that is in %USERPROFILE%\AppData\Local\hatch with shell="pwsh" and when that didn't work I also tried with

[shell]
name = "pwsh"
path = "C:/Users/olaf/AppData/Local/Microsoft/WindowsApps/Microsoft.PowerShell_8wekyb3d8bbwe/pwsh.exe"

But hatch still picks cmd as the shell for the run command.
Now I found that my cmd itself is broken. Even just trying to open it in a terminal immediately exits, so this is not a problem with hatch. What is a problem is that I can't manage to choose a different shell.
From within a powershell session hatch -e test shell enters the environment without a problem.
Any hints?

[OlafHaag]

I was able to solve the issue with C:\Windows\System32\reg.exe DELETE "HKCU\Software\Microsoft\Command Processor" /v AutoRun /f . Had nothing to do with hatch, but a broken cmd was affecting hatch. Couldn't figure out how to successfully switch shells on Windows, though.