Program freezes entirely and instantly if any firewall triggers an Action Center notification toast (tested with Windows Firewall, Symantec, etc on three different systems using different hardware). If toasts for firewalls are disabled entirely, this event will not occur. Probably a Win10 bug triggered by the change to the Action Center in the Anniversary Update.

Program does not exit gracefully at all (executable runs into some sort of error where it refuses to obey uxClose/Terminate thread instructions and requires a system reboot for the process to actually terminate before it can be re-opened, logging out the user and logging back in does not remedy, only a system restart). When trying to terminate the "frozen" thread manually, it leads into an infinite "Access is Denied" loop as Windows already views the zombie thread as having terminated even though it is still sitting there taking up resources and blocking any meaningful reload of the program (The program will start under a new PID, etc, but no UI will load thus making it entirely useless). This happens no matter how you attempt to terminate the program (Normal exit, Alt+F4, Process Explorer and the like).

Adding magnet links can lead to the program UI freezing entirely during the checking phase if part of the files have already downloaded.

This all being said, I will attempt to use the alpha version of 2.44 and see if any of this sorts itself out.

(executable runs into some sort of error where it refuses to obey uxClose/Terminate thread instructions and requires a system reboot for the process to actually terminate before it can be re-opened, logging out the user and logging back in does not remedy, only a system restart).

I've found this exact problem as of late. Killing the tixati.exe thread does not solve the problem, nor does logging out. It sits in a frozen deadlocked state of somesort. A reboot is the only thing I've found that lets tixati run normally again.

I am using 2.44 A1 and have no problems with W10 AU (other than the known ones with 2.44 A1).

D.

Running Tixati v2.44a1 in a Win7x64 virtual machine. The freezes you are seeing are just like mine. Tixati's GUI freezes, and no longer responds. The thread cannot be killed via task manager or procex, it gives a "Access is Denied" over and over and refuses to die. Logging out the virtual machine and loggin in shows the tixati.exe thread still frozen and unkillable. "Force Killing" with the visual studio debugger causes a bluescreen. Only solution to launch tixati.exe again is a full reboot. This has happened to me about once or twice per week on average, and the bug existed in 2.43 as well. There is no virus scanner/firewall on the Win7 virtual machine and nothing that could be impeding with its operation. Out of morbid curiosity setup a Win10 virtual machine, stripped defender/firewall and all Win10isms, and sure enough after several hours of downloading I came back to find the tixati window frozen and unkillable as similar to my Win7 virtual machine. Doesn't appear to be Windows version depedant.

I also am on 2.44 alpha 1 on Windows 10 x64 and have no issues with this.  Guest, try updating to the alpha and report if your issue continues.

what do the diagnostic graphs look like? they are under help->diagnostics.

you can post links to pics or send them directly to devs. support@tixati.com

are there any strange settings in the layout menu?

Tixati has become unusable for me the last while, with constant freezes and crashes, even after a fresh reinstall on multiple seedboxes. v2.38 appears to be the last 'stable' version of Tixati, as it's the latest version that I can come back to the next day and not find it frozen.