Error: spawn git.exe ENOENT
See original GitHub issueDescription
Upgraded to Desktop v1.3, got this error immediately after it opened:
Version
- GitHub Desktop: 1.3.0
- Operating system: Windows
Steps to Reproduce
- Update Github Desktop to v1.3
- Get Error
Logs
No errors in the logs
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:31 (14 by maintainers)
Top Results From Across the Web
VS Code Error: spawn git ENOENT - Stack Overflow
I get the error Error: spawn git ENOENT when I try to view git history using https://github.com/DonJayamanne/gitHistoryVSCode on VS Code.. I'm very new...
Read more >Error: spawn git ENOENT · Issue #100 - GitHub
I keep getting this error message: Error: spawn git ENOENT when I try to view git history log for a private repository that...
Read more >errno: -4058, code: 'enoent', syscall: 'spawn git', path - You.com
ENOENT means that a file does not exist. The path indicated is git . gh-pages is trying to use git but it seems...
Read more >npm ERR! enoent spawn git ENOENT - sneppets -
This tutorial guides you how to resolve npm error spawn git ENOENT when trying to install required dependencies from git.
Read more >Git node error can't clone or pull - Questions - n8n community
When I execute git node in my workflow, it can't pull or clone operation. What is the error message (if any)?. ERROR: Error:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks to everyone who has reported this. We believe this is related to missing repositories and the new repository indicator feature.
What’s happening here is:
ENOENT
error (because it’s trying to be run in a directory that doesn’t exist)As a workaround, you can remove these missing repositories on disk - it might take some time to click through the list and find the problem repository.
We’re working on a fix now to handle this error and not display any UI. Stay tuned.
1.3.1
has been published, and should address the issue of background updates.We are also tracking #5289 which you might encounter when you manually switch to a repository that’s been removed outside Desktop, and that will hopefully go into the next update.