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

Settings can't be reloaded with a "threading" error #23756

New Issue
Closed
opened 2026-01-31 08:51:40 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 08:51:40 +00:00
Owner
Copy Link

Originally created by @Efreak on GitHub (Oct 26, 2025).

Windows Terminal version

1.24.2812.0

Windows build number

10.0.26200.6899

Other Software

Software that has been running when I see the error (usually no more than 2-3 tabs at a time):

  • CMD.exe (ie, just a blank terminal left open)
  • koboldcpp (running up to 4 small LLMs ranging from pythia 70m to llama 1b, a total of 3.88gb right now)
  • random programs that I happen to have left running (some dotnet dlls, calibre with debugger attached, some python/nodejs scripts, etc)
  • WSL2 environments
  • SSH connections (usually they're disconnected by the time I sit down)
  • cygwin bash shell

Steps to reproduce

Leave Windows Terminal running overnight. The error pops up on its own.

Expected Behavior

No errors without user input.
No reloading the settings file when it hasn't even changed (unless this is coming from before then?)

Actual Behavior

A window pops up with An outgoing call cannot be made since the application is dispatching an input-synchronous call.

Screenshot:

Image
Originally created by @Efreak on GitHub (Oct 26, 2025). ### Windows Terminal version 1.24.2812.0 ### Windows build number 10.0.26200.6899 ### Other Software Software that has been running when I see the error (usually no more than 2-3 tabs at a time): - CMD.exe (ie, just a blank terminal left open) - koboldcpp (running up to 4 small LLMs ranging from pythia 70m to llama 1b, a total of 3.88gb right now) - random programs that I happen to have left running (some dotnet dlls, calibre with debugger attached, some python/nodejs scripts, etc) - WSL2 environments - SSH connections (usually they're disconnected by the time I sit down) - cygwin bash shell ### Steps to reproduce Leave Windows Terminal running overnight. The error pops up on its own. ### Expected Behavior No errors without user input. No reloading the settings file when it hasn't even changed (unless this is coming from before then?) ### Actual Behavior A window pops up with *An outgoing call cannot be made since the application is dispatching an input-synchronous call*. -------- Screenshot: <img width="686" height="364" alt="Image" src="https://github.com/user-attachments/assets/ee6bd63b-25ec-4832-87b2-579777096dd0" />
claunia added the Area-SettingsIssue-BugNeeds-Tag-FixNeeds-ReproProduct-Terminal labels 2026-01-31 08:51:40 +00:00
claunia commented 2026-01-31 08:51:42 +00:00
Author
Owner
Copy Link

@Efreak commented on GitHub (Oct 26, 2025):

Note: This is currently also happening when I open a new instance of the terminal (either opening a new window from the start menu, or dragging an existing tab out of its window, even if it's the only tab in that window)

@Efreak commented on GitHub (Oct 26, 2025): Note: This is currently also happening when I open a new instance of the terminal (either opening a new window from the start menu, or dragging an existing tab out of its window, even if it's the only tab in that window)
claunia commented 2026-01-31 08:51:43 +00:00
Author
Owner
Copy Link

@codefox42 commented on GitHub (Oct 27, 2025):

I have also been seeing this message on several computers since at least October 20. I couldn't recognize a pattern yet, but leaving the terminal window open overnight would at least suit my situation.

@codefox42 commented on GitHub (Oct 27, 2025): I have also been seeing this message on several computers since at least October 20. I couldn't recognize a pattern yet, but leaving the terminal window open overnight would at least suit my situation.
claunia commented 2026-01-31 08:51:43 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 27, 2025):

The yellow error message is quite helpful though. It's probably related to this then?
5ae95d7df0/src/cascadia/TerminalSettingsModel/CascadiaSettingsSerialization.cpp (L72-L92)

I wonder if we need to make the entire settings loading an async function...

@lhecker commented on GitHub (Oct 27, 2025): The yellow error message is quite helpful though. It's probably related to this then? https://github.com/microsoft/terminal/blob/5ae95d7df0ee3050ad36b98cd8f3f8d55005f0d2/src/cascadia/TerminalSettingsModel/CascadiaSettingsSerialization.cpp#L72-L92 I wonder if we need to make the entire settings loading an async function...
claunia commented 2026-01-31 08:51:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 27, 2025):

Huh. I don't know why that would have changed, though?

@DHowett commented on GitHub (Oct 27, 2025): Huh. I don't know why that would have _changed_, though?
claunia commented 2026-01-31 08:51:44 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 27, 2025):

Yeah, we have several new bugs that I'm not sure where they're coming from (e.g. the jumping scroll one, or the one with the trackpad). This one as well, shouldn't be affected by the windowing refactor, I think?

It's a long shot, but the only thing I can imagine what causes this is that previously we'd reload settings on a thread that's not a UI thread (it was the main()-thread for WindowEmperor).

@lhecker commented on GitHub (Oct 27, 2025): Yeah, we have several new bugs that I'm not sure where they're coming from (e.g. the jumping scroll one, or the one with the trackpad). This one as well, shouldn't be affected by the windowing refactor, I think? It's a long shot, but the only thing I can imagine what causes this is that previously we'd reload settings on a thread that's not a UI thread (it was the `main()`-thread for WindowEmperor).
claunia commented 2026-01-31 08:51:44 +00:00
Author
Owner
Copy Link

@BPJEnnova commented on GitHub (Nov 27, 2025):

For information: I got the same message but found out that the cause was PowerToys's "Light Switch" option. I had it set to Behavior Apps, and that apparently tries to change the settings when I switch between Light and Dark theme.

Just for information if someone else found this thread for that reason.

@BPJEnnova commented on GitHub (Nov 27, 2025): For information: I got the same message but found out that the cause was PowerToys's "Light Switch" option. I had it set to Behavior Apps, and that apparently tries to change the settings when I switch between Light and Dark theme. Just for information if someone else found this thread for that reason.
claunia commented 2026-01-31 08:51:45 +00:00
Author
Owner
Copy Link

@kchawla-pi commented on GitHub (Dec 12, 2025):

PowerToysReport_2025-12-12-13-34-04.zip
Clarifying that I observed the same behavior with Powertoys' Light Switch but not when switching color themes using "Windows Settings > Personalization"

The error does not appear when using Switch Theme option from Auto Dark Mode.

@kchawla-pi commented on GitHub (Dec 12, 2025): [PowerToysReport_2025-12-12-13-34-04.zip](https://github.com/user-attachments/files/24133446/PowerToysReport_2025-12-12-13-34-04.zip) Clarifying that I observed the same behavior with Powertoys' Light Switch but not when switching color themes using "Windows Settings > Personalization" The error does not appear when using Switch Theme option from Auto Dark Mode.
claunia commented 2026-01-31 08:51:45 +00:00
Author
Owner
Copy Link

@soerennielsen commented on GitHub (Dec 16, 2025):

I have also been seeing this message on several computers since at least October 20. I couldn't recognize a pattern yet, but leaving the terminal window open overnight would at least suit my situation.

Powertoys Light Switch was release around here.

I see the same errors and I also have light switch set to switch between light and dark (dark at evenings). What then happens is that the PC is woken the next morning and light switch will have a job of switching theme at the time when everything else is waking up. I often get the "Failed to reload settings" error after a resume, which often coincides with light switch activity.

@soerennielsen commented on GitHub (Dec 16, 2025): > I have also been seeing this message on several computers since at least October 20. I couldn't recognize a pattern yet, but leaving the terminal window open overnight would at least suit my situation. Powertoys Light Switch was release around here. I see the same errors and I also have light switch set to switch between light and dark (dark at evenings). What then happens is that the PC is woken the next morning and light switch will have a job of switching theme at the time when everything else is waking up. I often get the "Failed to reload settings" error after a resume, which often coincides with light switch activity.
claunia commented 2026-01-31 08:51:45 +00:00
Author
Owner
Copy Link

@BradKnowles commented on GitHub (Jan 14, 2026):

I'm also seeing this, but do not have PowerToys installed.

@BradKnowles commented on GitHub (Jan 14, 2026): I'm also seeing this, but do not have PowerToys installed.
claunia commented 2026-01-31 08:51:46 +00:00
Author
Owner
Copy Link

@soerennielsen commented on GitHub (Jan 17, 2026):

At the moment I can reliably reproduce by:

  1. Having one terminal (windows terminal) - does not matter if I have one or multiple tabs both powershell and msdos based tabs, one is enough.
  2. Win+R cmd to open a new terminal. The new terminal shows the error every single time

After a while I close all terminals, and then I'm back to it being non-reproducable.

The first terminal was a long running one that had persisted about 2 days and through multiple sleep cycles.

I believe the common denominator in the cases I've seen: It requires two different terminal, one of them having been through some powercycles/long lived. The first terminal seem to have some unreleased lock. I can look at handles etc. the next time it happens.

@soerennielsen commented on GitHub (Jan 17, 2026): At the moment I can reliably reproduce by: 1. Having one terminal (windows terminal) - does not matter if I have one or multiple tabs both powershell and msdos based tabs, one is enough. 2. Win+R cmd to open a new terminal. The new terminal shows the error every single time After a while I close all terminals, and then I'm back to it being non-reproducable. The first terminal was a long running one that had persisted about 2 days and through multiple sleep cycles. I believe the common denominator in the cases I've seen: It requires two different terminal, one of them having been through some powercycles/long lived. The first terminal seem to have some unreleased lock. I can look at handles etc. the next time it happens.
claunia commented 2026-01-31 08:51:46 +00:00
Author
Owner
Copy Link

@Efreak commented on GitHub (Jan 21, 2026):

Having power toys is not required to reproduce. I just reproduced this in a fresh install of Windows 11 that only has terminal and powershell installed (installed Windows, got myself fully up to date, installed some optional components/features like ssh server, then opened terminal to run a ps1 script from unigetui and the error popped up)

@Efreak commented on GitHub (Jan 21, 2026): Having power toys is not required to reproduce. I just reproduced this in a *fresh* install of Windows 11 that only has terminal and powershell installed (installed Windows, got myself fully up to date, installed some optional components/features like ssh server, then opened terminal to run a ps1 script from unigetui and the error popped up)
claunia commented 2026-01-31 08:51:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 22, 2026):

We're backporting the band-aid fix for this issue to 1.23. :)

FWIW, I tried for about an hour and I couldn't reproduce it with any amount of app fragment profiles (which is where our threading issues are), theme changes or settings file updates. Alas.

@DHowett commented on GitHub (Jan 22, 2026): We're backporting the band-aid fix for this issue to 1.23. :) FWIW, I tried for about an hour and I couldn't reproduce it with any amount of app fragment profiles (which is where our threading issues are), theme changes or settings file updates. Alas.
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 Area-Settings Issue-Bug Needs-Repro Needs-Tag-Fix Product-Terminal
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#23756
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?