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

Auto-updater/Check for updates #18625

New Issue
Closed
opened 2026-01-31 06:19:36 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:19:36 +00:00
Owner
Copy Link

Originally created by @u84six on GitHub (Oct 7, 2022).

Description of the new feature/enhancement

I searched and didn't see a request for this, but I'd like to see an auto-updater/check for updates feature in the Terminal app. I don't use Microsoft Store to download this, so it would be great if the feature was built in. This would be good for security fixes, etc., for people who don't use Microsoft Store

If there are any major security issues, it would be convenient to be able to quickly update, particularly if not using MS Store.

Proposed technical implementation details (optional)

Maybe a Settings checkbox that has "Auto-update: enable" and if this is checked off, have a button that will check for updates and then give the option to update now.

Originally created by @u84six on GitHub (Oct 7, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I searched and didn't see a request for this, but I'd like to see an auto-updater/check for updates feature in the Terminal app. I don't use Microsoft Store to download this, so it would be great if the feature was built in. This would be good for security fixes, etc., for people who don't use Microsoft Store <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> If there are any major security issues, it would be convenient to be able to quickly update, particularly if not using MS Store. # Proposed technical implementation details (optional) Maybe a Settings checkbox that has "Auto-update: enable" and if this is checked off, have a button that will check for updates and then give the option to update now. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-Tag-FixProduct-TerminalResolution-Won't-Fix labels 2026-01-31 06:19:37 +00:00
claunia commented 2026-01-31 06:19:38 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Oct 7, 2022):

Would something like Winget or Chocolately suffice for you? (The README does list official and unofficial ways to install outside of the MS Store.)

@WSLUser commented on GitHub (Oct 7, 2022): Would something like Winget or Chocolately suffice for you? (The README does list official and unofficial ways to install outside of the MS Store.)
claunia commented 2026-01-31 06:19:38 +00:00
Author
Owner
Copy Link

@u84six commented on GitHub (Oct 7, 2022):

Would something like Winget or Chocolately suffice for you? (The README does list official and unofficial ways to install outside of the MS Store.)

Not everyone uses package managers. I'd think that something like Chocolately should work for the people who use them, but I think most people feel more comfortable when the app itself has it built in (for the sake of security). For example, the last org I worked for banned node.js because of the high risk of using packages in all the libraries. Anyone can add malware to a deep lib and it might not even expose itself for months.

@u84six commented on GitHub (Oct 7, 2022): > Would something like Winget or Chocolately suffice for you? (The README does list official and unofficial ways to install outside of the MS Store.) Not everyone uses package managers. I'd think that something like Chocolately should work for the people who use them, but I think most people feel more comfortable when the app itself has it built in (for the sake of security). For example, the last org I worked for banned node.js because of the high risk of using packages in all the libraries. Anyone can add malware to a deep lib and it might not even expose itself for months.
claunia commented 2026-01-31 06:19:38 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Oct 7, 2022):

I don't think what you're asking will ever officially occur. Also realize that Chocolately offers an enterprise option as does MS Store and eventually Winget too that allows for no outside connections but simply a private repository for Windows applications.

@WSLUser commented on GitHub (Oct 7, 2022): I don't think what you're asking will ever officially occur. Also realize that Chocolately offers an enterprise option as does MS Store and eventually Winget too that allows for no outside connections but simply a private repository for Windows applications.
claunia commented 2026-01-31 06:19:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 8, 2022):

Yea, I'm gonna reject this one. The Store is our preferred method for installing the Terminal in a way that it'll auto-update. We've also got a WIP PR for adding a button to the Terminal to manually check for updates, but that'll again backend off the package catalog AKA the Store. Also, winget is great. That's the package manager to use, and it's built-in to Windows. Much love for our coworkers over on winget.

If you install the msixbundle off Github, then that'll still hook into the package catalog in the same way. But I don't think we're gonna add any extra code to make this work for unpackaged installs, to check if there's a new package on github or something.

@zadjii-msft commented on GitHub (Nov 8, 2022): Yea, I'm gonna reject this one. The Store is our preferred method for installing the Terminal in a way that it'll auto-update. We've also got a WIP PR for adding a button to the Terminal to manually check for updates, but that'll again backend off the package catalog AKA the Store. Also, winget is great. That's the package manager to use, and it's built-in to Windows. Much love for our coworkers over on winget. If you install the msixbundle off Github, then that'll still hook into the package catalog in the same way. But I don't think we're gonna add any extra code to make this work for unpackaged installs, to check if there's a new package on github or something.
claunia commented 2026-01-31 06:19:38 +00:00
Author
Owner
Copy Link

@u84six commented on GitHub (Nov 8, 2022):

Yeah, I don't think relying on the store is a good decision because many companies block it for security reasons. I can't access MS Store from my company's laptop.

@u84six commented on GitHub (Nov 8, 2022): Yeah, I don't think relying on the store is a good decision because many companies block it for security reasons. I can't access MS Store from my company's laptop.
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-Feature Needs-Tag-Fix Product-Terminal Resolution-Won't-Fix
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#18625
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?