QGIS » QGIS Application

Thank you Giovanni - no, I do not have another machine. All earlier QGis versions never showed this problem. In case this is a local issue - how could I fix it? I still have 2.18 installed but since the error messages are about .dll's in specific QGis 3.0-paths this shouldn't matter.

I have the same problem on Windows 10 1709.
We have the same error under 1703.
QGIS is installed via an automatic software installatoin system with user "System".
The installation parameter is "QGIS-OSGeo4W-3.0.0-3-Setup-x86_64.exe /S /NCRC".
The installation is finished as successful, but after the first start via a user with or without admin rights the error is that the dlls are corrupt.
If QGIS is installed manually there are no errors.

Thank you Bastian - how do I "install QGis manually"?

Hello Markus

i normaly start QGIS-OSGeo4W-3.0.0-3-Setup-x86_64.exe on the pc and installed it over the setup. But we want to install QGIS on several computers at the same time. So we are confused why the error happened.

I also used the normal windows installer. The problem remains with the newest version 3.0.1. I cannot start/use QGIS 3.

Markus Urbscheit wrote:

I also used the normal windows installer. The problem remains with the newest version 3.0.1. I cannot start/use QGIS 3.

Check for DLLs in %WINDIR%\system32 that are also in QGIS' PATH (esp. %OSGEO4W_ROOT%\bin and %OSGEO4W_ROOT%\apps\qt5\bin). If there are any removing them will probably fix the issue (but might break the package that put them there).

"but might break the package that put them there" - sorry do not understand this. What is QT5? What other potential package are your talking about? Might this affect/break other programs than QGis that use these dll's or just previous versions of QGis? So essentially: what is the risk of doing this? Thanks in advance for explanation. But this cannot be a long term solution for normal unexperienced users - digging out and deleting files deep in the system... There must be an automized mechanism to solve this in the long term, otherwise people will just feel helpless and stay with version 2.18.

Markus Urbscheit wrote:

"but might break the package that put them there" - sorry do not understand this. What is QT5?

The toolkit we use

What other potential package are your talking about?

No idea. It shouldn't have put the DLLs there in the first place.

Might this affect/break other programs than QGis that use these dll's or just previous versions of QGis?

It will only break other programs - those which expect their DLLs in system32. Unfortunately windows always prefers DLLs from system32 to over anything that is in PATH.

So essentially: what is the risk of doing this? Thanks in advance for explanation. But this cannot be a long term solution for normal unexperienced users - digging out and deleting files deep in the system... There must be an automized mechanism to solve this in the long term, otherwise people will just feel helpless and stay with version 2.18.

Feel free to suggest one.

Thanks very much Jürgen for your quick reaction and help - I apreciate it! So it would be probably be quite safe to keep a backup of the dll's, try out and see if something happens to other programs. I'll do this later on when I have more time.

Have a great day

Markus Urbscheit wrote:

Thanks very much Jürgen for your quick reaction and help - I apreciate it! So it would be probably be quite safe to keep a backup of the dll's, try out and see if something happens to other programs. I'll do this later on when I have more time.

Have a great day

please help us with a solution, possibly not have time, but I would be very grateful if you help me, otherwise I will have no choice but to stay with the 2.xx

BYRON BRAVO wrote:

please help us with a solution, possibly not have time, but I would be very grateful if you help me, otherwise I will have no choice but to stay with the 2.xx

Like? Did you find conflicting DLLs in system32?

Markus Urbscheit wrote:

"but might break the package that put them there" - sorry do not understand this. What is QT5? What other potential package are your talking about? Might this affect/break other programs than QGis that use these dll's or just previous versions of QGis?

yes, but those programs should not have placed any DLL in WINDIR\system32 in the first place (contributing the the well known "DLL Hell", that you are experiencing). Blame the others in this case, not QGIS.