Client: No Qt platform plugin could be initialized. Windows Client

[timetofaceit]

Hello,

I have compiled the client for windows from open source. On my PC client is starting and working normal as it should. If am trying to launch the bin directory from the other PC I get this error:

I used windeployqt from this link -> https://doc.qt.io/Qt-5/windows-deployment.html#the-windows-deployment-tool but still getting the same error.

My bin folder looks like this:

Any ideas?

[dschmidt]

What's the content of platforms/ folder?

[timetofaceit]

@dschmidt thank's for the quick answer.

Platforms folder:

[dschmidt]

Maybe try to create a qt.conf file in the root application folder with the following content:

[Paths]
Plugins = .

Compare https://doc.qt.io/qt-5/qt-conf.html

[timetofaceit]

@dschmidt thank's it works. I created that qt.conf file in platforms folder with your given content.

[dschmidt]

Neat! :tada:

FTR I'm currently updating the windows build instructions: https://github.com/owncloud/client/pull/7035
But glad you could make it work too :-)

[qasimali-byte]

https://www.youtube.com/watch?v=9eyNNkxYvEA

[esackbauer]

I am suddenly experiencing this exact error when I logon to Windows and OwnCloud Client is automatically started.
If I start Owncloud client manually, there is no problem.

It is happening since version 2.7.2
2.7.1 was ok.
Running on Windows 10 20H2.

Edit: Now I am puzzled, it seems the latest update installed owncloud client to the C:\ root folder.

[michaelstingl]

@esackbauer this issue is about self-compiled ownCloud Win builds. Do you use self-compiled ownCloud desktop client, or one downloaded from ownCloud website?

[esackbauer]

Its the one downloaded from the website.

[esackbauer]

Ok, its all sorted now. I uninstalled ownCloud client, removed any traces in the file system, rebooted, and then did a clean install.
Now it properly installed into c:\program files\owncloud as its supposed to.
Also the qt error during startup is now gone.

[Tomino-RI]

Hi esackbauer!
Thank you for sharing how you solved your problem.
I have the same problem as you had. Mine ownCloud client is also installed on C:\ root folder and is version 2.7.3
Do I have to synchronize again all data after I uninstall and perform new installation of ownCloud.
I mean, do I have to copy again all data from cloud to my computer or new installation of ownCloud will recognize structure of folders which were synchronized before?

[esackbauer]

Actually this happened again to me, when updating to 2.7.3! It seems something is wrong with the update procedures.
I uninstalled 2.7.2, and downloaded 2.7.3, all settings were taken over, no need to sync again.

Which version of Windows are you on?

Can someone reopen this? Or do we need to file a new issue?

[Tomino-RI]

Thank you for your fast reply.
I am on Windows 10 Pro version 1909.
If I have understood well, the problem is still there, but you did not need to sync again.

[dschmidt]

I'm sorry for the inconvenience with the installation to C:/.

This happened when your initial install of the client was from the 64bit MSI and then the autoupdater installed the 32bit version for you.

This was reported in https://github.com/owncloud/client/issues/8297 and fixed since then.

The autoupdater now correctly updates 64bit installs to 64bit binaries, so this won't happen automatically anymore.

Moreover 2.7.4 will contain a fix so that manual downgrades to 32bit will fallback to [ROOTDRIVE]Program Files (x86)/ownCloud.

[Tomino-RI]

Dear dschmidt,

Thank for your reply and this information!
This inconvenience with the installation to C:/ is not so serious. It is more important that ownCloud function properly 👍
I am again nicely surprised and thankful for help I get from internet community.
Thank you guys! 👍