starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Ask Windows Terminal how to disable automatic update #21048

New Issue
Closed
opened 2026-01-31 07:31:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:31:39 +00:00
Owner
Copy Link

Originally created by @thousmile on GitHub (Jan 4, 2024).

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Ask Windows Terminal how to disable automatic updates, there are too many BUGs in the latest version. Can't use it at all! 1.18.x opened for the first time, and the air environment variable. Can't find a place to close

Expected Behavior

aa

Actual Behavior

aa

Originally created by @thousmile on GitHub (Jan 4, 2024). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce Ask Windows Terminal how to disable automatic updates, there are too many BUGs in the latest version. Can't use it at all! 1.18.x opened for the first time, and the air environment variable. Can't find a place to close ### Expected Behavior aa ### Actual Behavior aa
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 07:31:39 +00:00
claunia commented 2026-01-31 07:31:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 4, 2024):

Can you please add the exact version number? We had a couple fixes for some environment variable issues earlier in 1.18 that we hotfixed in December.

Could you elaborate on the exact issue you're seeing/? If you're seeing something we haven't seen before, I'd rather make sure the issue is tracked so we can fix it, rather than just disable updates entirely 😉

@zadjii-msft commented on GitHub (Jan 4, 2024): Can you please add the exact version number? We had a couple fixes for some environment variable issues earlier in 1.18 that we hotfixed in December. Could you elaborate on the exact issue you're seeing/? If you're seeing something we haven't seen before, I'd rather make sure the issue is tracked so we can fix it, rather than just disable updates entirely 😉
claunia commented 2026-01-31 07:31:40 +00:00
Author
Owner
Copy Link

@thousmile commented on GitHub (Jan 5, 2024):

@zadjii-msft

This video is my operation Windows Terminal version 1.17.11461.0 and version 1.18.3181.0

When version 1.18.3181.0 is opened for the first time, it is a new environment, and the “go version” command configured in the environment variable cannot be executed. After passing the settings, in the new tab, you can execute the “go version” command

Version 1.17.11461.0 has no problems. You can also execute the “go version” command when opening it for the first time.

https://github.com/microsoft/terminal/assets/28520524/57abe296-5690-463d-8df9-51e4d2616b22

@thousmile commented on GitHub (Jan 5, 2024): @zadjii-msft This video is my operation Windows Terminal version 1.17.11461.0 and version 1.18.3181.0 When version 1.18.3181.0 is opened for the first time, it is a new environment, and the “go version” command configured in the environment variable cannot be executed. After passing the settings, in the new tab, you can execute the “go version” command Version 1.17.11461.0 has no problems. You can also execute the “go version” command when opening it for the first time. https://github.com/microsoft/terminal/assets/28520524/57abe296-5690-463d-8df9-51e4d2616b22
claunia commented 2026-01-31 07:31:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 5, 2024):

Huh. That's got shades of #16226 in it, but also, seems a bit different. In your case, you shouldn't really be inheriting env vars from File Explorer. Very strange then that the first tab still uses a bad PATH, but the subsequent tabs get a working PATH.

There might be a couple things at play here:

  • Are you on Windows 10? If you are, does this repro if you make absolutely sure there are no other open Terminal windows or processes?
  • What exactly is the difference in your PATH here? (e.g. share $env:path in both a broken tab and a working one)
  • Does this repro if you launch wt from the Run dialog? (maybe there's something weird about the way the shell context menu entry invokes the Terminal)
@zadjii-msft commented on GitHub (Jan 5, 2024): Huh. That's got shades of #16226 in it, but also, seems a bit different. In your case, you shouldn't really be _inheriting_ env vars from File Explorer. Very strange then that the first tab still uses a bad PATH, but the subsequent tabs get a working PATH. There might be a couple things at play here: * Are you on Windows 10? If you are, does this repro if you make absolutely sure there are no other open Terminal windows or processes? * What exactly is the difference in your PATH here? (e.g. share `$env:path` in both a broken tab and a working one) * Does this repro if you launch `wt` from the Run dialog? (maybe there's something weird about the way the shell context menu entry invokes the Terminal)
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-Author-Feedback Needs-Triage
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#21048
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?