java.io.IOException: Cannot run program "powershell.exe": CreateProcess error=2
See original GitHub issueThis was originally reported by @xshi0001 as https://github.com/sbt/sbt/issues/5386
steps
sbt version: 1.3.4 window10
problem
xshi0@LAPTOP-L904TFAI MINGW64 /d/WorkPlace/Flink/2-demo/springBoot-flink
$ sbt
[warn] No sbt.version set in project/build.properties, base directory: D:\WorkPlace\Flink\2-demo\springBoot-flink
[error] java.io.IOException: Cannot run program "powershell.exe": CreateProcess error=2, 系统找不到指定的文件。
[error] Use 'last' for the full log.
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? l
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (4 by maintainers)
Top Results From Across the Web
java.io.IOException: Cannot run program "powershell.exe ...
java.io.IOException: Cannot run program "powershell.exe": CreateProcess error=2, The system cannot find the file specified #5386.
Read more >java - Error while run the powershell command - Stack Overflow
note : i map the correct path. I tried with the above code but it gives the error like java.io.IOException: Cannot run program...
Read more >All powershell workflows fail - Cannot run program ...
Error: "Cannot run program "powershell" (in directory "D:\Program ... CreateProcess error=2, The system cannot find the file specified".
Read more >java.io.IOException: Cannot run program "powershell.exe"
io. IOException: Cannot run program "powershell.exe" I can see the that repo has been successfully cloned as folders and scripts all now exist ......
Read more >If "powershell.exe" is not in PATH "Add..." action for ... - YouTrack
IOException: Cannot run program "powershell.exe": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Agreed. Would it be possible for you to create/test a patch that checks those two things in addition to using path?
I’d look into migrating to Base64 encoding the command as you suggested in https://github.com/soc/directories-jvm/issues/26#issuecomment-583901362.
With those two things in place, I’d cut a new release soonish if that works for you?
@alexarchambault https://github.com/soc/directories-jvm/pull/30