BehaviorTree
Unable to launch on Windows 11
Describe the bug
The most recent version (1.6.1) is unable to launch on my Windows 11 machine. Nothing happens after the splash screen disappears, except for the following entry that is generated inside groot2.log:
Fatal: Mon Jul 22 15:11:47 2024 - Cannot mix incompatible Qt library (6.5.3) with this library (6.6.1)
How to Reproduce
- Download the Windows installer
- Install Groot2 with the default installation settings
- Execute Groot2
Desktop
- OS: Windows
- Version 11 Pro N (23H2 - 22631.3880)
I am running into the same behavior on Windows 10 Enterprise. Additionally I noticed that the entry in the start menu is not created. After the splash screen disappears nothing happens.
Where can I find the groot2.log? Happy to provide more details.
I have find a way to work around this issue, my winver win 11-25H3
🧩 Fix for “Cannot mix incompatible Qt library (6.5.3) with this library (6.6.1)” when launching Groot2 on Windows
If you try to launch Groot2 on Windows and it shows the splash screen but never opens — and the log says:
Fatal: Cannot mix incompatible Qt library (6.5.3) with this library (6.6.1)
— this guide explains why and how to fix it.
🧠 Cause
Groot2 already includes the correct Qt runtime (6.6.1) inside:
C:\Program Files\Groot2\bin
However, some other applications on your system — for example:
-AMD Ryzen Master
-AMD Adrenalin / CNext
-Perforce (P4V / P4Merge)
-VMware Workstation
-Cursor IDE
— also install their own Qt DLLs (often version 6.5.3) and automatically add their folders to the system PATH.
When Windows starts Groot2, it loads those older Qt DLLs first, before the ones inside Groot2’s folder. That version mismatch (6.5.3 vs 6.6.1) causes the application to crash or remain invisible in Task Manager.
✅ The Reliable Fix: Launch via a .bat File
The only 100% consistent way to fix this is to launch Groot2 in a clean environment where it can only see its own Qt DLLs.
🧩 Step-by-Step
Create a new text file named RunGroot2.bat (for example, on your Desktop).
Paste the following lines inside:
@echo off setlocal rem === Launch Groot2 with a clean PATH that includes only its own Qt runtime === set PATH=C:\Program Files\Groot2\bin cd "C:\Program Files\Groot2\bin" start groot2.exe endlocal
Save the file.
Right-click → Run as Administrator
Groot2 should now open normally, with the full UI visible.
🧩 Why this Works
The .bat script creates a temporary environment for that process only:
Windows ignores the global PATH.
Only DLLs from C:\Program Files\Groot2\bin can be loaded. *No AMD / Perforce / VMware Qt libraries can interfere. *That’s why the batch file works even if changing your system PATH didn’t.
