I've just downloaded and installed Cygwin on Windows 7. It seems to have installed successfully, with the C:\Cygwin64 folder comprising 1.2GB of data when the installation folder I installed it from was just under 300MB. However, clicking the desktop shortcut opens mintty.exe, which then displays the error:

Failed to run '/bin/bash': No such file or directory

This is despite the fact I installed all of the base files, of which bash was supposedly part of - and even if it wasn't, the installer later showed it as a required package and installed it itself. So does anyone have any idea what's happening here? This might be my fourth attempt in the last day trying to get a successful install of Cygwin working; I'm starting to think I'm just not meant to have it.

  • Navigate to C:\Cygwin64, do you see there a file cygwin.bat ? Try to double click on it and let us know what happened – Alex Jan 29 '17 at 5:24
  • The .bat file was there, but clicking it made cmd flash for a fraction of a second and did nothing else. Still, I've managed to sort this now, as detailed in my answer. Thanks anyway, @Alex. – Hashim Jan 29 '17 at 5:55
up vote 0 down vote accepted

I managed to sort this with yet another installation - this time I opted to download and install from the net (option 1 in the installer), instead of downloading the files separately and installing from the locally-stored folder (options 2 and 3). I can't be sure why selecting those options was providing me with an incomplete installation, but I'm now able to run bash without errors.

  • file base installation is convenient choice when you already setup some cygwin installation and need to spread it across another computers. This way first you download from inet, and installation folder would stuffed full of packages on the end of installation that you can reuse on other computers later. – Alex Jan 29 '17 at 6:00
  • Agreed. Thankfully I didn't need it that urgently, so I can do without it, but it is a shame that it wasn't installing properly that way, could have been useful in the future. – Hashim Jan 29 '17 at 6:07

I had the same problem after a default fresh install directly from the web.

I solved it by going to "C:\cygwin64\bin" and duplicating "ash.exe" and renaming the copy to "bash.exe".

(I was trying this by pure chance, just because bash was missing and I found this ominous ash file)

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.