Error when launching FAF after update(prerelease thingy)

[DrIvoRobotnik]

So, here's the story. I logged into FAF like usual, and a pop-up came up suggesting that I update to a stable prerelease thingy. (ending in rc.2 or something like that) Then while it installed I tabbed out to do something else for a little while as it did its thing. Shortly afterwards, it finished installing and I attempted to launch FAF as before, only this time I was confronted with the attached error message. I reset my computer tried again, and I received the same result. I do not know how to fix this issue, and I would appreciate assistance. If any other information is needed, I will be in contact. I can be reached through this forum, or preferably Discord.(I am on the FAF discord and my username is Taco_Grande) Thank you for your consideration!

[MobiusBE]

Hey man, I have no idea how to fix this, but I would like to point you to this topic where the same problem was stated:
http://forums.faforever.com/viewtopic.php?f=3&t=15610. One of the devs asked some question there to pinpoint the issue, but the original poster never answered, so maybe you can .

[Uveso]

i searched the forum and found this:

viewtopic.php?f=40&t=15695
viewtopic.php?f=3&t=15610

[DrIvoRobotnik]

Alright I've reviewed both of the previous threads you two listed (you both put down one of the same) and one of them said something about having a directory C:\Python36 or something like that. (which is apparently rarely needed) I do not have such a directory. Additionally one of them asks what version of the client I am using is in question, I don't remember exactly the title of the version I have, it was something like "stable prerelease rc.2". Hopefully this helps?

[DrIvoRobotnik]

Actually, I do have a Python36 zip file in the faf folder, if that makes a difference.

[Wesmania]

The problem is with missing Qt libraries - figuring out which ones we need to pack for things to work is guesswork, AND you have to worry about some things still missing in rare cases that we didn't encounter. I'll prepare some instructions for you to pinpoint the issue - it's basically going to be a 'copy libraries and files from that zip until things start working'

[DrIvoRobotnik]

I understand copy paste pretty well, just tell me where the things that I need to try are, and where to move them, and I can tell you which one fixes the issue.

[Wesmania]

Alright, here are the rough steps:
1. Download the PyQt5 package from https://pypi.python.org/pypi/PyQt5/5.9.2 - you want PyQt5-5.9.2-5.9.3-cp35.cp36.cp37-none-win32.whl.
2. Rename the extension to zip and extract the archive.
3. Various Qt libraries and files in the archive are kept in various directories in ./PyQt5/Qt in the archive.

You'll need to try and dump them into your FAF installation directory - you can consult our installation script at https://github.com/FAForever/client/blo ... pveyor.yml, at lines 27 to 42 are the libraries and files we currently copy to the FAF install dir. From there it's mostly a tedious game of backing up your original FAF install dir and adding libraries until you pinpoint the ones that are needed to make things run for you.

And now that I look at it, it seems we copy dlls from another python package too. If dumping all dlls and resources from PyQt5 isn't enough, try dumping all dlls from https://github.com/FAForever/python-whe ... -win32.whl, too.

I'm sorry for having to put you through this stuff - we tested this for as many Windows installations as we could, but some rare cases still slipped through

[ZOB]

ok, i had exactly the same error i think, solved by uninstalling faf and reinstalling.
i also uninstalled downlords client as i had recently installed that in case there was some kind of conflict, but i'm a paranoid and pedantic kind of guy, try leaving downlord's if you have it and see what happens.

yeah it was the same error viewtopic.php?f=3&t=15601

[Wesmania]

It sounds to me like, in the meantime, you installed something that added whatever library you were missing to system directories. I wish it was easy to figure out which one it was