Fine. Only in this software, it never happens when start others.
The process is not ended, after start command, or there will be a path PS C:\Users\ycbrd\AppData\Local\Obsidian>
on the red line. But the Ob window is actually successfully opened. (and crash when cmd is closed)
Please at least explain what the software is doing in this start process. Start is just start, no need to check for updates simultaneously.
YES! I have the same issue and can’t find an answer anywhere. I’m trying to add Obsidian to my “Open/Close Work Apps” scripts, but no matter what I do, the command prompt has to stay open for Obsidian. No other app behaves this way.
Using either start obisidian://open?vault=MyVaultName or start "full-path-to-obsidian.exe" gives this output, and occassionally I see the same passthrough message as OP.
Whoops, that was just a typo in my post . I’ve definitely been typing it correctly in the command prompt.
My Obsidian instance opens and renders normally unlike OP, but I have the exact same issue where typing start obsidian in cmd requires the command prompt to stay open. In the dozen or so apps I’ve tested, Obsidian is the only one that behaves this way.
Even if I open the exe via cmd /C "C:\Users\<username>\AppData\Local\Obsidian\Obsidian.exe" in my .bat file, it still force closes Obsidian if I close the command prompt after.
As I’m on Mac, I’m not able to verify this, but a google search on the topic seems to indicate it’s related to not having a title on the window, strangely enough, so could you please try the following and report back?