New Hybrid install on Windows 11

[Miranda]

I've just got another PC that's running Windows 11. My first Hybrid install (Hybrid_dev_2026.04.27-194143) on this PC fails to launch and reports "GetTool Versions got an empty output for vspipe. The cause might be that vspipe could not be found... Please redo this with debug output enabled and tell the author."

Any suggestions?

[Selur]

Strange, Hybrid should detect Vapoursynth under: ".\64bit\Vapoursynth\Lib\site-packages\vapoursynth\vspipe.exe"
You didn't load old settings, right?
Does this also happen with the latest dev? (make sure to deinstall Hybrid beforehand)

Cu Selur

[Miranda]

Same error with latest dev version.

[Selur]

Is vspipe properly detected under ".\64bit\Vapoursynth\Lib\site-packages\vapoursynth\vspipe.exe" ?

[Selur]

Strangely, I can't reproduce this here. (I installed Hybrid_dev_2026.05.13-17173 just now, and it properly detected vspipe's version.)
Do you have any virus scanner running aside from Windows Defender or MalwareBytes?

Cu Selur

[Miranda]

Nothing, I only just got the PC.

[Selur]

Really strange.
I built a Hybrid version which starts with a terminal window.
If you replace the Hybrid.exe with the one in the attachment, can you share the output it shows in the terminal. (Terminal content can be exported to a .txt file)

Cu Selur

[Miranda]

It runs the terminal window but quits when it gets to loading vpipe, so I can't save any details.

I'll see if I can film it on my phone.

[Selur]

Try, opening a terminal window in you Hybrid-folder, and call Hybrid.exe from there. This should put the output in that terminal.

Also, what happens if you call:

"c:\Programs\Hybrid\64bit\Vapoursynth\Lib\site-packages\vapoursynth\vspipe.exe" --version

inside a terminal window?
The expexted output would be:

VapourSynth Video Processing Library Copyright (c) 2012-2025 Fredrik Mellbin Core R75 API R4.2 API R3.6 Options: -

Cu Selur

[Miranda]

I tried running the Terminal Hybrid again and now I see:

"The code execution cannot proceed because Qt6Gui.dll was not found. Reinstalling the program may fix the problem."