microsoft
Settings can't be reloaded due to threading issues
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:
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)
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.
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...
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).
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.
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.
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.
