cx_freeze / importerror: dll load failed

[GS_]

I just installed with the intent of checking out FAF, but when I attempted to launch the client, I got the error in the attached image.

I've searched exhaustively but found no solutions to this problem. I'd appreciate any help since I'm eager to start getting utterly destroyed.

[Wesmania]

This is a problem with the Python client installer - unfortunately we have to make a guess which libraries to include in it so that the download does not become too large, and we seem to have missed a couple libraries that, in some rare cases, aren't installed on the host.
I can prepare an installer for the Python client for you in a few hours that has more libraries included. In the meantime, you can try the alternative Java client from the download page.
If you're patient enough for some more testing, I'd love to identify precisely which library is missing - this would help us fix this problem for good. This would basically mean dropping libraries one by one into the installation directory until we find the one that was causing the priblem.

[GS_]

It doesn't seem like a common issue, but if you're into solving it in that fashion, I'll certainly help. Let me know which libraries to start trying.

[Wesmania]

Okay, here are the instructions:

1. Grab this file.
2. Rename the extension from .whl to .zip and unpack it.
3. Navigate to PyQt5/Qt/bin.
4. All potential dlls we might need are here.

These dlls should be dropped to the client installation directory (wherever other dlls are, I believe it's the root folder). You can try dropping them all in first to see if the issue goes away, if you don't mind reinstalling the client afterwards to clean up. Other than that, it's just a matter of dropping libraries until things work.

If it still doesn't work, then try the same thing with libraries from here.

[GS_]

One at a time, I copied in every .dll and every .pyd, from both sources, and tried to launch after each addition. No dice. Entirely possible that I misunderstood something because I'm retarded.

[Wesmania]

I'll try to dig into pyqt code then, maybe I can figure out which specific library is missing. Also many thanks for helping with debugging, few people have the patience for this

[Wesmania]

I looked around a bit - it seems that I can't really tell which dll is missing from the debug message alone, and there's nothing I can put into the Python client to get more info about it. If you still want to pursue the issue, then we'll have to trace the client process to figure out which libraries it's attempting to open.
This article describes how to trace an executable using Process monitor. If we can run it and get logs out of it, it might point us to the missing library.

[GS_]

The filters in the example (which were more extensive than the "comprehensive" screenshot) screened out all results for some reason, so I had to fiddle a bit. Eventually I wound up with 207 items. About half are "file locked with only readers," with the remainder as "name not found" and only two "path not found." Link to the .PML log: http://www.mediafire.com/file/x3n8q2r9t ... ogfile.PML

Also, glad to help. It's heartening to see dev dedication to a project like this considering the ubiquity of half-assed slackery.

[Wesmania]

Okay, after some additional filtering I narrowed the culprit to a handful of libraries, among them mostly some Windows DLLs as I expected:

dlls.txt

(2.74 KiB) Downloaded 58 times

I think the most likely culprit is api-ms-win-core-path, though it might be one of others, too. You'd have to search your windows directory for these DLLs. If they are there, then this should be a way to make Windows aware of them:
https://community.spiceworks.com/topic/ ... is-missing
If not, then perhaps your Windows installation borked something and some DLLs are missing. You'd have to look for them on the web - ignoring all the shady "dll free download" sites of course :/

[GS_]

Either I don't have the .DLL you suggested, or it's hidden somewhere that didn't show up in a search on C:/ (albeit one that finished suspiciously quickly).

I attempted the regsvr32 /u on both that .DLL and the one I wound up downloading after looking online (api-ms-win-core-path-l1-1-0.dll) which was the closest I could find. "File not found" errors for both.

I had tried sfc /scannow before posting here, but I tried it again anyway—to no avail. (My file browsing seems to be a little faster now. Could be a coincidence.) The result: some problems were fixed, but others couldn't be addressed for whatever reasons. The resultant log file is extensive and I have no idea how to interpret it. (In case it would be of any use, I've attached it.) (I had a worrying thought: what if my cached .DLLs are faulty?)

I honestly hadn't thought of trying to run the program from a different account. For the sake of science I might give that a go.


A couple times I've been asked why I don't try to get into programming.
This.
This is the reason.
I'm certain you're all quite mad.