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

Windows Terminal session log entires #20985

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

Originally created by @matys1 on GitHub (Dec 13, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.19045.0

Other Software

Some forum posts suggest that it's perhaps related to Visual Studio Code, but I wasn't able to find anything conclusive. VS Code version: 1.85.0.

Steps to reproduce

Start my windows machine and launch Windows Terminal and these log entries will start appearing. I have VS Code installed but the log entries appear even when VS Code has not been launched.

Expected Behavior

I don't want any automatic/random log entries littering my Windows Terminal session.

Actual Behavior

09:55 C:\Users\myusername>
[main 2023-12-13T07:55:27.414Z] update#setState idle
[main 2023-12-13T07:55:30.670Z] WSL is not installed, so could not detect WSL profiles
[main 2023-12-13T07:55:57.439Z] update#setState checking for updates
[main 2023-12-13T07:55:57.631Z] update#setState idle

the last two log entries will keep getting re-logged every hour. this started happening a few weeks ago. before I never saw these log entries. I have never even used WSL. why do these log entries appear?

Originally created by @matys1 on GitHub (Dec 13, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.19045.0 ### Other Software Some forum posts suggest that it's perhaps related to Visual Studio Code, but I wasn't able to find anything conclusive. VS Code version: 1.85.0. ### Steps to reproduce Start my windows machine and launch Windows Terminal and these log entries will start appearing. I have VS Code installed but the log entries appear even when VS Code has not been launched. ### Expected Behavior I don't want any automatic/random log entries littering my Windows Terminal session. ### Actual Behavior ``` 09:55 C:\Users\myusername> [main 2023-12-13T07:55:27.414Z] update#setState idle [main 2023-12-13T07:55:30.670Z] WSL is not installed, so could not detect WSL profiles [main 2023-12-13T07:55:57.439Z] update#setState checking for updates [main 2023-12-13T07:55:57.631Z] update#setState idle ``` the last two log entries will keep getting re-logged every hour. this started happening a few weeks ago. before I never saw these log entries. I have never even used WSL. why do these log entries appear?
claunia added the Issue-BugResolution-External labels 2026-01-31 07:29:44 +00:00
claunia commented 2026-01-31 07:29:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 13, 2023):

Hey there! Thanks for filing.

It absolutely seems like this is a VS Code issue: https://github.com/Microsoft/vscode/issues/56833. They're looking for people who have the ability to reproduce it, so you may be able to help them out!

FWIW: If one of your startup scripts is launching code for any reason, even for checking the version number (or something), it could be attaching itself to whichever console session first interacted with it.

/dup https://github.com/Microsoft/vscode/issues/56833

@DHowett commented on GitHub (Dec 13, 2023): Hey there! Thanks for filing. It absolutely seems like this is a VS Code issue: https://github.com/Microsoft/vscode/issues/56833. They're looking for people who have the ability to reproduce it, so you may be able to help them out! FWIW: If one of your startup scripts is launching code for any reason, even for checking the version number (or something), it could be attaching itself to whichever console session first interacted with it. /dup https://github.com/Microsoft/vscode/issues/56833
claunia commented 2026-01-31 07:29:45 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Dec 13, 2023): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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-External
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#20985
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?