Newest version 1.6.10 causes immediate crash

[morthein]

Description

Updated to new version as of some 13 hours ago of this message, and it causes the game launcher to crash without opening anything else.

To Reproduce

1. Start launcher.

Expected behaviour

Normal startup and then proceeding to the UI window showing the most recent updates.

Screenshots

No response

Attempted Fixes

Ran in admin
restarted PC after updating
ran CDDA.exe separately and it's not the game, just the launcher/updater itself.

System Details

windows 11 - latest build
CDDA version up to day as of 5 days ago.

Additional context

Previous to this update, things worked flawlessly.
Note: I redownloaded 1.6.9 and reinstalled and the launcher works perfectly. Something in 1.6.10 my system doesn't like or is botched.
It never gets past running the batch file (no UI) but closes in less than a second after attempting to open.

[morthein]

It doesn't show that I updated it to 1.6.10 since it crashes immediately, but it does show recently that I installed 1.6.9 and ran it (around noon EST) as shown in the last entry. I even tried reinstalling the 1.6.10 and rerunning it and it just opens and immediately closes without logging in the 'app' file.

…

________________________________ From: Leon ***@***.***> Sent: Tuesday, March 14, 2023 11:27 AM To: DazedNConfused-/CDDA-Game-Launcher ***@***.***> Cc: morthein ***@***.***>; Author ***@***.***> Subject: Re: [DazedNConfused-/CDDA-Game-Launcher] Newest version 1.6.10 causes immediate crash (Issue #89) I tried downloading the new installer in a new Windows Virtual Machine and no crash occurred. You might want to include your log file content here. Try locating the log file at "C:\Users<username>\AppData\Local\CDDA Game Launcher\app.txt". — Reply to this email directly, view it on GitHub<https://github.com/DazedNConfused-/CDDA-Game-Launcher/issues/89#issuecomment-1468318696>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMD5VLFT6RLP7FGYOW2PNC3W4CE7VANCNFSM6AAAAAAV2NJ4FE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[DazedNConfused-]

Well that's certainly odd. Using a Windows 11 VM I was able to run the launcher with no hitches. Is anyone else experiencing this issue? Any other details that could be provided in order to diagnose the issue?

[loeuekken]

Had the same problem. On Win10, German localization, updated to 1.6.10 today and the launcher did not start anymore.

This was the error I got for a fraction of a second:

And this was my solution:

Worked then

[morthein]

I just made the adjustments and it works. :) yay thank you.

[DazedNConfused-]

Another day, another timezone bug. Will put this in the backlog

[TadhgEomonn]

Had same problem. loeuekken's solution worked for me also.

Thanks.

[Stadler76]

Took me like two hours of installing and uninstalling every permutation of python 3.9 and 3.10 in both 32bit and 64bit versions because I got a lot of could not load xyz32.dll / could not load built in python module blah-yadda in xyz.py till I gave up and downgraded to 1.6.9 yesterday.
Tried again today with the fix above (I tried yesterday too, btw.) and it worked like a charm. Thanks for that.

Long story short: Running python.exe -m cddagl manually in Powershell taught me again, that it's a bad idea to try to run commands made for the commandline in PS.
Just FYI in case someone else tries to repro the error message in Powershell instead of the commandline and gets a mild headache.