Disabling legacy console mode does not show any text on cmd console #6647

Closed
opened 2026-01-31 00:43:49 +00:00 by claunia · 3 comments
Owner

Originally created by @varshavjm on GitHub (Feb 27, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]

Platform ServicePack Version      VersionString                    
-------- ----------- -------      -------------                    
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):
Microsoft Windows [Version 10.0.18363.657]

Any other software?

N/A

Steps to reproduce

  1. Open cmd -> right click on top -> properties -> Options -> Check "use Legacy console" -> select OK.
  2. After a few minutes for a new session, right click on top-> properties -> Options -> Uncheck "use Legacy console" -> select OK.
  3. Close and open new window.
  4. The new window does not show any text.
  5. Try typing in the window.
  6. Switch back to legacy mode as per step 1.

Expected behavior

For step 4,5 no text shows up even after changing the font color, restarting a bunch of times.

Actual behavior

Typed text and current directory should show up in the console window.

Originally created by @varshavjm on GitHub (Feb 27, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Microsoft Windows [Version 10.0.18363.657] Any other software? ``` N/A # Steps to reproduce 1. Open cmd -> right click on top -> properties -> Options -> Check "use Legacy console" -> select OK. 2. After a few minutes for a new session, right click on top-> properties -> Options -> Uncheck "use Legacy console" -> select OK. 3. Close and open new window. 4. The new window does not show any text. 5. Try typing in the window. 6. Switch back to legacy mode as per step 1. # Expected behavior For step 4,5 no text shows up even after changing the font color, restarting a bunch of times. # Actual behavior Typed text and current directory should show up in the console window. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 00:43:49 +00:00
Author
Owner

@varshavjm commented on GitHub (Feb 27, 2020):

Hi,

I wanted to disable non-legacy mode of the command prompt so I unchecked the Legacy mode option. After reopening cmd window I cannot see what I typed. Also did a bunch of font color changes, but nothing shows up still. Then switching back to Legacy mode and reopening a cmd tab makes the newly typed content visible.

@varshavjm commented on GitHub (Feb 27, 2020): Hi, I wanted to disable non-legacy mode of the command prompt so I unchecked the Legacy mode option. After reopening cmd window I cannot see what I typed. Also did a bunch of font color changes, but nothing shows up still. Then switching back to Legacy mode and reopening a cmd tab makes the newly typed content visible.
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 27, 2020):

Explanation and workarounds in /dup #2319.

@DHowett-MSFT commented on GitHub (Feb 27, 2020): Explanation and workarounds in /dup #2319.
Author
Owner

@ghost commented on GitHub (Feb 27, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 27, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6647