git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git bash 2.50.0(2) not working on windows 11 PRO 64bit

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jul 8, 2025, 11:15 UTC
Message-ID
<aGz95cpfS0s4zsMc@fruit.crustytoothpaste.net>
In-Reply-To
<C4F62B0F-1729-437B-B9C0-0FEA74B307E0@gmail.com>
On 2025-07-07 at 12:18:08, Fabio Frumento wrote:
> Hi,
Hi,
> After upgrading from 2.49 to 2.50 git bash won’t start anymore, a prompt window shortly appears and close immediately, downgrading to 2.49 solve the issue
> 
> So 2.50 don’t work on windows 11 Pro

The Git project doesn't ship any binaries, only source code, and we don't ship bash at all. The Git for Windows project, however, does ship Git bash, and you can report this problem to them at https://github.com/git-for-windows/git/issues.

I would suggest reading the contributor documentation and seeing if you can pin down more about why it's not working, since the report as it stands seems unlikely to be resolved. I feel confident that Git for Windows 2.50 actually works fine for many people on Windows 11 Pro, so the more information you can provide about what might be going on, the more likely it is that your bug will be addressed.

Best of luck with your problem.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Fabio FrumentoNext: Johannes Schindelin
Message 2 of 6 in “Git bash 2.50.0(2) not working on windows 11 PRO 64bit”
  1. Fabio FrumentoJul 7, 2025
  2. brian m. carlsonJul 8, 2025
  3. Johannes SchindelinJul 17, 2025
  4. Johannes SchindelinJul 17, 2025
  5. Fabio FrumentoJul 17, 2025
  6. Fabio FrumentoJul 18, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.