Issues like these can be a pain to identify where the culprit is, so sorry for the rather slow process. So far we’ve established that:
- The same vault functions on another computer
- The actual installation of Obsidian seems to work
- The issue persist with different installation packages of Obsidian, which also should have ruled out any issues with installer vs obsidian version
- Changing the basic configuration on workspaces doesn’t do anything
- And I’ll add that different hardware shouldn’t affect anything, especially when the problematic issue is on the more powerful computer, as you put it
What can then cause this kind of an issue:
- The vault is in fact not the same, only very close or started from the file set
- The plugins are somehow interfering, and maybe some of them are not updated properly and as such participate into the issue
- The backing database (and/or local computer configuration) is somehow corrupted
Verify vault likeness
Are you able to compare the problematic and the working vault on a file by file basis? Like zipping up the problematic one, copy it to the working computer, and do a file-by-file comparison? (Make sure to also include the .obsidian files and structure below ).
And along the same lines of reckoning, could you do the reverse copy, and try to open that on the problematic computer? Maybe that would solve the issue directly?
This could possibly identify/rectify the two first likely candidates.
Troubles with the indexdb
I’ve not done this, so proceed with caution, and this could possibly also affect the cache/indexes of any other vaults you’ve got on that computer, but you could consider doing some of the suggestions from this thread:
As you can see, this will likely require you to reconnect to any sync tools, and reenable community plugins, so it could possibly be wise to make sure you’ve got that copy of the configuration/vault from the other computer readily available.