What happened?
gemini --yolo
in pwsh at 15:07:27
An unexpected critical error occurred:Error: EISDIR: illegal operation on a directory, realpath 'A:\a'
at async Module.realpath (node:internal/fs/promises:1176:10)
at async loadServerHierarchicalMemory (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/chunk-JS5WSGB2.js:51797:33)
at async loadCliConfig (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/gemini.js:7690:20)
at async main (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/gemini.js:14455:25)
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
What did you expect to happen?
Start gemini cli
A:\ is a virtual drive mounted in windows, gemini failed to open, but it was ok in the past. He suggested some modifications try catch:
✦ I have successfully applied the local patch to fix the EISDIR crash and created a tracking log at C:\Users\Greuceanu\gemini-patch-log.md.
You can now use the Gemini CLI from A:\ or other virtual drives without it crashing during initialization.
Regarding reporting this to the developers: Yes, you definitely should. This is a valid edge case that the core team can fix by adding
similar try/catch or non-native fallbacks in the main codebase.
You can report this bug directly from within the CLI by running the following command in your terminal:
1 /bug
This will guide you through submitting a report with the details of the crash and the fix we applied.
Client information
- CLI Version: 0.37.1
- Git Commit: 3b2d4f1
- Session ID: 24bccc82-dd3a-470d-9b0c-373d580e5e2d
- Operating System: win32 v20.20.2
- Sandbox Environment: no sandbox
- Model Version: auto-gemini-3
- Auth Type: oauth-personal
- Memory Usage: 205.9 MB
- Terminal Name: Unknown
- Terminal Background: #121212
- Kitty Keyboard Protocol: Unsupported
Login information
No response
Anything else we need to know?
every time i run gemini he is trying to upgrade itself and fails every time, i did some version juggling with nvm use 20.20.2 but the result still fails, maybe this worth more testing and fix
What happened?
gemini --yolo
in pwsh at 15:07:27
An unexpected critical error occurred:Error: EISDIR: illegal operation on a directory, realpath 'A:\a'
at async Module.realpath (node:internal/fs/promises:1176:10)
at async loadServerHierarchicalMemory (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/chunk-JS5WSGB2.js:51797:33)
at async loadCliConfig (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/gemini.js:7690:20)
at async main (file:///C:/Users/Greuceanu/AppData/Local/nvm/v20.20.2/node_modules/@google/gemini-cli/bundle/gemini.js:14455:25)
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
What did you expect to happen?
Start gemini cli
A:\ is a virtual drive mounted in windows, gemini failed to open, but it was ok in the past. He suggested some modifications try catch:
✦ I have successfully applied the local patch to fix the EISDIR crash and created a tracking log at C:\Users\Greuceanu\gemini-patch-log.md.
You can now use the Gemini CLI from A:\ or other virtual drives without it crashing during initialization.
Regarding reporting this to the developers: Yes, you definitely should. This is a valid edge case that the core team can fix by adding
similar try/catch or non-native fallbacks in the main codebase.
You can report this bug directly from within the CLI by running the following command in your terminal:
1 /bug
This will guide you through submitting a report with the details of the crash and the fix we applied.
Client information
Login information
No response
Anything else we need to know?
every time i run gemini he is trying to upgrade itself and fails every time, i did some version juggling with nvm use 20.20.2 but the result still fails, maybe this worth more testing and fix