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

Starting terminal on boot not configurable. #14567

New Issue
Closed
opened 2026-01-31 04:13:45 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:13:45 +00:00
Owner
Copy Link

Originally created by @sarahkittyy on GitHub (Jul 18, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

No response

Steps to reproduce

Windows Settings -> Apps -> Startup -> Scroll down to "Windows Terminal"

The option is greyed out.
image

Task Manager -> Startup -> Windows Terminal -> Enable -> Close and reopen Task Manager -> See that enabling it didn't persist.

https://user-images.githubusercontent.com/31551546/126053068-31a7e10c-2b42-40dc-a19e-a22824c784f7.mp4

Expected Behavior

I expect to be able to control whether or not windows terminal opens on boot.

Actual Behavior

Windows Terminal forcibly opens itself on startup, and I (as shown above) cannot change it.

Originally created by @sarahkittyy on GitHub (Jul 18, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software _No response_ ### Steps to reproduce Windows Settings -> Apps -> Startup -> Scroll down to "Windows Terminal" The option is greyed out. ![image](https://user-images.githubusercontent.com/31551546/126053019-11405c8c-0961-4d4f-aa41-a0170e36d8be.png) Task Manager -> Startup -> Windows Terminal -> Enable -> Close and reopen Task Manager -> See that enabling it didn't persist. https://user-images.githubusercontent.com/31551546/126053068-31a7e10c-2b42-40dc-a19e-a22824c784f7.mp4 ### Expected Behavior I expect to be able to control whether or not windows terminal opens on boot. ### Actual Behavior Windows Terminal forcibly opens itself on startup, and I (as shown above) cannot change it.
claunia commented 2026-01-31 04:13:47 +00:00
Author
Owner
Copy Link

@sarahkittyy commented on GitHub (Jul 18, 2021):

Oh, and yes, the internal "Launch on machine startup" setting is disabled, too.

@sarahkittyy commented on GitHub (Jul 18, 2021): Oh, and yes, the internal "Launch on machine startup" setting is disabled, too.
claunia commented 2026-01-31 04:13:47 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2021):

Thanks for the report! We can't figure out why this would happen; we're not locking the state of the task, and Terminal's code here tries to turn it off if your settings say that it should be off.

@DHowett commented on GitHub (Jul 22, 2021): Thanks for the report! We can't figure out why this would happen; we're not locking the state of the task, and Terminal's code [here](https://github.com/microsoft/terminal/blob/335f69e099179d533ffa3a1376035f1a63637de0/src/cascadia/TerminalApp/AppLogic.cpp#L960-L967) tries to turn it off if your settings say that it should be off.
claunia commented 2026-01-31 04:13:47 +00:00
Author
Owner
Copy Link

@sarahkittyy commented on GitHub (Aug 11, 2021):

I actually fixed this a while ago with a full reinstall of windows. I tried all over to fix my issue, to no avail. I finally just gave up and bit the bullet after that. It happened on other apps too, and I couldn't find any regedit key / group policy key that would lock the startup state like that.

You're free to close this, unless someone else is having it too :)

@sarahkittyy commented on GitHub (Aug 11, 2021): I actually fixed this a while ago with a full reinstall of windows. I tried all over to fix my issue, to no avail. I finally just gave up and bit the bullet after that. It happened on other apps too, and I couldn't find any regedit key / group policy key that would lock the startup state like that. You're free to close this, unless someone else is having it too :)
claunia commented 2026-01-31 04:13:47 +00:00
Author
Owner
Copy Link

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

Weird. Something must have been messed up on your system, but I guess it'll be impossible to know for sure what now. We'll keep our ears open for this if anyone else ever reports it.

Thanks for following up!

@zadjii-msft commented on GitHub (Aug 12, 2021): Weird. Something must have been messed up on your system, but I guess it'll be impossible to know for sure what now. We'll keep our ears open for this if anyone else ever reports it. Thanks for following up!
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 Culprit-Centennial Issue-Bug Needs-Repro Needs-Tag-Fix Product-Terminal Resolution-No-Repro
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#14567
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?