Skip to content

assertion failed: flush_paint_messages - cc-switch crash

Quick fix

Upgrade cc-switch to the latest version for the underlying GUI framework crash fix, or try closing proxy software and resetting the network.

Error output
assertion failed: flush_paint_messages(None, &subclass_input.event_loop_runner)

An assertion failure caused by an event loop handling anomaly in tao, the GUI framework underneath cc-switch, on Windows.

Per user reports, on Windows 11 this crash can trigger randomly when certain proxy software is enabled (v2ray, for example) or when the DPI changes. Maintainers confirmed the problem and merged a fix PR.

  1. Update cc-switch to the latest version. Maintainers confirmed the crash is fixed in the new version.

  2. If it still crashes after updating, close all proxy software and stop it starting automatically, run `netsh restart network` on the command line, then restart the machine.

  3. Once the machine has restarted and cc-switch works again, if you still need a proxy, try changing the proxy software network mode to avoid the conflict.

Toolcc-switch
Version3.10.2 - 3.11.1
PlatformsWindows
I have to use a proxy and cannot leave it off. What can I do?
Resolve the crash first by turning the proxy off and restarting the machine. Once cc-switch opens normally, try changing the proxy software network mode — proxies offer several network-layer modes, and changing it usually avoids triggering the crash again.
Is there a version known not to have this problem? I want to roll back.
Maintainers stated plainly that the crash is fixed in the new version, so update to the latest rather than rolling back.

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.