starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows terminal does not show missing dll popup #13413

New Issue
Closed
opened 2026-01-31 03:42:03 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 03:42:03 +00:00
Owner
Copy Link

Originally created by @codec-abc on GitHub (Apr 12, 2021).

Windows Terminal version (or Windows build number)

1.6.10571.0

Other Software

No response

Steps to reproduce

When opening a program that lack a dll from Windows Terminal, the usual popup that reveal the problem is not shown. For example, today I wanted to test the 0.3 version of Mun. To do this, I downloaded the release, extracted it somewhere and launched Windows Terminal into the extracted directory. Then running commands, nothing particular happened giving me the impression the program ran fine but without doing anything. You can find the Mun issue I opened here about this. The thing is that I don't have the Visual Studio 2019 runtime installed. While this is a Mun distribution issue, the problem is not reported with Windows Terminal while it is with other terminals.

Expected Behavior

The expected behavior would be the the one when using cmd.exe or Cmder where a popup appear revealing the underlying issue. See screenshot below for their respective behavior.

image

image

Actual Behavior

In the tested version, no popup appear which make finding the underlying problem harder.

image

Originally created by @codec-abc on GitHub (Apr 12, 2021). ### Windows Terminal version (or Windows build number) 1.6.10571.0 ### Other Software _No response_ ### Steps to reproduce When opening a program that lack a dll from Windows Terminal, the usual popup that reveal the problem is not shown. For example, today I wanted to test the 0.3 version of [Mun](https://github.com/mun-lang/mun). To do this, I downloaded the release, extracted it somewhere and launched Windows Terminal into the extracted directory. Then running commands, nothing particular happened giving me the impression the program ran fine but without doing anything. You can find the Mun issue I opened [here](https://github.com/mun-lang/mun/issues/322) about this. The thing is that I don't have the Visual Studio 2019 runtime installed. While this is a Mun distribution issue, the problem is not reported with Windows Terminal while it is with other terminals. ### Expected Behavior The expected behavior would be the the one when using ``cmd.exe`` or Cmder where a popup appear revealing the underlying issue. See screenshot below for their respective behavior. ![image](https://user-images.githubusercontent.com/1208646/114420330-843de700-9bb4-11eb-9df1-da20990023e4.png) ![image](https://user-images.githubusercontent.com/1208646/114420397-93bd3000-9bb4-11eb-97bd-65047cb0d1f6.png) ### Actual Behavior In the tested version, no popup appear which make finding the underlying problem harder. ![image](https://user-images.githubusercontent.com/1208646/114420851-fe6e6b80-9bb4-11eb-8a04-1f50e8401746.png)
claunia added the Resolution-Duplicate label 2026-01-31 03:42:03 +00:00
claunia commented 2026-01-31 03:42:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 12, 2021):

Curious. The only difference between a standard console host and Terminal is that there is no console window handle.

@DHowett commented on GitHub (Apr 12, 2021): Curious. The only difference between a standard console host and Terminal is that there is no console window handle.
claunia commented 2026-01-31 03:42:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 12, 2021):

Does the popup appear, but somewhere else in the z-order? Like, is the popup still in the alt-tab list of windows somewhere?

@zadjii-msft commented on GitHub (Apr 12, 2021): Does the popup appear, but somewhere else in the z-order? Like, is the popup still in the alt-tab list of windows somewhere?
claunia commented 2026-01-31 03:42:05 +00:00
Author
Owner
Copy Link

@codec-abc commented on GitHub (Apr 12, 2021):

@zadjii-msft : No popup nor the error sound. Same thing goes for Powershell (though I am not sure how to run a program with Powershell). Funny fact, git bash terminal does not have the popup nor the sound alert but report the problem as text.

image

@codec-abc commented on GitHub (Apr 12, 2021): @zadjii-msft : No popup nor the error sound. Same thing goes for Powershell (though I am not sure how to run a program with Powershell). Funny fact, git bash terminal does not have the popup nor the sound alert but report the problem as text. ![image](https://user-images.githubusercontent.com/1208646/114422947-016a5b80-9bb7-11eb-983c-395d95b60fe5.png)
claunia commented 2026-01-31 03:42:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 12, 2021):

I wonder if cmd.exe is calling GetConsoleWindow to pop that messagebox on top of conhost 😨

@zadjii-msft commented on GitHub (Apr 12, 2021): I wonder if cmd.exe is calling [`GetConsoleWindow`](https://docs.microsoft.com/en-us/windows/console/getconsolewindow) to pop that messagebox on top of conhost 😨
claunia commented 2026-01-31 03:42:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 12, 2021):

It's not. This error message seems to be generated via NtRaiseHardError which is handled by csrss (as far as I can tell...)

@DHowett commented on GitHub (Apr 12, 2021): It's not. This error message seems to be generated via `NtRaiseHardError` which is handled by _csrss_ (as far as I can tell...)
claunia commented 2026-01-31 03:42:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 13, 2021):

I'm going to close this one as a /dup of #2988 -- I think us not having a real window on-screen prevents the dialog from being displayed.

Thanks!

@DHowett commented on GitHub (Apr 13, 2021): I'm going to close this one as a /dup of #2988 -- I think us not having a real window on-screen prevents the dialog from being displayed. Thanks!
claunia commented 2026-01-31 03:42:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 13, 2021):

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 (Apr 13, 2021): 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!
claunia commented 2026-01-31 03:42:06 +00:00
Author
Owner
Copy Link

@codec-abc commented on GitHub (Apr 13, 2021):

This is might be true only if you want to display a dialog. But if going the git bash way could be enough to fix this in my opinion. Arguably it could be even better because popup are kind of annoying in this case and the git bash error message is clearer (the issue might be poorly named since the complain is more about the lack of feedback about missing dll rather than the popup itself)

Also is it sure that it is linked to some real windows on-screen issue? Since the behavior nor the error message is not the same between git bash and other there might be something else than the windowing issue.

@codec-abc commented on GitHub (Apr 13, 2021): This is might be true only if you want to display a dialog. But if going the git bash way could be enough to fix this in my opinion. Arguably it could be even better because popup are kind of annoying in this case and the git bash error message is clearer (the issue might be poorly named since the complain is more about the lack of feedback about missing dll rather than the popup itself) Also is it sure that it is linked to some real windows on-screen issue? Since the behavior nor the error message is not the same between git bash and other there might be something else than the windowing issue.
claunia commented 2026-01-31 03:42:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2021):

Clearly, git bash and cmd.exe are deciding to display the error in different ways. We can't modify the way cmd.exe works unfortunately. Since the behavior in cmd.exe seems to be linked to the missing console HWND, that's the best we can do for bringing that dialog back.

@zadjii-msft commented on GitHub (Apr 13, 2021): Clearly, git bash and cmd.exe are deciding to display the error in different ways. We can't modify the way cmd.exe works unfortunately. Since the behavior in cmd.exe seems to be linked to the missing console HWND, that's the best we can do for bringing that dialog back.
claunia commented 2026-01-31 03:42:06 +00:00
Author
Owner
Copy Link

@codec-abc commented on GitHub (Apr 13, 2021):

So you are saying there is no easy workaround for this? My guess is that #2988 is rather hard to fix and might not be fixed soon. So being pragmatic here, if somehow there is an easy way to catch this error it might be worth trying to print a message (dunno Windows internal but there might be a way to catch the NtRaiseHardError event) . Otherwise if it is as hard (or even harder) it makes sense to close this and wait for the resolution of 2988. What's your opinion on this?

@codec-abc commented on GitHub (Apr 13, 2021): So you are saying there is no easy workaround for this? My guess is that #2988 is rather hard to fix and might not be fixed soon. So being pragmatic here, if somehow there is an easy way to catch this error it might be worth trying to print a message (dunno Windows internal but there might be a way to catch the ``NtRaiseHardError`` event) . Otherwise if it is as hard (or even harder) it makes sense to close this and wait for the resolution of 2988. What's your opinion on this?
claunia commented 2026-01-31 03:42:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 14, 2021):

  • Yes, there's no easy workaround for this
  • #2988 is going to be hard to do right. There's no good plan for that one, but a lot of bad plans.
  • It would be even harder to fix cmd.exe. I'd rather wait for heat death of the universe than touch cmd.exe.

Given the above, we're gonna leave this closed as a duplicate of #2988 and hope that's figured out

@zadjii-msft commented on GitHub (Apr 14, 2021): * Yes, there's no easy workaround for this * #2988 is going to be hard to do right. There's no good plan for that one, but a lot of _bad_ plans. * It would be even _harder_ to fix cmd.exe. I'd rather wait for heat death of the universe than touch cmd.exe. Given the above, we're gonna leave this closed as a duplicate of #2988 and hope that's figured out
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13413
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?