No Screenshot

Submit Screenshot

The latest version of Cygwin as of 03/08/2020

Application Details:

Version: 3.1.6
License: Free to use and share
Votes: 0
Latest Rating: Garbage
Latest Wine Version Tested: 5.13

Maintainers: About Maintainership

Free Download Cygwin's Home Page

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

The installer works, though there are a few (unimportant looking) errors for a few of the default packages.

Very little. Mintty almost opens but fails with a "fork: Resource Temporarily Unavailable" error. Running Cygwin's bash.exe from the Wine Command Prompt does work, but it exits after trying to run just one command (like "ls")/

What does not

Not usable due to above issues. I have not tried to install additional software beyond the default selection.


What was not tested

Everything not mentioned above - I was not able to get far enough to test anything else.

Hardware tested


  • GPU: AMD
  • Driver: open source

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentLinux Mint 20 "Ulyana"Aug 03 20205.13Yes Yes NoGarbageHamish McIntyre-Bhatty 

Known Bugs

Bug # Description Status Resolution Other apps affected
12104 Cygwin's setup.exe doesn't resize properly NEW View
39627 BreezeBrowser Pro 1.x crashes on start (FSCTL_GET_REPARSE_POINT is not implemented) NEW View

Show all bugs


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Workarounds exist
by Damjan Jovanovic on Saturday August 15th 2020, 8:45
The bash.exe problem where it exits after the first command is this bug:

You can work around it by build Wine from source with this one line patch:
RE: Workarounds exist
by Hamish McIntyre-Bhatty on Monday August 17th 2020, 5:55
Ah, good to know. I won't personally be doing that, but I know someone who could be helped by this.

Cheers :)
RE: Workarounds exist
by Hamish McIntyre-Bhatty on Wednesday August 19th 2020, 10:09
I had a go, I couldn't resist.

Unfortunately I couldn't get it to work (wine 5.15), I get the good old "Couldn't compute FAST_CWD pointer" error now. Quite possibly I haven't built WINE correctly, I don't know.
RE: Workarounds exist
by Damjan Jovanovic on Wednesday August 19th 2020, 11:40
The patch only fixes the problem where bash.exe exits after the first command, not the FAST_CWD problem.

The FAST_CWD warning however seems harmless to me. Is there any other issue you are experiencing?
RE: Workarounds exist
by Hamish McIntyre-Bhatty on Wednesday August 19th 2020, 12:04
Yeah, mintty now doesn't open at all when the patch is present.
Also, while bash now doesn't exit after running only one command, none of the commands seem to work, for example:


Never outputs anything, regardless of what path I give it. None of the options elicit any output either.
RE: Workarounds exist
by Damjan Jovanovic on Wednesday August 19th 2020, 18:20
That must be a recent regression. I definitely had "ls" working only a few months ago.

In Wine 5.14 wineconsole itself is currently hanging my whole desktop until killed, so it will take me a while to get set up again.
RE: Workarounds exist
by Hamish McIntyre-Bhatty on Thursday August 20th 2020, 12:27
How are you building WINE? I've been having serious trouble with building the 32-bit part.

I've now even gone as far as using a LXC container, but am unable to make an i386 container for my distro (Ubuntu 20.04): it always fails with an error and then deletes the logs so I can't see what went wrong.

For the moment I'll build under Ubuntu 18.04 containers, and hope those work for me anyway, but this is far from ideal I think.
RE: Workarounds exist
by Damjan Jovanovic on Tuesday June 22nd 2021, 21:33
You shouldn't need to build it from source any more. Bug 48891 (exit after first command) was fixed in Wine 6.11.
RE: Workarounds exist
by Hamish McIntyre-Bhatty on Tuesday July 5th 2022, 11:16
Can confirm it is fixed :)