terminal: Terminal shows an empty window and then crashes

I got this issue and after uncheck Use legacy console option, my terminal show up

I think the Terminal was so impressed with your desktop image it didn’t want to render on top of it.

Ok…
I think I found out why this is happening… 🤔

A couple of minutes ago I tried to run again the Terminal on my PC to log any errors to attach here…
Well… It runs (and it’s great)! 🤩

«So? Why now runs? What’s the difference?»

Today I was using my notebook on my legs (without any devices connected).
Usually, I use my notebook connected to this Universal Dock.

These kind of devices (DisplayLink docks) are seen by the OS as external video cards without extended support for hardware acceleration…
In facts, you can’t run video games or 3D graphics in general even if your GPU is the best one you can buy!

So, I think, if the video card you’re trying to render the Terminal on isn’t compatible with hardware acceleration (or something like that) it, simply, crashes badly.

It could be also your case @ShadowEO, @magiblot and @tanayagar?
Maybe something like:

• Cheap hardware?
• Integrated video cards?
• Virtual machines?
• … and so on?

I’ve submitted an issue using the Feedback Hub - https://aka.ms/AA5jk66

Even though I have Windows Terminal (Preview) listed in Settings | Apps, it didn’t come up in the list of Apps in the Feedback Hub, so I just had to choose “All other apps”.

I also created a crash dump (applying the same settings as documented here for WindowsTerminal.exe) and attached that to the report.

I got this issue and after uncheck Use legacy console option, my terminal show up

This is probably different. I forked it to another issue.

@miniksa Michael Niksa FTE Certainly! How can I go about getting a crash dump of it from the affected machine?

I also went to my development station (x64) and attempted the UseDx change you requested. I can confirm that conhost fails to start with UseDx set to 0x1 on a machine where the same source build does work properly. Toggling UseDx back off results in a working console again.

Interestingly, I did this test on the affected tablet (once again with same sources), and conhost works in both scenarios on it, I get a command prompt as normal… however Cascadia still fails.

You can technically right click a process in the Details page of Task Manager and create a dump and attach it somewhere online, but be warned, it may contain personally identifiable information as it dumps the entire memory space.

You can also try using the Feedback Hub and choosing the Windows Terminal app and submitting that way.

Or if it crashes, you can try getting the Windows Error Reporting information from the event viewer and give me all of that so I can try to look up the IDs with the WER service.

Thanks for the tip. May I ask you how you did that ?

I opened the NVIDIA Control Panel, under Manage 3D Settings select the Program Settings tab. At step one, the Windows Terminal is listed as “microsoft.windowsterminal_[id]”. At step two I selected the integrated graphics (sorry for the poor drawing skills 😃):