A bit of disassembling led me to a quick and dirty solution. The error message is only written if some value is set, which is set directly after ssleay32.dll is loaded.
By renaming “C:\Program Files\Pimax\Runtime\ssleay32.dll” into “_ssleay32.dll” seems to get rid of this problem. However, this leads to many “Warning: QSslSocket: cannot call unresolved function xyz” in the log.
But still better than nothing I guess.