Issue in 3.16.2 with qt6core.dll on Windows Server 2016- The procedure entry point SetThreadDescription could not be located

[DaHooka]

Hello all,

I tried to update 3.15.3 which works fine on Windows Server 2016 to 3.16.2. After that i can't start Nextcloud desktop as of the error:

The procedure entry point SetThreadDescription could not be located in the dynamic link library C:\Program Files\Nextcloud\Qt6Core.dll.

I assume it's related to the server version.

Just that you got aware of it.

[camilasan]

Hello, Can you reproduce the issue on Windows 10 or 11? We do not support Windows server.

[DaHooka]

Just curious as it was working on 3.15.3. Sorry have no win10/11 around

[mgallien]

can you test QtCreator latest release from Qt Company ? that would use the same Qt release the desktop files client is using. given Windows Server 2016 might be based on early WIndows 10 releases, it is well possible that some needed Windows APIs are missing

[volkswagner]

I get the same error on a fresh install of NC version 3.16.2 on Server 2016.

How can I resolve?

[nilsding]

FWIW, while looking at the Qt bug tracker I found QTBUG-134075 which references a fix for this for Qt 6.8.4 and 6.9.0 -- both of these Qt versions are not released yet.

So for the time being, 3.15.3 (which uses Qt 6.7.x that does not make use of SetThreadDescription yet) is the only option for Windows Server 2016...

[wiesty]

Is there a fix yet? Or a workaround?

[nilsding]

There is a fix in Qt versions 6.8.4 and 6.9.1, though neither are released yet. Once there are new releases available are we need to update our build pipeline to make use of these versions.

So for now the most realistic workaround is to stay on 3.15.3 for Windows Server 2016 until we can bump the version of Qt we use...

[FSRobot]

same here. OS version is Win10 1607(14393.0) Qt Version is 6.9.0

[nilsding]

looks like Qt 6.9.1 that contains the fix for these Windows versions is scheduled to be released next month: https://wiki.qt.io/Qt_6.9_Release

We plan to update the Qt version again in 3.17.0 -- in the case 6.9.1 is still not released by then I will try to backport that fix to our Qt 6.9.0 build.

[EchedelleLR]

So for the time being, 3.15.3 (which uses Qt 6.7.x that does not make use of SetThreadDescription yet) is the only option for Windows Server 2016...

3.15.3 has an issue in which client logouts when you close the session or reboot the machine. At least in Windows. 3.16.x did not have this issue so is basically exchanging an issue by another issue X3

[wiesty]

is this fixed in 3.16.4?

[nilsding]

@wiesty no, but we aim to have this resolved with 3.17.0.

The current plan for 3.17 is to bump the Qt version 6.8.3. The Qt build we'll use contains the patch which should fix that issue.

When we switch to the new Qt version for our daily builds I'll leave a comment here to let you know about it.

[nilsding]

We recently integrated the switch to Qt 6.8.3 with the patch that allows the application to start on Windows Server 2016. You can already test that by using a daily build >= 20250515, downloadable from here: https://download.nextcloud.com/desktop/daily/windows/

Please let us know if the build works for you.
Note that Qt 6.8 has changed the default font rendering engine. In the case the text looks off, you might want to try to start the client using the command line parameter -platform windows:fontengine=gdi (or -platform windows:nodirectwrite, both should have the same effect)

[fabiscafe]

@nilsding at least it starts again. it's however still not usable as it only displays tofu.

This is of today windows-20250519.msi, on WinServer 2016

[nilsding]

@fabiscafe thanks for the feedback :)

Can you try starting nextcloud.exe with the -platform windows:nodirectwrite CLI parameter set?

[fabiscafe]

… with the -platform windows:nodirectwrite CLI parameter set …

It works, text is readable again, @nilsding :)

[regrocsi]

Good afternoon. I’m experiencing exactly this issue when trying to run Nextcloud 3.16.5-x64 on Windows Server 2016 Standard. Should I use a daily build version as mentioned at some point by @nilsding ? Or is there already another solution available? Are these daily builds like beta versions — still under development?

[nilsding]

The 3.16.x versions will not work Windows Server 2016 due to the Qt version used, but 3.17.0+ will.

Until 3.17.0 is out you can use the daily builds. While those are built from the default branch (i.e. they're very much under development, bug reports are encouraged), these should generally be stable enough for daily use.

[regrocsi]

Thanks for the confirmation @nilsding . I downloaded a daily build (windows-20250609) and it opened. However, I noticed that during the initial setup there is no option for 'Use virtual files instead of downloading content immediately.' This option is similar to Google Drive's 'streaming file transfer,' which prevents local disk space from being used, as it doesn't download all content—for example, from a department’s shared folder that may contain many files. Is it possible to make this feature available in a daily build? I'm using the latest stable version of Nextcloud and doing some tests in a staging environment, as I plan to adopt it as a definitive solution

[nilsding]

Daily Windows builds contain VFS support.

The VFS functionality uses the Cloud Files API that's available on Windows versions >= 1709, so it won't be available on Server 2016 which has the version 1607.

[thowi84]

Hey there - is there already an estimated stable release date for the Windows Server 2016 compatible release? Thank you :)

[nilsding]

As 3.17.0 is already out I'm closing this issue now.