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 does not upgrade #14526

New Issue
Closed
opened 2026-01-31 04:12:42 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 04:12:42 +00:00
Owner
Copy Link

Originally created by @angelog0 on GitHub (Jul 15, 2021).

Windows Terminal version (or Windows build number)

19043.1083

Other Software

No response

Steps to reproduce

.

Expected Behavior

After about 20 hours, only the WT preview version upgraded to current on MS Store while WT is at 1.8.1444.1.

My installation reports WT-1.8.1521.0.

I had installed WT from the store about 2 year (ore more?) ago. Here Windows is at: Windows 10 Pro 21H1-19043.1083.

Usually WT updates a few minutes after your announce...

Actual Behavior

See above

All the fields to fill are annoying

Originally created by @angelog0 on GitHub (Jul 15, 2021). ### Windows Terminal version (or Windows build number) 19043.1083 ### Other Software _No response_ ### Steps to reproduce . ### Expected Behavior After about 20 hours, only the WT preview version upgraded to current on MS Store while WT is at 1.8.1444.1. My installation reports WT-1.8.1521.0. I had installed WT from the store about 2 year (ore more?) ago. Here Windows is at: Windows 10 Pro 21H1-19043.1083. Usually WT updates a few minutes after your announce... ### Actual Behavior See above All the fields to fill are annoying
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 04:12:42 +00:00
claunia commented 2026-01-31 04:12:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 15, 2021):

Yea, sometimes the Store is just slow to roll out updates throughout the CDN. Unfortunately, there's not much we can do about it on our end, you'll just have to be patient ☺️

@zadjii-msft commented on GitHub (Jul 15, 2021): Yea, sometimes the Store is just slow to roll out updates throughout the CDN. Unfortunately, there's not much we can do about it on our end, you'll just have to be patient ☺️
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

@angelog0 commented on GitHub (Jul 15, 2021):

The strange thing is that the new preview version was soon upgraded on the Store... In any case thanks..

@angelog0 commented on GitHub (Jul 15, 2021): The strange thing is that the new preview version was soon upgraded on the Store... In any case thanks..
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

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

Per the release notes here and kayla's blog post on the commandline blog, we're using a ring-based rollout system for 1.9. We need to be more cautious with the stable build, given how many users it could potentially impact if something were to be wrong with it.

@DHowett commented on GitHub (Jul 15, 2021): Per the [release notes here](https://github.com/microsoft/terminal/releases/tag/v1.9.1942.0) and kayla's [blog post on the commandline blog](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-10-release/), we're using a ring-based rollout system for 1.9. We need to be more cautious with the stable build, given how many users it could potentially impact if something were to be wrong with it.
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

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

Sorry, it looks like the language we used in the blog post was not particularly clear. @cinnamon-msft is that something you can fix?

@DHowett commented on GitHub (Jul 15, 2021): Sorry, it looks like the language we used in the blog post was not particularly clear. @cinnamon-msft is that something you can fix?
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

@angelog0 commented on GitHub (Jul 15, 2021):

Sorry, also these answers are not clear to me. Do they mean 1.9 is only for insider users of Windows? not standard, official users??

@angelog0 commented on GitHub (Jul 15, 2021): Sorry, also these answers are not clear to me. Do they mean 1.9 is only for insider users of Windows? not standard, official users??
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

@Astrophizz commented on GitHub (Jul 16, 2021):

Hmm I'm the Beta channel but don't see the update. Is there anywhere we can look to see which versions are in which channels?

@Astrophizz commented on GitHub (Jul 16, 2021): Hmm I'm the Beta channel but don't see the update. Is there anywhere we can look to see which versions are in which channels?
claunia commented 2026-01-31 04:12:44 +00:00
Author
Owner
Copy Link

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

Sorry, also these answers are not clear to me. Do they mean 1.9 is only for insider users of Windows? not standard, official users??

We're just rolling 1.9 out more slowly. When we released 1.8 to the Stable channel, we got about 30,000 crash reports in the first two days for an issue we probably could have avoided.

1.9 is available in the "Dev" channel this week, and will be moving to the Beta channel and then full release some time next week.

@DHowett commented on GitHub (Jul 16, 2021): > Sorry, also these answers are not clear to me. Do they mean 1.9 is only for insider users of Windows? not standard, official users?? We're just rolling 1.9 out more slowly. When we released 1.8 to the Stable channel, we got about 30,000 crash reports in the first two days for an issue we probably could have avoided. 1.9 is available in the "Dev" channel this week, and will be moving to the Beta channel and then full release some time next week.
claunia commented 2026-01-31 04:12:45 +00:00
Author
Owner
Copy Link

@angelog0 commented on GitHub (Jul 16, 2021):

we got about 30,000 crash reports

From many bug reports it seems you are developing this app mainly for insider users filling it of many many new features. The risk is that the app becomes buggy and out of control.. I would refrain from adding new features and would concentrate to fix bugs.. adding a feature at the time and adding the next only when the previous is stable.. But this is only my opinion..

@angelog0 commented on GitHub (Jul 16, 2021): > we got about 30,000 crash reports From many bug reports it seems you are developing this app mainly for insider users filling it of many many new features. The risk is that the app becomes buggy and out of control.. I would refrain from adding new features and would concentrate to fix bugs.. adding a feature at the time and adding the next only when the previous is stable.. But this is only my opinion..
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 Needs-Tag-Fix Needs-Triage Resolution-By-Design
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#14526
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?