spodermenpls

Thanks for reminding me of the Task Scheduler (didn’t open it in probably 10 years), I think I found the reasons: Fluxfonts was configured by default to only start if...

Well, well.. seems like correcting the settings did not solve it. I had multiple new crashes with the following error code, displayed in the Task Scheduler: "The process terminated unexpectedly....

I will re-install my Windows system when the Creators Update comes out, maybe that will solve things.

I didn’t have the chance to re-install Windows yet, that’s why I didn’t comment since. Fluxfonts itself runs without problems, the automatic startup (by the Task Scheduler, despite having corrected...

@da2x I finally found the time to install an all-new Windows 10 (Version 1709 - Fall Creators Update) on my system, but unfortunately it didn’t solve the issue of Fluxfonts...

@Atavic Fluxfonts does in fact start up, but crashes after some time (same issue as in November). Since it doesn't have a control panel, the only life sign I can...

@Atavic Kaspersky is granting Fluxfonts full access on the system, and even when I shut KIS down and disable the automatic start-up, the issue stays the same. Like I originally...

I think I've solved the mystery: I've taken the Scheduler settings of another program, that runs without crashing, for Fluxfonts (start with User account instead of SYSTEM, start with login...

Well, well.. mission failed after about 15 hours of runtime. I am running Fluxfonts as a service now (with NSSM: https://stackoverflow.com/questions/3582108/create-windows-service-from-executable/15719678#15719678), it works so far and should restart automatically now...

After 1 ½ years it's time for an update: Executing Fluxfonts as a Service is great, crashes - without an automated restart - are very rare (once or twice a...