4 ms·
Tried running bash by renaming it to bash.exe using both CMD and Powershell and both return "Access denied. Even though Windows 10 already has Terminal and I w
by smusamashah 3y ago
Tried running bash by renaming it to bash.exe using both CMD and Powershell and both return "Access denied.
Even though Windows 10 already has Terminal and I was getting
[error 2147942405 (0x80070005) when launching `C:\bin\bash -l']
I downloaded Terminal Preview which still throws the same error. Is Terminal or Terminal Preview the only way to run bash? There might be a way to configure cmder to use bash in a similar way you suggested for Terminal. Don't know how yet.
- jart 3y agoTry whitelisting the folder with Windows Defender. Sometimes when I get EACCES style errors on Windows mysteriously, it's because I need to recalibrate the security on the folder. Here's an example of something I ran once which fixed it. PS C:\WINDOWS\system32> $ACL = Get-ACL -Path C:\Users\jtunn PS C:\WINDOWS\system32> $ACL | Set-ACL -Path C:\bin I also just uploaded cosmos-3.0.1.zip to Microsoft Security Intelligence to make sure they get whitelisted with their cloud security.
- AMICABoard 3y agoDiscuss here: https://github.com/jart/cosmopolitan/discussions https://github.com/jart/cosmopolitan/discussions Add issues here: https://github.com/jart/cosmopolitan/issues https://github.com/jart/cosmopolitan/issues
- marwis 3y agoI linked bash to bash.exe and was able to start it however everything from /bin was failing with: The application was unable to start correctly (0xc0000142). Turns out it doesn't work when I start bash by double click bash.exe but it works if I start it from cmd.exe.