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

Terminal takes 3.5s to load user data and be functional #18925

New Issue
Closed
opened 2026-01-31 06:28:36 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 06:28:36 +00:00
Owner
Copy Link

Originally created by @omonimus1 on GitHub (Nov 18, 2022).

Windows Terminal version

No response

Windows build number

Win32NT 10.0.25236.0 Microsoft Windows NT 10.0.25236.0

Other Software

No response

Steps to reproduce

Open your terminal
Few characteristics:

  • I have a professional (work account) added into my system
    image

Expected Behavior

Be usable within reasonable time, like any other useful terminal, with a loading time at least under 250ms.

Actual Behavior

It takes ALWAYS more than 2 seconds to be ready.

Originally created by @omonimus1 on GitHub (Nov 18, 2022). ### Windows Terminal version _No response_ ### Windows build number Win32NT 10.0.25236.0 Microsoft Windows NT 10.0.25236.0 ### Other Software _No response_ ### Steps to reproduce Open your terminal Few characteristics: * I have a professional (work account) added into my system <img width="372" alt="image" src="https://user-images.githubusercontent.com/23085146/202777721-d80423dd-d681-4c2e-8828-768769281f9b.png"> ### Expected Behavior Be usable within reasonable time, like any other useful terminal, with a loading time at least under 250ms. ### Actual Behavior It takes ALWAYS more than 2 seconds to be ready.
claunia commented 2026-01-31 06:28:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 18, 2022):

It looks like this message is coming from PowerShell. If you switch your "Default Profile" to "Command Prompt," do you see the same delay?

@DHowett commented on GitHub (Nov 18, 2022): It looks like this message is coming from PowerShell. If you switch your "Default Profile" to "Command Prompt," do you see the same delay?
claunia commented 2026-01-31 06:28:38 +00:00
Author
Owner
Copy Link

@omonimus1 commented on GitHub (Nov 19, 2022):

Switching to Windows Console Host solves the loading time issue;
https://support.microsoft.com/en-us/windows/command-prompt-and-windows-powershell-for-windows-11-6453ce98-da91-476f-8651-5c14d5777c20
image

@omonimus1 commented on GitHub (Nov 19, 2022): Switching to Windows Console Host solves the loading time issue; [https://support.microsoft.com/en-us/windows/command-prompt-and-windows-powershell-for-windows-11-6453ce98-da91-476f-8651-5c14d5777c20](https://support.microsoft.com/en-us/windows/command-prompt-and-windows-powershell-for-windows-11-6453ce98-da91-476f-8651-5c14d5777c20) <img width="334" alt="image" src="https://user-images.githubusercontent.com/23085146/202840270-9bb0ebe3-eae7-4dc0-8a6a-54dc4546fb03.png">
claunia commented 2026-01-31 06:28:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 19, 2022):

At the risk of sounding like a form letter...

You are reporting a message that came from PowerShell. If you change your Default Profile to Command Prompt, are you seeing the same delay?

If not: this is an issue with PowerShell.

If so: that is surprising, because Command Prompt does not produce a message indicating its startup duration.

@DHowett commented on GitHub (Nov 19, 2022): At the risk of sounding like a form letter... You are reporting a message that came from PowerShell. If you change your **Default Profile** to **Command Prompt**, are you seeing the same delay? If not: this is an issue with PowerShell. If so: that is surprising, because Command Prompt does not produce a message indicating its startup duration.
claunia commented 2026-01-31 06:28:39 +00:00
Author
Owner
Copy Link

@omonimus1 commented on GitHub (Nov 20, 2022):

@DHowett by changing the Default Profile to Command Prompt, I DO NOT see the same delay (as shown in the previous message);
Anyway, changing the default profile by the developer settings is a temporary fix, as I have restarted my machine, and the CMD started again to show the same delay.

Could be also a bug from window settings side?
How to replicate:

  1. Go to privacy and security
  2. Click on 'For developers'
  3. Set window console to: Windows terminal (this will produce the delay)
  4. GO back to the same settings and set instead Windows Console host (this will remove the delay)
  5. Restart your machine, and start-up delay message will appear again in your cmd.
@omonimus1 commented on GitHub (Nov 20, 2022): @DHowett by changing the Default Profile to Command Prompt, I DO NOT see the same delay (as shown in the previous message); Anyway, changing the default profile by the developer settings is a temporary fix, as I have restarted my machine, and the CMD started again to show the same delay. Could be also a bug from window settings side? How to replicate: 1. Go to privacy and security 2. Click on 'For developers' 3. Set window console to: Windows terminal (this will produce the delay) 4. GO back to the same settings and set instead Windows Console host (**this will remove the delay**) 5. Restart your machine, and start-up delay message will appear again in your cmd.
claunia commented 2026-01-31 06:28:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 21, 2022):

Ah see, I think there's still a little miscommunication. There's two axes at play here:

  • The default terminal ("Windows Console Host" (conhost) vs "Windows Terminal")
  • The shell being launched (cmd, powershell, pwsh, wsl, whatever.)

PowerShell is the shell that prints out that "loading profiles took forever" message. PowerShell consistently starts slower than CMD.

Then there's the Terminal vs conhost. Conhost definitely starts faster than Terminal, but typically not more than a few hundred ms. Terminal and conhost don't care which application is run inside them. Notably, however, if you just run the Terminal directly, it'll default to some version of PowerShell. This can be changed in the Terminal settings.

Does that make more sense?

@zadjii-msft commented on GitHub (Nov 21, 2022): Ah see, I think there's still a little miscommunication. There's two axes at play here: * The default terminal ("Windows Console Host" (`conhost`) vs "Windows Terminal") * The shell being launched (`cmd`, `powershell`, `pwsh`, `wsl`, whatever.) PowerShell is the _shell_ that prints out that "loading profiles took forever" message. PowerShell consistently starts slower than CMD. Then there's the Terminal vs conhost. Conhost definitely starts faster than Terminal, but typically not more than a few hundred ms. Terminal and conhost don't care which application is run inside them. Notably, however, if you just run the Terminal directly, it'll default to some version of PowerShell. This can be changed in the Terminal settings. Does that make more sense?
claunia commented 2026-01-31 06:28:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 25, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 25, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Issue-Question Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#18925
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?