Launch failure using DOS command "START"

Steps to reproduce

  1. type start C:\Users\ycbrd\AppData\Local\Obsidian\Obsidian.exe and Enter in cmd.exe (ycbrd is my user name)
  2. close cmd.exe
  3. Obsidian window went blank

Expected result

Close cmd window and use Obsidian.

Actual result

As above.


  • Operating system: Windows 11 22H2 22621.755
  • Debug info:
    Obsidian version: v1.0.0
    Installer version: v0.15.9
    Operating system: Windows 10 Home 10.0.22621
    Login status: logged in
    Catalyst license: none
    Insider build toggle: off
    Live preview: on
    Legacy editor: off
    Base theme: dark
    Community theme: Blue Topaz
    Snippets enabled: 0
    Restricted mode: off
    Plugins installed: 23
    Plugins enabled: 21
    1: Auto pair chinese symbol v0.9.5
    2: Contextual Typography v2.2.4
    3: Copy Block Link v1.0.4
    4: Find and replace in selection v1.0.1
    5: Footnote Shortcut v0.0.9
    6: Mind Map v1.1.0
    7: Number Headings v1.10.0
    8: Obsidian Enhancing Export v1.1.7
    9: obsidian markmind v1.6.1
    10: Obsius Publish v1.0.0
    11: Outliner v4.1.0
    12: Recent Files v1.3.3
    13: Remember cursor position v1.0.7
    14: Sidebar Expand on Hover v1.0.1
    15: Style Settings v0.4.12
    16: Better footnote v1.0.1
    17: Zoom v1.1.0
    18: Better Word Count v0.8.1
    19: Drag-n-Drop for blocks v1.2.0
    20: Hover Editor v0.11.6
    21: Various Complements v7.2.4

I don’t consider this a bug. moved to help

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.

self reply to avoid from being closed

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.


Not sure on the first one as I’m on Mac, but regarding @Tousuto issue, you’ve written obisidan, not obsidian. That could be your culprit.

Whoops, that was just a typo in my post :sweat_smile:. 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?

start "" "C:\Users\ycbrd\AppData\Local\Obsidian\Obsidian.exe"

And yes, it seems vital to have that first pair of "" in there.

Hope this helps,

Thanks a lot for your kind help and sorry for late reply. I tried your code but it works like:
Close cmd will close Obsidian.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.