Hey @pshev, I can’t seem to replicate this behaviour with neither \\wsl.localhost\ nor \\wsl$\ with the latest Obsidian installed on Windows 11 + WSL2. Attached a screenshot of the error observed:
An error occurred while loading Obsidian. Error: EISDIR: illegal operation on a directory, watch '\\wsl$\Ubuntu\home\
Despite this, the following boilerplate files are created within a nested “.obsidian” directory of the WSL2 path, just as @pcbowers mentioned:
.obsidian
├── app.json
├── appearance.json
├── core-plugins-migration.json
├── core-plugins.json
└── hotkeys.json
To echo @mgamble, an approach like VS Code would be most appreciated for seamless integration of Obsidian across filesystems, regardless of the host.