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

Can't disable startup #22794

New Issue
Closed
opened 2026-01-31 08:23:41 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:23:41 +00:00
Owner
Copy Link

Originally created by @neonvoidx on GitHub (Jan 23, 2025).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.26100.0

Other Software

Docker (disabled on startup, does not launch)
AthenaOS WSL

Steps to reproduce

  1. Install WSL (any distro, currently using AthenaOS WSL)
  2. Install Windows Terminal
  3. Install Docker Desktop
  4. Disable docker on startup
  5. Disable Launch on Machine startup in Windows Terminal settings
    Image
  6. Check shell:startup
    Image
  7. Check shell:Common Startup
    Image
  8. Check task manager startup apps
    Image
  9. Check Windows Settings App -> Apps -> Startup (NOTICE HERE, Terminal is checked on and greyed out so it can't be disabled??)
    Image
  10. On Fresh windows start, terminal auto opens and launches WSL

Things I have tried to alleviate:

  1. I have disabled WSL, which still causes Terminal to launch at startup, but will just launch with a WSL error because WSL is not running
  2. I have turned off showing recent files in explorer
  3. I have ensured Linux subsystem folders are not expanded or manually pinned to quick start
  4. Ensured docker desktop with WSL support does not run at startup
  5. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal

Expected Behavior

I expect Windows Terminal to not autostart when computer starts, I also expect to be able to disable Windows Terminal from Settings App -> Apps -> Startup, currently it is enabled and greyed out with no way to disable it.

Actual Behavior

Windows terminal launches at startup everytime.

Originally created by @neonvoidx on GitHub (Jan 23, 2025). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.26100.0 ### Other Software Docker (disabled on startup, does not launch) AthenaOS WSL ### Steps to reproduce 1. Install WSL (any distro, currently using AthenaOS WSL) 2. Install Windows Terminal 3. Install Docker Desktop 4. Disable docker on startup 5. Disable Launch on Machine startup in Windows Terminal settings ![Image](https://github.com/user-attachments/assets/ad149f3c-6184-403a-b7c2-e0418a81931f) 7. Check `shell:startup` ![Image](https://github.com/user-attachments/assets/5a08cd1a-c5d1-4d01-a241-90a89295b5c9) 8. Check `shell:Common Startup` ![Image](https://github.com/user-attachments/assets/1dd7ffb1-0aca-4dec-ad5f-cb72e9a63110) 9. Check task manager startup apps ![Image](https://github.com/user-attachments/assets/1dbbbcde-1557-4bd4-8541-78710f5f0842) 10. Check Windows Settings App -> Apps -> Startup (NOTICE HERE, Terminal is checked on and greyed out so it can't be disabled??) ![Image](https://github.com/user-attachments/assets/12235cc5-0a02-47d8-b026-2ac2045830ee) 11. On Fresh windows start, terminal auto opens and launches WSL Things I have tried to alleviate: 1. I have disabled WSL, which still causes Terminal to launch at startup, but will just launch with a WSL error because WSL is not running 2. I have turned off showing recent files in explorer 3. I have ensured Linux subsystem folders are not expanded or manually pinned to quick start 4. Ensured docker desktop with WSL support does not run at startup 5. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal ### Expected Behavior I expect Windows Terminal to not autostart when computer starts, I also expect to be able to disable Windows Terminal from Settings App -> Apps -> Startup, currently it is enabled and greyed out with no way to disable it. ### Actual Behavior Windows terminal launches at startup everytime.
claunia added the Needs-TriageResolution-Fix-CommittedIssue-Bug labels 2026-01-31 08:23:41 +00:00
claunia commented 2026-01-31 08:23:43 +00:00
Author
Owner
Copy Link

@neonvoidx commented on GitHub (Jan 23, 2025):

To note from above, this will fix the issue:

  1. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal

Although I don't understand why this is necessary

@neonvoidx commented on GitHub (Jan 23, 2025): To note from above, this will fix the issue: 5. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal Although I don't understand why this is necessary
claunia commented 2026-01-31 08:23:43 +00:00
Author
Owner
Copy Link

@WhatsACloud commented on GitHub (Feb 1, 2025):

Hmm that seems very odd. I followed the replication steps but I couldn't reproduce the bug. I suspect there might be something else at play. Could you answer the following questions so I can diagnose this issue further?

  1. Have you tried uninstalling and reinstalling Windows Terminal to see if the bug still occurs? (a bit simplistic, but it might work. If you have loads of settings tweaked, I believe you can export it by saving the settings.json somewhere.)
  2. when did this bug start occurring? Right after downloading it, or did it randomly start one morning?
@WhatsACloud commented on GitHub (Feb 1, 2025): Hmm that seems very odd. I followed the replication steps but I couldn't reproduce the bug. I suspect there might be something else at play. Could you answer the following questions so I can diagnose this issue further? 1. Have you tried uninstalling and reinstalling Windows Terminal to see if the bug still occurs? (a bit simplistic, but it might work. If you have loads of settings tweaked, I believe you can export it by saving the settings.json somewhere.) 2. when did this bug start occurring? Right after downloading it, or did it randomly start one morning?
claunia commented 2026-01-31 08:23:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 26, 2025):

@DHowett sanity check, this was fixed by #18530?

@zadjii-msft commented on GitHub (Mar 26, 2025): @DHowett sanity check, this was fixed by #18530?
claunia commented 2026-01-31 08:23:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 26, 2025):

Yep! Missed this one somehow, sorry!

@DHowett commented on GitHub (Mar 26, 2025): Yep! Missed this one somehow, sorry!
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-Triage Resolution-Fix-Committed
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#22794
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?