[Bug]: CKAN crashes on start after installing Windows 11's KB5036893 update
zhangyuesai opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
Operating System
Windows 11 23H2 (22631.3447)
CKAN Version
1.34.4
Games
KSP 1
Game Version
1.12.5.3190
Did you make any manual changes to your game folder (i.e., not via CKAN)?
No
Describe the bug
After I installed Windows 11's KB5036893 update (version 22631.3447), CKAN crashed immediately on start.
I uninstalled that Windows update and CKAN started properly.
Steps to reproduce
- Install Windows 11's KB5036893 update
- Launch CKAN
- CKAN crashes immediately on start
Relevant log output
No response
Hi @zhangyuesai, we'll need some information about the crash to investigate this. Is there an error message? Can you describe what you see? Can you share a screenshot?
Hi @HebaruSan , it's really weird. I reinstalled the Windows update to take a screenshot but the issue was gone. However, after I reboot the computer the issue occurred again, and another rebooting could make it gone again. I'm pretty sure the issue occurs only when the Windows update is installed, but I can't 100% reproduce it.
Does CKAN have a log file and where can I find it? I could provide the log if the issue occurs again.
Here's what I see when the issue occurs:
- Run CKAN.
- The console and the GUI show up.
- Process
ckan.exe
shows up in the Windows Task Manager, too. - The console and the GUI disappear on "Loading registry...". Silently, no error message.
- And process
ckan.exe
disappears, too.
Attached is a video about the issue. I couldn't change my system language to English; the message showed on the GUI before CKAN crashed was "Loading registry..." or something like that. The Task Manager is on the right side of the screen.
ckan-crashes-on-start.mp4
@zhangyuesai, yes, if you open a terminal window and cd
to the folder where ckan.exe
is, you can run ckan --debug --show-console
to see the logging. This should at least allow us to guess the last few things that happen before it closes, and if we're lucky, it may show an exception being thrown.
Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automatically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it!