10

I would just like to ask what could be the meaning of this error?

error: fsmonitor_ipc__send_query: unspecified error on '.git/fsmonitor--daemon.ipc'

I'm trying to find something similar to this case but for some reason, all I see is another line error which is very similar but isn't explained why. I encountered this while I'm using Git Bash. I'm trying to utilize the Bash terminal as I want to have a different window separated when working with VS Code. Hope this become a reference for the others.

Ramon Zarazua B.
  • 7,195
  • 4
  • 22
  • 26
Shironekomaru
  • 361
  • 1
  • 6
  • 15
  • Include the name and release of your OS, and your specific Git version here. The file system monitoring code is new, highly OS-dependent, and may contain various bugs. – torek Aug 25 '21 at 09:42
  • I'm seeing the same error here. I'm actually not using git bash, but rather Powershell, both 5.1 and 7.1. Git Version: 2.32.0.windows.1 OS Version: Windows 10 19043.1165 – Ramon Zarazua B. Aug 26 '21 at 01:31
  • After updating to Git 2.33 I do not see this message anymore. – Ramon Zarazua B. Aug 26 '21 at 01:35
  • @RamonZarazuaB. I'll try to update my Git as well. Thank you very much for informing me. – Shironekomaru Aug 26 '21 at 01:54
  • @torek I'm using Win10 x64 v.1904 while the Git vesion is 2.32. I'll try to update my git if that will solve the error. Thank you very much to all of you guys. – Shironekomaru Aug 26 '21 at 01:55
  • Same error here, but upgrade did not help. Git Version: 2.33.0. windows. OS Version: Windows Server 2019 Standard [Version 10.0.17763.2183]. VMware Virtual Platform. – Stiegler Sep 28 '21 at 07:33
  • I got this error, and it appears that it was caused by git daemon process running elevated (as Administrator) but `git pull` command called from a non-elevated process. Killing daemon and restating it non-elevated fixed the issue. But it could be a coincidence. – Vladimir Reshetnikov Oct 07 '21 at 01:00

3 Answers3

10

I, like others have mentioned, received this error, and my current Git version is 2.32.0.windows.1. I've been running this version for months and today was the first time I encountered the error.

I killed all running git.exe processes on my machine and the error went away.

Note that when you upgrade to a new version of Git, one of the things you have to do is stop all running processes of Git. I mention this because it might not be the case that this is a bug specific to 2.32 which is fixed in version 2.33, but instead, maybe it's simply the action of killing the running Git processes during the install that fixes the issue. I suppose a reboot may have fixed it as well.

TTT
  • 22,611
  • 8
  • 63
  • 69
4

Error seems to be related to a bug in Git for Windows 2.32. Upgrading to Git for Windows 2.33+ has fixed it for several people.

Ramon Zarazua B.
  • 7,195
  • 4
  • 22
  • 26
  • For anyone looking on how to update their git using windows please refer to this [link](https://stackoverflow.com/questions/13790592/how-to-upgrade-git-on-windows-to-the-latest-version) – Bryan Lim Sep 08 '21 at 06:21
  • 1
    I'm running git version 2.33.0.windows.2 , still get this message. I used to have core.fscache=true but now set to false but I still get this error every time I run git status – Amit G Oct 04 '21 at 14:24
  • Still getting it regardless of core.fscache – Menachem Hornbacher Oct 07 '21 at 18:15
  • I was getting this error on version 2.33.0.windows.2, updating to version 2.33.1.windows.1 fixed it. – somethingRandom Oct 20 '21 at 09:01
  • I got it on 2.35.0.windows.1, but I did check the experimental built-in file system monitor – AlignedDev Jan 25 '22 at 22:36
3

At first, uninstall git from your computer. Then delete the Git folder from C:\Program Files. Finally, install git again and restart your computer.

Raihan Ullah
  • 61
  • 3