Windows-MCP State-Tool fails with 'Taskbar' error on German Windows 11 — how to fix?
I'm on Windows 11 24H2 (German) using Claude Desktop with Windows-MCP v0.1.0 installed from the Claude Desktop extension. The State-Tool always fails with a persistent 'Taskbar' error and tools sometimes disappear. Where are the logs, and how do I make State-Tool work on a non-English Windows system?
Originally asked on GitHub: https://github.com/CursorTouch/Windows-MCP/issues/24
6 answers
The State-Tool issue was resolved in this thread after the maintainer updated
manifest.jsonand the reporter used the GitHub version instead of the one bundled in Claude Desktop — State-Tool then worked on German Windows. The follow-up permission-prompt problem was answered with "change the settings to ask for permission," but the thread does not confirm whether that fixed it.Logs are in
%USERPROFILE%\AppData\Roaming\Claude\logs. The failing call showed:ERROR Error calling tool 'State-Tool': 'Taskbar', raised from fastmcp'stool_manager.py.The maintainer said the version in Claude Desktop is old and asked the reporter to clone the GitHub repo. The reporter did (
git clone https://github.com/CursorTouch/Windows-MCP.git) and rannpx @anthropic-ai/dxt pack; the packed manifest still reported 0.1.0, which the maintainer then updated. After that, the State-Tool worked on the German system. The thread does not describe how the updated version was installed.General advice based on the maintainer's comments: a German (or other non-English) Windows locale can cause the tool to behave incorrectly, so either set the machine language to English or tell Claude in your query that the system is German.
If you rely on the permission prompt before the tool acts, double-check your extension settings are configured to ask for permission after updating.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter used Windows-MCP 0.1.0 installed from Claude Desktop on German Windows 11 24H2. State-Tool failed with a persistent 'Taskbar' error, Launch-Tool started wrong programs, and tools disappeared.
Source: https://github.com/CursorTouch/Windows-MCP/issues/24 (opens external site)
Did this work for you?What @palasinio tried on GitHub (Outcome unclear)
Reporter cloned the repo from GitHub and ran
npx @anthropic-ai/dxt pack. The packed manifest still showed version 0.1.0, so no fix was confirmed at this point.Source: https://github.com/CursorTouch/Windows-MCP/issues/24#issuecomment-3192370205 (opens external site)
Did this work for you?What @Jeomon tried on GitHub (Outcome unclear)
Maintainer said the version in Claude Desktop is old, suggested cloning the GitHub repo, and offered a workaround: set the machine language to English or mention the German system in the query. Logs were pointed to
%USERPROFILE%\AppData\Roaming\Claude\logs.Source: https://github.com/CursorTouch/Windows-MCP/issues/24#issuecomment-3169625296 (opens external site)
Did this work for you?What @palasinio tried on GitHub (Partly worked)
After the maintainer updated manifest.json and the reporter had the updated version, the State-Tool worked on German Windows. The reporter then noticed the tool no longer asked for permission before acting.
Source: https://github.com/CursorTouch/Windows-MCP/issues/24#issuecomment-3192443295 (opens external site)
Did this work for you?What @Jeomon tried on GitHub (Outcome unclear)
Maintainer replied to the permission-prompt regression with: change the settings to ask for permission.
Source: https://github.com/CursorTouch/Windows-MCP/issues/24#issuecomment-3192470438 (opens external site)
Did this work for you?
Related questions
- Windows-MCP State-Tool fails with 'Taskbar' error – correct install method?
- How to fix Windows-MCP State-Tool vision error 'Tool result is too large. Maximum size is 1MB' on 2560x1440?
- Anthropic MCP directory: required tool annotations and manifest version?
- Windows-MCP times out MCP initialize handshake with Claude Desktop (-32001) on cold start
- Windows-MCP fails on Microsoft Store Claude Desktop with egg_base error from ${__dirname} path. How to fix?