Can't uninstall Console Host #20998

Closed
opened 2026-01-31 07:30:05 +00:00 by claunia · 7 comments
Owner

Originally created by @skanda890 on GitHub (Dec 19, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22621.2861

Other Software

OS Build Version: 10.0.22621.2861.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.25

Steps to reproduce

Install Terminal.

Expected Behavior

It should uninstall Console Host or at least give the option to uninstall Console Host.

Actual Behavior

It didn't uninstall Console Host or at least give the option to uninstall Console Host.

Originally created by @skanda890 on GitHub (Dec 19, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.22621.2861 ### Other Software OS Build Version: 10.0.22621.2861.amd64fre.ni_release.220506-1250 .NET Version: .NET 6.0.25 ### Steps to reproduce Install Terminal. ### Expected Behavior It should uninstall Console Host or at least give the option to uninstall Console Host. ### Actual Behavior It didn't uninstall Console Host or at least give the option to uninstall Console Host.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:30:05 +00:00
Author
Owner

@237dmitry commented on GitHub (Dec 19, 2023):

It didn't uninstall Console Host or at least give the option to uninstall Console Host.

conhost.exe is the system console host and a part of Windows.

@237dmitry commented on GitHub (Dec 19, 2023): > It didn't uninstall Console Host or at least give the option to uninstall Console Host. conhost.exe is the system console host and a part of Windows.
Author
Owner

@skanda890 commented on GitHub (Dec 19, 2023):

But still, there should be a way to uninstall Console Host.

@skanda890 commented on GitHub (Dec 19, 2023): But still, there should be a way to uninstall Console Host.
Author
Owner

@DHowett commented on GitHub (Dec 19, 2023):

Even when Windows Terminal is installed and enabled as the default console host, conhost still provides API support for all of the Windows Console APIs to applications running in service desktops, in other window stations, over SSH, over Telnet, and over the EMS serial console. It also provides API services to applications in detached sessions or with "hidden" consoles.

We are not going to remove it.

Why would you like to see it removed?

@DHowett commented on GitHub (Dec 19, 2023): Even when Windows Terminal is installed and enabled as the default console host, `conhost` still provides API support for all of the Windows Console APIs to applications running in service desktops, in other window stations, over SSH, over Telnet, and over the EMS serial console. It also provides API services to applications in detached sessions or with "hidden" consoles. We are not going to remove it. Why would you like to see it removed?
Author
Owner

@237dmitry commented on GitHub (Dec 19, 2023):

But still, there should be a way to uninstall Console Host.

What about tasks which are out of user's space? Set WT as default terminal application and forget about standard console. Why does this app bother you so much? In my opinion it works pretty fine.

@237dmitry commented on GitHub (Dec 19, 2023): > But still, there should be a way to uninstall Console Host. What about tasks which are out of user's space? Set WT as default terminal application and forget about standard console. Why does this app bother you so much? In my opinion it works pretty fine.
Author
Owner

@skanda890 commented on GitHub (Dec 20, 2023):

But still, there should be a way to uninstall Console Host.

What about tasks which are out of user's space? Set WT as default terminal application and forget about standard console. Why does this app bother you so much? In my opinion it works pretty fine.

Because it is shown in this.

image

@skanda890 commented on GitHub (Dec 20, 2023): > > But still, there should be a way to uninstall Console Host. > > What about tasks which are out of user's space? Set WT as default terminal application and forget about standard console. Why does this app bother you so much? In my opinion it works pretty fine. Because it is shown in this. ![image](https://github.com/microsoft/terminal/assets/99239826/e0ed4aeb-0cfe-4091-9457-c16c7229ab27)
Author
Owner

@skanda890 commented on GitHub (Dec 20, 2023):

Even when Windows Terminal is installed and enabled as the default console host, conhost still provides API support for all of the Windows Console APIs to applications running in service desktops, in other window stations, over SSH, over Telnet, and over the EMS serial console. It also provides API services to applications in detached sessions or with "hidden" consoles.

We are not going to remove it.

Why would you like to see it removed?

Because of that ( from a normal user ), it won't be used except as a terminal.

@skanda890 commented on GitHub (Dec 20, 2023): > Even when Windows Terminal is installed and enabled as the default console host, `conhost` still provides API support for all of the Windows Console APIs to applications running in service desktops, in other window stations, over SSH, over Telnet, and over the EMS serial console. It also provides API services to applications in detached sessions or with "hidden" consoles. > > We are not going to remove it. > > Why would you like to see it removed? Because of that ( from a normal user ), it won't be used except as a terminal.
Author
Owner

@DHowett commented on GitHub (Dec 20, 2023):

Thanks for the input!

We won't be doing this. Sorry!

@DHowett commented on GitHub (Dec 20, 2023): Thanks for the input! We won't be doing this. Sorry!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20998