Skip to content

Unable to launch VS Code terminal within UVFS #2310

@stop-sine

Description

@stop-sine

The problem:

Launching an integrated or external terminal from VS Code from within the UVFS causes VS Code to throw an exception.

To Reproduce:

  1. Launch VS Code from Mod Organizer 2
  2. Launch 'New Terminal' in VS Code

Environment:

  • Mod Organizer Version that exhibits the issue: 2.5.2
  • Last Mod Organizer Version that did not exhibit the issue (if applicable): N/A
  • Desktop OS/version used to run Mod Organizer: Windows 10, Windows 11 (24H1 and 24H2)

Details:

Image Image

An error is thrown regardless of whether VS Code is using ConPTY or WinPTY.

The Windows Terminal application likewise fails to launch within the UVFS entirely. PowerShell, when launched fully externally, functions from within the UVFS. However, it exhibits unusual behavior. For example, the display of print statements when running a Mutagen-based C# CLI application was delayed until code completion, rather than displaying on execution. If the application failed due to an exception, the statements did not print at all even though failure occurred subsequent in the application's execution.

Link to Mod Organizer logs:

USVFS:

Unable to create Gist due to GitHub server error

MO Interface:

Interface Log

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions