Client stuck on black screen

[kojiinari]

Describe the bug
Desk client won't launch, only launches black screen with a white bar across the top. This persists even with killing the background process in task manager
To Reproduce
Steps to reproduce the behavior:

1. Launch App
2. Close app
3. Relaunch app
4. Black screen appears

Expected behavior
App should launch and display chats

Screenshots

Additional context
Prior to this showing, rooms with updates weren't being marked as read. I closed the client and reopened it, and now it won't get past this black screen. Other clients like Cinny Desktop and Commet Mobile (Android) are loading properly.

I am running on Windows 11 25H2 build 26200.7623

Interestingly notifications are coming in as I get the Windows toast notification, just the app won't display them.

Device Information

Device
Platform: windows
Version: v0.4.0
Git Hash: c8ea1249d0ec05582fc007b247c5b83fe9ce72f6
Detail: default
Build Timestamp: 1770025852237 (February 2, 2026)

System Info

[kojiinari]

This issue resolved itself. I closed the program for roughly an hour, and went to re-open it and it loaded like normal. Logs started when the client started up again, so nothing to indicate what happened. Closing.

[kojiinari]

After rebooting my computer, I am once again back to the black screen every time I open the application.

[kojiinari]

Continuing to test on this - if i fullscreen the client, and then end the task in the task manager, I'm able to bring it back from the black state. Still haven't determined what causes it to get into the black state in the first place, but I suspect it might be window size?

[FynnleyNeko]

Check if this is the same as #674

[kojiinari]

Check if this is the same as #674

This does look like the same issue, but I can't seem to reproduce it at will, so I'm still not sure what gets it into that state. Next time it happens I'll double-check to see if it's also eating up the CPU like in that post.

[kojiinari]

okay I can confirm there is no CPU spike from Commet on my version of this issue.

I can also confirm that this is something to do with window sizing, and might be specific to use with powertoys
I think perhaps forcing the client to a smaller than default window size can get it into this state. I use powertoys to set up fancyzones on my desktop to keep my applications in specific sizes - when locked to the side of my screen in the zone I created, it is fine until the client is closed. re-opening it re-opens it in that zone and causes the black screen.

Changing the size of the client to the default size, waiting a minute or two, and then killing the client process causes it to re-launch un-docked to the zone, and with the text drawing properly.

This leads me to think that the app simply doesn't like being resized below a certain threshold (or doesn't like launching docked to a pre-determined size).

What tipped me off was after moving the app to another zone and then relaunching it, it was completely white instead of black - and fullscreening the app caused the size of the zone to be white, and the rest of the app to be black, similar to what was being shown in #674

Replication Steps:

1. Using powertoys set up a window zone that is relatively small (see below example on a 2560x1440 screen)

2. Dock the commet client to that zone (Shift+ Drag to the zone, if using power toys)
3. Close the commet client
4. Relaunch the client - you will see a black and white screen

5. undock the commet app to bring it back to a normal size (drag it outside the zone, and it will pop back to its original size)

6. Close the app and re-launch it and it will recover and even re-launch in the zone and be fine.