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

The update to a new version happens silently without user consent #7862

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

Originally created by @Arclight3 on GitHub (May 1, 2020).

Environment

Windows build number: Windows 10
Windows Terminal version: 0.11.1191.0 (currently installed)

Steps to reproduce

Expected behavior

Let the user decide when to update to a newer version or opt out from automatic updates.

Actual behavior

The software is silently updating without user consent!
After last update there were breaking changes (1. My custom color scheme stopped working. Out of nowhere I got black text on black background - which you can imagine is a very cool experience when you are in a hurry and need to get things done fast. 2. The syntax to overwrite shortcuts to switch to a tab by number changed, so my navigation shortcuts stopped working, hitting my productivity).
Again: Updates, especially breaking changes should not happen without user consent, otherwise this software is not reliable to be used in a production environment!
Also, I don't think it`s hard to migrate the syntax in settings.json when you do it in defaults.json (Like it happend with breaking change 2 that I mentioned earlier)! Just saying..

Originally created by @Arclight3 on GitHub (May 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Windows 10 Windows Terminal version: 0.11.1191.0 (currently installed) ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior Let the user decide when to update to a newer version or opt out from automatic updates. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior The software is silently updating without user consent! After last update there were breaking changes (1. My custom color scheme stopped working. Out of nowhere I got black text on black background - which you can imagine is a very cool experience when you are in a hurry and need to get things done fast. 2. The syntax to overwrite shortcuts to switch to a tab by number changed, so my navigation shortcuts stopped working, hitting my productivity). Again: Updates, especially breaking changes should not happen without user consent, otherwise this software is not reliable to be used in a production environment! Also, I don't think it`s hard to migrate the syntax in settings.json when you do it in defaults.json (Like it happend with breaking change 2 that I mentioned earlier)! Just saying.. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 01:14:27 +00:00
claunia commented 2026-01-31 01:14:28 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 1, 2020):

I'm sorry about all that. We haven't been able to get the store to stop killing us -- even when the application says "hold up, I'm in use", it gets terminated automatically. I'm in talks with the store and servicing folks about how best to handle this.

Also, I'm sorry about the one-time breaking settings change. This software really isn't intended to be used in a production environment when it's a technical preview. I know that we do that, and a lot of folks are doing that, but it's like being in the Windows Insider program.

After 1.0, settings changes will come with migration.

I'm gonna close this one out with a hat tip to #5458 and /dup #3915.

Thanks for letting us know. I know it's been rough. ☹️

@DHowett-MSFT commented on GitHub (May 1, 2020): I'm sorry about all that. We haven't been able to get the store to stop killing us -- even when the application says "hold up, I'm in use", it gets terminated automatically. I'm in talks with the store and servicing folks about how best to handle this. Also, I'm sorry about the one-time breaking settings change. This software really isn't _intended_ to be used in a production environment when it's a technical preview. I know that we do that, and a lot of folks are doing that, but it's like being in the Windows Insider program. After 1.0, settings changes will come with migration. I'm gonna close this one out with a hat tip to #5458 and /dup #3915. Thanks for letting us know. I know it's been rough. ☹️
claunia commented 2026-01-31 01:14:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 1, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 1, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 01:14:28 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 1, 2020):

(The main issue is that we yanked all the code that re-wrote a user's settings file, because it was unreliable and dangerous. We didn't want to reintroduce it so late in the cycle when we were worried it would end in something worse than "my key bindings aren't working".)

@DHowett-MSFT commented on GitHub (May 1, 2020): (The main issue is that we yanked all the code that re-wrote a user's settings file, because it was unreliable and dangerous. We didn't want to reintroduce it so late in the cycle when we were worried it would end in something worse than "my key bindings aren't working".)
claunia commented 2026-01-31 01:14:29 +00:00
Author
Owner
Copy Link

@Arclight3 commented on GitHub (May 1, 2020):

Thanks for the reply. I understand the situation.
I am glad that you are working to solve it. I hope you'll manage to find a solution before the next update.
Also, thanks for caring about the user experience even thou the terminal is still in preview.
Keep up the good work :)

@Arclight3 commented on GitHub (May 1, 2020): Thanks for the reply. I understand the situation. I am glad that you are working to solve it. I hope you'll manage to find a solution before the next update. Also, thanks for caring about the user experience even thou the terminal is still in preview. Keep up the good work :)
claunia commented 2026-01-31 01:14:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 1, 2020):

before the next update

We definitely won't before then, but we won't have any breaking settings changes in it at least 😬

@DHowett-MSFT commented on GitHub (May 1, 2020): > before the next update We definitely won't before then, but we won't have any breaking settings changes in it at least 😬
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 Resolution-Duplicate
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#7862
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?