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

multiple startup issues #7718

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

Originally created by @perlmaster on GitHub (Apr 26, 2020).

recently the version of Windows Terminal was updated on my system and after that update there are now several issues at startup.

  1. the initial window that is opened upon startup does not have the correct size. In the global values section of the settings I have specified 120 columns and 40 rows. It opens up with smaller values for both those dimensions.

  2. the program that is run in the initial window is the powershell. However the "defaultprofile" indicates that CMD.EXE should be run

According to the "About" command I am running version 0.11.1121.0

My system is a windows 10 64 bit laptop.

Originally created by @perlmaster on GitHub (Apr 26, 2020). recently the version of Windows Terminal was updated on my system and after that update there are now several issues at startup. 1) the initial window that is opened upon startup does not have the correct size. In the global values section of the settings I have specified 120 columns and 40 rows. It opens up with smaller values for both those dimensions. 2) the program that is run in the initial window is the powershell. However the "defaultprofile" indicates that CMD.EXE should be run According to the "About" command I am running version 0.11.1121.0 My system is a windows 10 64 bit laptop.
claunia added the Resolution-Duplicate label 2026-01-31 01:11:07 +00:00
claunia commented 2026-01-31 01:11:08 +00:00
Author
Owner
Copy Link

@tadmccorkle commented on GitHub (Apr 26, 2020):

I am getting the same issue. Same version. Settings file points to an msys2 profile, but powershell opens on start-up. I can still launch different profiles, but the default is incorrect.

@tadmccorkle commented on GitHub (Apr 26, 2020): I am getting the same issue. Same version. Settings file points to an msys2 profile, but powershell opens on start-up. I can still launch different profiles, but the default is incorrect.
claunia commented 2026-01-31 01:11:08 +00:00
Author
Owner
Copy Link

@tadmccorkle commented on GitHub (Apr 26, 2020):

@perlmaster looks like there's a pinned issue that fixes this problem. Just move your settings out of the global dictionary to the root dictionary and delete the global object. Or...

Or even better, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.

@tadmccorkle commented on GitHub (Apr 26, 2020): @perlmaster looks like there's a [pinned issue that fixes this problem](https://github.com/microsoft/terminal/issues/5458). Just move your settings out of the global dictionary to the root dictionary and delete the global object. Or... > Or even better, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.
claunia commented 2026-01-31 01:11:08 +00:00
Author
Owner
Copy Link

@perlmaster commented on GitHub (Apr 26, 2020):

that seems to have fixed the issues. thanks.....

@perlmaster commented on GitHub (Apr 26, 2020): that seems to have fixed the issues. thanks.....
claunia commented 2026-01-31 01:11:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 26, 2020):

Looks like this discussion has run its course, thanks! /dup #5458

@DHowett-MSFT commented on GitHub (Apr 26, 2020): Looks like this discussion has run its course, thanks! /dup #5458
claunia commented 2026-01-31 01:11:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 26, 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 (Apr 26, 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!
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#7718
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?