Skip to content

Author a KB article documenting DxD and how to disable it #13787

Open
@DHowett

Description

@DHowett

When DxD hits broadly, it will be good for us to have some official Microsoft documentation on (1) what happened, (2) the anticipated risk to applications and (3) how to revert to a known-good state. Enterprises can fall back on this documentation, and we can point users to it.

Why a KB article, instead of Terminal Docs?

We should do both, but a KB article is more "official." They're not user-editable, and they document "best practice" and compatibility risks and things like that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-DocsIt's a documentation issue that really should be on MicrosoftDocs/Console-DocsNeeds-Tag-FixDoesn't match tag requirementsPriority-1A description (P1)Product-ConhostFor issues in the Console codebaseProduct-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions