it seems this could be a real blocker for Windows users (which I believe is still a big group of users) and it prevents them to use Camel Testing plugin..

The only possible workaround is to switch directly to Citrus JBang, but than some features are lost like eg. for init file

• tests are not auto-generated into `test` sub-folder
• `jbang.properties` is not auto-generated

This is also a blocker for Kaoto to bring a Citrus Testing feature into Kaoto VS Code extension which was defined as one of OKRs for 2026.

Reproducer

For example init a new test file using 

camel test init <filename>

or just call 

camel test --help

on a macOS or Linux this is working just fine

Logs Output

PS C:\Users\hudson\vscode-kaoto\test Fixture with speci@l chars\kaoto-view\example-tests> jbang '-Dcamel.jbang.version=4.17.0' camel@apache/camel test --help
2026-02-12 13:23:35.625  WARN 4300 --- [           main] org.citrusframework.jbang.JBangSupport   : JBang installation not found. Downloading ...
2026-02-12 13:23:35.641  INFO 4300 --- [           main] org.citrusframework.jbang.JBangSupport   : Using local JBang in C:\Users\hudson\.jbang
'C:\Users\hudson\.jbang\jbang\bin\jbang.cmd' is not recognized as an internal or external command,
operable program or batch file. 

Using a Citrus Framework through Citrus JBang plugin directly and executing is working just fine

citrus init <filename>