QML debugging no longer works (Could not connect to the in-process QML debugger. Do you want to retry?)

[parteimeister]

After recent updates of Windows, my QML debugger stopped working with the error "Could not connect to the in-process QML debugger. Do you want to retry?".
This problem is present in Windows 11 and Windows 10.
In the "General Messages" tab I have messages like "LanguageClient Qmlls (C:\Qt\6.8.1\msvc2022_64\bin\qmlls.exe): The command "C:\Qt\6.8.1\msvc2022_64\bin\qmlls.exe" terminated with exit code 1. (see logs in "C:/Users/User/AppData/Local/Temp/QtCreator-rDvXvi/lspclient.oyaMXm.log")", but the specified log file does not contain any useful information:

Starting server: C:\Qt\6.8.1\msvc2022_64\bin\qmlls.exe
Output:

I tried to install the latest Qt and Visual Studio on an old computer that hadn't been updated for a couple of months (OS Windows 10). The debugger works there, so the problem is definitely in the incompatibility of the latest versions of Windows and Qt.
Enabling and disabling QML Language Sever has no effect.
The problem occurs regardless of the selected compiler (MSVC 2022, MinGW, etc.)
Disabling the built-in antivirus and firewall also has no effect.

[parteimeister]

I got even deeper into the problem. It turns out that if the "Default for "Run in terminal"" option is enabled (Edit - Preferences - Build & Run), then this error will occur. Everything returns to normal if you disable this option.

[Antony007]

I am facing the same issue too

[linxi]

I am facing the same issue too

[parteimeister]

God bless ChatGPT!

ChatGPT suggested me to clear Qt Creator cache (%APPDATA%\QtProject\QtCreator) as a solution, and it worked!

[parteimeister]

I got even deeper into the problem. It turns out that if the "Default for "Run in terminal"" option is enabled (Edit - Preferences - Build & Run), then this error will occur. Everything returns to normal if you disable this option.