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

Fails to start when "Sync Settings" is active in a machine where the primary EXE is not installed #2467

New Issue
Closed
opened 2026-01-30 22:55:47 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:55:47 +00:00
Owner
Copy Link

Originally created by @ocalvo on GitHub (Jul 1, 2019).

Cannot use Windows Terminal at all.

Environment

Windows 10 19H1
PowerShell Preview 6 installed in machine 1
PowerShell Preview 7 installed in machine 2
Windows "Sync Settings" is active.

Windows build number: [run "ver" at a command prompt]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

  1. Install Windows Terminal in 2 machines with the same MSA account.
  2. Install PowerShell Core in machine 1.
  3. Change the default console to be PowerShell Core.
  4. Log out and wait for settings to sync.
  5. Log into Machine 2.

Start Windows Terminal.

Expected behavior

Windows Terminal can start (even in CMD or some recovery console mode)

Actual behavior

Windows Terminal fails to start

The settings from machine 1 are getting copied to machine 2, but this is invalid as machine 2 does not have the same environment as machine 1.

Originally created by @ocalvo on GitHub (Jul 1, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> Cannot use Windows Terminal at all. # Environment Windows 10 19H1 PowerShell Preview 6 installed in machine 1 PowerShell Preview 7 installed in machine 2 Windows "Sync Settings" is active. ```none Windows build number: [run "ver" at a command prompt] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce 1. Install Windows Terminal in 2 machines with the same MSA account. 2. Install PowerShell Core in machine 1. 3. Change the default console to be PowerShell Core. 4. Log out and wait for settings to sync. 5. Log into Machine 2. <!-- A description of how to trigger this bug. --> Start Windows Terminal. # Expected behavior Windows Terminal can start (even in CMD or some recovery console mode) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Windows Terminal fails to start <!-- What's actually happening? --> The settings from machine 1 are getting copied to machine 2, but this is invalid as machine 2 does not have the same environment as machine 1.
claunia added the Resolution-Duplicate label 2026-01-30 22:55:47 +00:00
claunia commented 2026-01-30 22:55:48 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 2, 2019):

I'm going to consolidate these discussions in #1770. Thanks, Oscar!

@DHowett-MSFT commented on GitHub (Jul 2, 2019): I'm going to consolidate these discussions in #1770. Thanks, Oscar!
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#2467
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?