Thank you. But it does not solve the issue. The custom URI concept is too complex and alien in the Windows world.

A Windows user would much better prefer to have a special anchor file in Obsidian vault folder that could be double-clicked and treated by the standard and observable means.

This is why .txt files are so popular. A double-click and they work. The specialized tools may be 100 times better, but they often miss one important detail: frictionless entry. If something causes friction, especially at the start, then it gradually becomes a burden a user doesn't want to deal with.

However, you advice solves the issue for me because I'm a technical user and you have kindly presented the information. But just imagine how many of those who would totally miss that.

I tried using the URI-scheme and vault-parameter some time ago on linux, to open specific vaults via script. Surprisingly, this did not worked at all. Even worse, the whole scripting of obsidian is horrible even on the fundamental levels, and it failed on pretty much any normal job. Though, this is not such a surprise, considering that it's complete foreign to linux any kind of integration. At the end, it's a closed space, not like an editor, open to the rest of the system.