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 still run in background even I turned it off #17037

New Issue
Closed
opened 2026-01-31 05:30:29 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 05:30:29 +00:00
Owner
Copy Link

Originally created by @hungpham3112 on GitHub (Mar 18, 2022).

Windows Terminal version

1.12.220208003-release1.12

Windows build number

10.0.22000.556

Other Software

I installed windows-terminal with scoop

Steps to reproduce

  1. scoop bucket add extras
  2. scoop install windows-terminal
  3. open wt in terminal
  4. turn off wt
  5. scoop uninstall windows-terminal and see error

Expected Behavior

It can uninstall like normal.

Actual Behavior

In screen record below, I have only 3 tabs and none of them are windows-terminal. I closed it but still can't uninstall, there's still something running in background. I opened an issue in scoop repo https://github.com/ScoopInstaller/Scoop/issues/4701

bandicam 2022-03-18 21-53-19-630

Originally created by @hungpham3112 on GitHub (Mar 18, 2022). ### Windows Terminal version 1.12.220208003-release1.12 ### Windows build number 10.0.22000.556 ### Other Software I installed windows-terminal with scoop ### Steps to reproduce 1. scoop bucket add extras 2. scoop install windows-terminal 3. open wt in terminal 4. turn off wt 5. scoop uninstall windows-terminal and see error ### Expected Behavior It can uninstall like normal. ### Actual Behavior In screen record below, I have only 3 tabs and none of them are windows-terminal. I closed it but still can't uninstall, there's still something running in background. I opened an issue in scoop repo https://github.com/ScoopInstaller/Scoop/issues/4701 ![bandicam 2022-03-18 21-53-19-630](https://user-images.githubusercontent.com/75968004/159027289-145177ec-d073-459a-ad88-aff214402a99.gif)
claunia commented 2026-01-31 05:30:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 18, 2022):

Did you set up the Terminal as your Default Terminal application? It's possible that there's a leftover RuntimeBroker hanging around keeping the Terminal process alive, even after the window exited.

You might be able to find that process with

tasklist /FI "IMAGENAME eq WindowsTerminal.exe"

And then Task Manager should show the a RuntimeBroker.exe associated with it. (if my theory is correct).

I don't believe that the remoting code's COM registration should leave the RuntimeBroker around after we exit, but that might be another place for me to look.

@zadjii-msft commented on GitHub (Mar 18, 2022): Did you set up the Terminal as your Default Terminal application? It's possible that there's a leftover RuntimeBroker hanging around keeping the Terminal process alive, even after the window exited. You might be able to find that process with ``` tasklist /FI "IMAGENAME eq WindowsTerminal.exe" ``` And then Task Manager should show the a RuntimeBroker.exe associated with it. (if my theory is correct). I don't believe that the remoting code's COM registration should leave the RuntimeBroker around after we exit, but that might be another place for me to look.
claunia commented 2026-01-31 05:30:30 +00:00
Author
Owner
Copy Link

@hungpham3112 commented on GitHub (Mar 18, 2022):

Did you set up the Terminal as your Default Terminal application? It's possible that there's a leftover RuntimeBroker hanging around keeping the Terminal process alive, even after the window exited.

You might be able to find that process with

tasklist /FI "IMAGENAME eq WindowsTerminal.exe"

And then Task Manager should show the a RuntimeBroker.exe associated with it. (if my theory is correct).

I don't believe that the remoting code's COM registration should leave the RuntimeBroker around after we exit, but that might be another place for me to look.

For some reasons, I don't want to set up the Terminal as Default.

Here is output of tasklist /FI "IMAGENAME eq WindowsTerminal.exe":

image

I didn't see the app named RuntimeBroker.exe.

@hungpham3112 commented on GitHub (Mar 18, 2022): > Did you set up the Terminal as your Default Terminal application? It's possible that there's a leftover RuntimeBroker hanging around keeping the Terminal process alive, even after the window exited. > > You might be able to find that process with > > ``` > tasklist /FI "IMAGENAME eq WindowsTerminal.exe" > ``` > > And then Task Manager should show the a RuntimeBroker.exe associated with it. (if my theory is correct). > > I don't believe that the remoting code's COM registration should leave the RuntimeBroker around after we exit, but that might be another place for me to look. For some reasons, I don't want to set up the Terminal as Default. Here is output of `tasklist /FI "IMAGENAME eq WindowsTerminal.exe"`: ![image](https://user-images.githubusercontent.com/75968004/159097420-c41324cd-d016-4fcd-9720-a3e505926791.png) I didn't see the app named RuntimeBroker.exe.
claunia commented 2026-01-31 05:30:30 +00:00
Author
Owner
Copy Link

@hungpham3112 commented on GitHub (Apr 21, 2022):

How do I solve this problem without delete instances of RuntimeBroker.exe everytime? Maybe you can force it close regardless I set Windows Terminal as default or not.

I tried to delete RuntimeBroker.exe but it didn't work.

https://user-images.githubusercontent.com/75968004/164467481-be2dc6e1-8761-4b13-9d8e-390d73e49f69.mp4

@hungpham3112 commented on GitHub (Apr 21, 2022): How do I solve this problem without delete instances of RuntimeBroker.exe everytime? Maybe you can force it close regardless I set Windows Terminal as default or not. I tried to delete RuntimeBroker.exe but it didn't work. https://user-images.githubusercontent.com/75968004/164467481-be2dc6e1-8761-4b13-9d8e-390d73e49f69.mp4
claunia commented 2026-01-31 05:30:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 5, 2022):

Hey sorry for the late reply, stuff gets lost in the triage queue.

I'm not sure there's a better way to kill off RuntimBroker instances, if that indeed is the process hanging around. Could be something else too - try double checking in Task Manager (sort by name) if there's a Terminal entry, and check if there's anything else the OS thinks is running in the Terminal package.

RuntimeBroker is supposed to clean itself up after a few seconds to minutes though...

This might just be an ask on scoop. There's definitely ways to force update packages even if they're in use (hell, the Store does it all the time 😅 )

@zadjii-msft commented on GitHub (Dec 5, 2022): Hey sorry for the late reply, stuff gets lost in the triage queue. I'm not sure there's a better way to kill off RuntimBroker instances, if that indeed is the process hanging around. Could be something else too - try double checking in Task Manager (sort by name) if there's a Terminal entry, and check if there's anything else the OS thinks is running in the Terminal package. RuntimeBroker is supposed to clean itself up after a few seconds to minutes though... This might just be an ask on `scoop`. There's definitely ways to force update packages even if they're in use (hell, the Store does it all the time 😅 )
claunia commented 2026-01-31 05:30:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 9, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 9, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:30:31 +00:00
Author
Owner
Copy Link

@hungpham3112 commented on GitHub (Dec 10, 2022):

Thanks for your information, I will take a look at this issue and give you feedback in near future, right now I'm quite busy at work. Just let it opened. Thank you.

@hungpham3112 commented on GitHub (Dec 10, 2022): Thanks for your information, I will take a look at this issue and give you feedback in near future, right now I'm quite busy at work. Just let it opened. Thank you.
claunia commented 2026-01-31 05:30:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 7, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 7, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Issue-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#17037
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?