Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.87.0
• OS Version: macOS 14.3.1 (23D60)

Steps to Reproduce:

1. Set "workbench.startupEditor": "terminal" in settings.json.
2. Open VSCode.
3. Use ⌘W to close the tab and then ⌘W to close the window.
4. Open VSCode again.

Expected outcome:

Opening new VScode windows with "workbench.startupEditor": "terminal" configured should always lead to a terminal in the editor area on startup.

Actual outcome:

Sometimes, the very first time you open VSCode, the terminal fails to open. Instead of a terminal you see an error message like

The editor could not be opened due to an unexpected error: Unable to resolve resource vscode-terminal:/1709154721587/1

Here's an example of that happening in a completely blank profile.

Other times, the terminal might open fine on the first try, but then fail on subsequent tries. Here's an example of that happening on my regular profile.

Interestingly, at 00:52 and 01:00 in that video, the terminal does succeed in opening, but fails to automatically receive focus, so no text cursor is visible until I click the mouse in there a moment later. IDK if that's relevant, feels like a detail worth highlighting just in case though!