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

WT is relatively slow at executing cmd scripts at Windows startup #19541

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

Originally created by @vadimkantorov on GitHub (Mar 16, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.1413

Other Software

No response

Steps to reproduce

My Windows system somehow has some *.cmd logon scripts: Terminal/cmd windows get spun up and closed several times at Windows login.

I could not find those scripts in Sysinternals autoruns64.exe, but they certainly get executed. My system is in a good shape, so it's not some virus etc.

These scripts do not require user input and typically do not even print anything, but the time to open a WT window, render it and then close is relatively slow. So WT startup/teardown time is a whole different beast when the usecase are the logon scripts and the OS/disk is bombarded by tons of apps/services starting up in parallel.

Some questions:

  1. Is it possible to somehow ask WT to log to file its launches / closings with times (and hopefully with the argv)?
  2. WT should be much faster for these cycles. Maybe it could somehow lazily render the Window or do only a minimal render (since the teardown is imminent faster than it could complete the rendering)? cmd.exe used to be much faster for these cycles. Ideally, WT would not be rendered at all for these scenarios. Maybe some "quiet" calls of cmd.exe did not show any window before, and started to show WT window now?

Expected Behavior

No response

Actual Behavior

N/A

Originally created by @vadimkantorov on GitHub (Mar 16, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621.1413 ### Other Software _No response_ ### Steps to reproduce My Windows system somehow has some `*.cmd` logon scripts: Terminal/cmd windows get spun up and closed several times at Windows login. I could not find those scripts in Sysinternals `autoruns64.exe`, but they certainly get executed. My system is in a good shape, so it's not some virus etc. These scripts do not require user input and typically do not even print anything, but the time to open a WT window, render it and then close is relatively slow. So WT startup/teardown time is a whole different beast when the usecase are the logon scripts and the OS/disk is bombarded by tons of apps/services starting up in parallel. Some questions: 1. Is it possible to somehow ask WT to log to file its launches / closings with times (and hopefully with the argv)? 2. WT should be much faster for these cycles. Maybe it could somehow lazily render the Window or do only a minimal render (since the teardown is imminent faster than it could complete the rendering)? cmd.exe used to be much faster for these cycles. Ideally, WT would not be rendered at all for these scenarios. Maybe some "quiet" calls of cmd.exe did not show any window before, and started to show WT window now? ### Expected Behavior _No response_ ### Actual Behavior N/A
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:46:37 +00:00
claunia commented 2026-01-31 06:46:38 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 16, 2023):

Hi @vadimkantorov. Thanks for the feedback.

  1. WT should be much faster for these cycles. Maybe it could somehow lazily render the Window or do only a minimal render (since the teardown is imminent faster than it could complete the rendering)? cmd.exe used to be much faster for these cycles. Ideally, WT would not be rendered at all for these scenarios. Maybe some "quiet" calls of cmd.exe did not show any window before, and started to show WT window now?

Yes! We definitely need to improve our startup/teardown performance. We're tracking this over in #5907, so we're going to mark this as a /dup of #5907.

  1. Is it possible to somehow ask WT to log to file its launches / closings with times (and hopefully with the argv)?

As of now, no. The console hosting process model precludes us from doing this. However, there is a windows system feature that you can enable to audit process execution. This section from our FAQs may help out: https://github.com/microsoft/terminal/wiki/What-is-causing-consoles-to-pop-up-on-me%3F

@carlos-zamora commented on GitHub (Mar 16, 2023): Hi @vadimkantorov. Thanks for the feedback. > 2. WT should be much faster for these cycles. Maybe it could somehow lazily render the Window or do only a minimal render (since the teardown is imminent faster than it could complete the rendering)? cmd.exe used to be much faster for these cycles. Ideally, WT would not be rendered at all for these scenarios. Maybe some "quiet" calls of cmd.exe did not show any window before, and started to show WT window now? Yes! We definitely need to improve our startup/teardown performance. We're tracking this over in #5907, so we're going to mark this as a /dup of #5907. > 1. Is it possible to somehow ask WT to log to file its launches / closings with times (and hopefully with the argv)? As of now, no. The console hosting process model precludes us from doing this. However, there is a windows system feature that you can enable to audit process execution. This section from our FAQs may help out: https://github.com/microsoft/terminal/wiki/What-is-causing-consoles-to-pop-up-on-me%3F
claunia commented 2026-01-31 06:46:38 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 16, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 16, 2023): 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!
claunia commented 2026-01-31 06:46:38 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Mar 16, 2023):

Is it possible to have some heuristics that delay full UI rendering specifically when it's running in unattended mode? Rendering of the UI / full Terminal systems bootstrapping is useless in these cases as the whole thing needs to exit in 500ms. E.g. ideally it should run cmd.exe some_script.cmd as fast as the old cmd.exe wrt UI loading and teardown

@vadimkantorov commented on GitHub (Mar 16, 2023): Is it possible to have some heuristics that delay full UI rendering specifically when it's running in unattended mode? Rendering of the UI / full Terminal systems bootstrapping is useless in these cases as the whole thing needs to exit in 500ms. E.g. ideally it should run `cmd.exe some_script.cmd` as fast as the old cmd.exe wrt UI loading and teardown
claunia commented 2026-01-31 06:46:39 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Mar 16, 2023):

I think that this specific usecase is not discussed in https://github.com/microsoft/terminal/issues/5907

@vadimkantorov commented on GitHub (Mar 16, 2023): I think that this specific usecase is not discussed in https://github.com/microsoft/terminal/issues/5907
claunia commented 2026-01-31 06:46:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 24, 2023):

@zadjii-msft could Terminal somehow run headless / without UI or with minimal non fully-fledged UWP UI if a *.cmd (or other) script is being launched in an unattended way as part of Windows startup? usecase of slow Terminal UI flickering when Windows runs some startup scripts: #15001 - maybe these runtime scripts are being executed as cmd.exe .... which now spins up Terminal. maybe for these cases Terminal could support a headless mode?

(from #9996)

Maybe? But those scripts shouldn't be displaying consoles in the first place. Defterm handoff is pretty specific - if a script wanted a visible console window, it tries to do a defterm handoff (resulting in the Terminal UI). Any of the many ways to start a hidden / minimized / headless console application won't invoke a defterm handoff.

So, a defterm handoff starting the Terminal headless is kinda besides the point here. Those apps either wanted to have a visible console window, or didn't bother hiding themselves on startup.

Now, 1.18 does have an unrelated fix where it won't display the Terminal HWND at all till the UI is actually ready. So that should mitigate some "transparent terminal window frames that pop in and out of existence before the Terminal even appears".

@zadjii-msft commented on GitHub (May 24, 2023): > @zadjii-msft could Terminal somehow run headless / without UI or with minimal non fully-fledged UWP UI if a `*.cmd` (or other) script is being launched in an unattended way as part of Windows startup? usecase of slow Terminal UI flickering when Windows runs some startup scripts: #15001 - maybe these runtime scripts are being executed as `cmd.exe ....` which now spins up Terminal. maybe for these cases Terminal could support a headless mode? _(from #9996)_ Maybe? But those scripts shouldn't be displaying consoles in the first place. Defterm handoff is pretty specific - if a script wanted a _visible_ console window, it tries to do a defterm handoff (resulting in the Terminal UI). Any of the _many_ ways to start a hidden / minimized / headless console application _won't_ invoke a defterm handoff. So, a defterm handoff starting the Terminal headless is kinda besides the point here. Those apps either wanted to have a visible console window, or didn't bother hiding themselves on startup. Now, 1.18 does have an unrelated fix where it won't display the Terminal HWND at all till the UI is actually ready. So that should mitigate some "transparent terminal window frames that pop in and out of existence before the Terminal even appears".
claunia commented 2026-01-31 06:46:39 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (May 24, 2023):

hmm... and in my case, these scripts somehow don't appear in sysinternals autoruns. I wonder if Terminal/cmd.exe (or maybe Windows in general?) has any simple way of logging all process executions (along with args)? that way at least I can give you a concrete example

I agree that they shouldn't be displaying consoles, so probably some command line flags are missing to hide these windows. but if they show it anyway, i wonder if there's any way to speed up these UI's starting up / shutting down. Maybe Terminal launches first in headless mode, is it faster for all subsequent Terminals to start up / shut down?

@vadimkantorov commented on GitHub (May 24, 2023): hmm... and in my case, these scripts somehow don't appear in sysinternals autoruns. I wonder if Terminal/cmd.exe (or maybe Windows in general?) has any simple way of logging all process executions (along with args)? that way at least I can give you a concrete example I agree that they shouldn't be displaying consoles, so probably some command line flags are missing to hide these windows. but if they show it anyway, i wonder if there's any way to speed up these UI's starting up / shutting down. Maybe Terminal launches first in headless mode, is it faster for all subsequent Terminals to start up / shut down?
claunia commented 2026-01-31 06:46:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 25, 2023):

simple way of logging all process executions

Sorry to give you a drive-by, but you might be served well enough on this point by https://github.com/microsoft/terminal/wiki/What-is-causing-consoles-to-pop-up-on-me%3F 😄

@DHowett commented on GitHub (May 25, 2023): > simple way of logging all process executions Sorry to give you a drive-by, but you _might_ be served well enough on this point by https://github.com/microsoft/terminal/wiki/What-is-causing-consoles-to-pop-up-on-me%3F :smile:
claunia commented 2026-01-31 06:46:40 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (May 27, 2023):

btw gpedit.msc is not included in Windows 11 Home... So hacks needed to install it https://answers.microsoft.com/en-us/windows/forum/all/how-to-enable-the-gpeditmsc-on-windows-10-and-11/dbc76919-f2b5-4dec-a2b7-bcf545c34d00 - maybe worth including it in that wiki document

I used these two cmd commands in an elevated Command Prompt:

FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")

Then gpedit.msc opened

@vadimkantorov commented on GitHub (May 27, 2023): btw `gpedit.msc` is not included in Windows 11 Home... So hacks needed to install it https://answers.microsoft.com/en-us/windows/forum/all/how-to-enable-the-gpeditmsc-on-windows-10-and-11/dbc76919-f2b5-4dec-a2b7-bcf545c34d00 - maybe worth including it in that wiki document I used these two cmd commands in an elevated Command Prompt: ``` FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F") FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F") ``` Then `gpedit.msc` opened
claunia commented 2026-01-31 06:46:41 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Jun 3, 2023):

@DHowett btw how can I filter the Process Creation events in the Event Viewer? What should I select as Event Sources? Without selecting Event Sources, the Task Category filter drop down is disabled so I can't choose Process Creation to filter only the relevant events

@vadimkantorov commented on GitHub (Jun 3, 2023): @DHowett btw how can I filter the Process Creation events in the Event Viewer? What should I select as `Event Sources`? Without selecting `Event Sources`, the `Task Category` filter drop down is disabled so I can't choose `Process Creation` to filter only the relevant events
claunia commented 2026-01-31 06:46:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 5, 2023):

That is an excellent question! Unfortunately, I am not particularly good with Event Viewer and I don't know how to filter those events adequately. ☹️

@DHowett commented on GitHub (Jun 5, 2023): That is an excellent question! Unfortunately, I am not particularly good with Event Viewer and I don't know how to filter those events adequately. ☹️
claunia commented 2026-01-31 06:46:41 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Jun 6, 2023):

I wonder if Terminal could have an option for logging to its own topic in Event Viewer logging, including its startup arguments

@vadimkantorov commented on GitHub (Jun 6, 2023): I wonder if Terminal could have an option for logging to its own topic in Event Viewer logging, including its startup arguments
claunia commented 2026-01-31 06:46:41 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Oct 6, 2025):

This also leads to Terminal capturing focus for 1 second stealing it from wherever I'm typing and it steals keys I've typed

When there are multiple startup scripts, it gets quite nasty. In addition to them being displayed in the foreground.

At least I propose to somehow have these scripts not execute in a foreground window, it will remove the flicker. Maybe even execute these as minimized window somehow.

If these are executed as cmd.exe scripts - maybe there could be a hack to not show window in foreground if it completed execution in 1 second (e.g. start as minimized and draw the window in foreground only if the batch script hasn't completed execution in 1 second. this can also speed up execution of such scripts!)

@vadimkantorov commented on GitHub (Oct 6, 2025): This also leads to Terminal capturing focus for 1 second stealing it from wherever I'm typing and it steals keys I've typed When there are multiple startup scripts, it gets quite nasty. In addition to them being displayed in the foreground. At least I propose to somehow have these scripts not execute in a foreground window, it will remove the flicker. Maybe even execute these as minimized window somehow. If these are executed as `cmd.exe` scripts - maybe there could be a hack to not show window in foreground if it completed execution in 1 second (e.g. start as minimized and draw the window in foreground only if the batch script hasn't completed execution in 1 second. this can also speed up execution of such scripts!)
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 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#19541
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?