Obsidian: Active vault is closed unexpectedly. Vault Manager is opened

Bug reports
1

Hi Team,

We are facing issues with the Obsidian application where it intermittently closes the active vault and returns to the “Open Vault” screen without any error message, indicating a possible silent crash and restart.

Restarting the machine has not resolved the issue. We also upgraded to the latest version (1.12.7), but the problem persists across both older and newer versions.

Could you please help investigate this and let us know if any additional logs or diagnostics are needed from our end?

Thanks,
Pranitha

2

Hi, I’ve moved this to Help for now. Can you please complete the bug report template?

At least if you please share your “Show debug info” from the command inside Obsidian. And share any details like if you’re storing your vault in a cloud tool or NAS, etc.

3

Hi, could you let me know the process to retrieve the bug report from Obsidian?

4

Hello @pranithaevana

What is the output of “show debug info” command?

5

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.12.7
Operating system: Windows 11 Enterprise 10.0.26200
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

6

And what about this?

And was it working well before, or is this the first time you are trying Obsidian?

7

I’m from the Systems team, and users have been using Obsidian for some time. They first encountered this issue in v1.8.9, and the same behavior persists after upgrading to v1.12.7. I also checked the vault location, and it is stored on the H: drive, which is a mapped network drive rather than a local drive.

8

Hi, following up to see if you had a chance to check the above?

9

Hello,

I haven’t been able to pinpoint the exact problem and I am not sure version 1.8.9 has anything to do with this.

My current working hypothesis is that the network share becomes (temporarily) unavailable and Obsidian closes the vault.

10

The vault is on my H: drive, which is home drive mapped at login rather than a removable or local path, so I would not normally expect it to become unavailable during use. Is there a way to verify from Obsidian logs or Windows logs whether the H: drive actually became unavailable at the time the vault closed?”

11

The remote server (where the drive) is can disconnect, or the connection itself can have problems (for example if it is WiFi)

I don’t think there’s any log within the app about this. We will consider adding a notification in the future if we detect such event.

You can perhaps take a look at windows own logs (under event viewer).