Hello , Josef Mehursky
Welcome to Microsoft Q&A.
For someone like you — a seasoned cmd.exe user with over 20 years of experience — it’s entirely understandable how frustrating these issues must feel. You’re not complaining about trivial matters; you’re highlighting how changes to a core productivity tool can deeply impact experienced users.
In recent years, Microsoft has been undertaking significant modernization efforts under the hood to support newer applications such as Windows Terminal, which you mentioned. While the intentions behind these changes are good, the new logic has inadvertently broken certain classic and well-understood behaviors when interacting with legacy shells like cmd.exe.
Regarding your other frustrations, such as the inability to submit issues directly to Microsoft: this indeed severs an important feedback loop for professional users like you. You also mentioned your thoughts on Windows Terminal. If you’re interested in joining the discussion, I highly recommend submitting feedback here on GitHub, where many other users like yourself are actively engaged.
Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.
Additionally, the only official way to reach the Windows engineering team directly is via the Feedback Hub. Submitting high-quality feedback is critical, and I recommend the following steps:
How to Submit an Effective Feedback Report in Feedback Hub
- Open the “Feedback Hub” app on your Windows 11 system.
- Click “Report a Problem”.
- Create a detailed report encompassing all of the issues you’ve encountered. Be sure to write a clear and concise title.
- Provide as much context as you did here, describing the exact symptoms and behavior.
- Select the appropriate category:
- Developer Platform > Command-line
- Set the priority and choose the most accurate description for your issue.
- Record diagnostic data for each bug (this is the most important part):
- Go to “Recreate my problem”.
- Click “Start recording”.
- Reproduce each of the bugs you mentioned, pausing briefly between actions.
- Click “Stop recording” when you’re finished. This will capture a diagnostic package with a screen recording and detailed trace logs (ETL) that engineers can use to see exactly what’s going wrong.
- Attach your configuration screenshots, especially the three you already included in your original post.
- Submit your feedback.
- Reproduce each of the bugs you mentioned, pausing briefly between actions.
- Click “Start recording”.
- Go to “Recreate my problem”.
- Developer Platform > Command-line
After submission, you’ll receive a feedback link. While this doesn’t guarantee an immediate fix, it is the most effective way to get your issue directly to the right team, along with the evidence they need to reproduce and investigate the root cause.
Please consider posting this link in your original Microsoft Learn thread so that others encountering the same issue can upvote it, which increases its visibility and impact.
Thank you for taking the time to document and report these issues so thoroughly. Feedback from experienced professionals like yourself is invaluable in maintaining the quality of Windows’ core tools.
Again, thank you for your contribution to Microsoft Q&A — this is absolutely the right and most impactful path toward resolution.
Best wishes
Ami | Microsoft Q&A Support Specialist