Hi everyone,
I’m hoping someone in the community can help me with a persistent and frustrating issue I’ve been facing for a while now. I’m completely stuck and have run out of ideas.
What I’m trying to do
I am trying to create a new note in my vault. This happens with any method of note creation, including using the Ctrl+N
hotkey, clicking the ‘New note’ button in the file explorer, or using the command palette.
What’s happening
Every time I attempt to create a new note, I immediately get a pop-up error that says: Unable to Open ""
.
When I check the developer console, I see the following ENOENT
error repeating:
app.js:1 Error: ENOENT: no such file or directory, read
at async readFileHandle (node:internal/original-fs/promises:555:24)
(anonymous) @ app.js:1
What I’ve tried
I have tried several troubleshooting steps to isolate and fix the problem, with no lasting success:
- Restricted Mode: The problem persists even with Restricted Mode enabled, so it doesn’t seem to be caused by a community plugin.
- Templates: I use the Templates core plugin, but the error still occurs when I have a template configured and when I have it set to none.
- Deleting
workspace.json
: I have tried deleting theworkspace.json
file from my vault’s.obsidian
folder. - Clearing the Cache: I have completely cleared the cache by deleting the
Cache
,Code Cache
, andGPU Cache
folders from my Obsidian app data folder (%APPDATA%/Obsidian
).
Interestingly, clearing the cache folders and removing workspace.json
a few times fixed the problem for a few minutes in a new session, but it inevitably returns at some point.
My Environment
- OS: Windows 11
- Obsidian Version: Currently on v1.9.12, but this issue has been present across several previous versions.
- Vault Location: My vault is stored in a Google Drive folder to sync with the Obsidian mobile app. This setup has worked perfectly for years, and this issue only started recently. While I suspect the syncing service might be involved, I’m not sure why it would suddenly become a problem.
This issue seems similar to the one described in this older forum post, but the solutions there haven’t worked for me.
I’m at a loss for what to try next. Has anyone encountered this specific ENOENT
error when creating a new file? Any suggestions would be greatly appreciated.
Thanks in advance for your help!