[BUG] Will not start

[oleljos]

Is this a bug in companion itself or a module?

• [x] I believe this to be a bug in companion

Is there an existing issue for this?

• [x] I have searched the existing issues

Describe the bug

Try to start companion and it's stop.

getting this ot of the LOG:

2024-10-13T17:40:07.688Z Application: Companion process started 2024-10-13T17:40:08.959Z Application: Companion exited with code: 3221225478 2024-10-13T17:40:08.959Z Application: Restart Count: 1 2024-10-13T17:40:10.525Z Application: Companion exited with code: 3221225478 2024-10-13T17:40:10.525Z Application: Restart Count: 2 2024-10-13T17:40:12.089Z Application: Companion exited with code: 3221225478 2024-10-13T17:40:12.089Z Application: Restart Count: 3 2024-10-13T17:40:12.881Z Application: trigger companion restart 2024-10-13T17:40:12.881Z Application: Companion process stopped 2024-10-13T17:40:12.980Z Application: Companion process started 2024-10-13T17:40:13.472Z Application: Companion exited with code: 3221225478 2024-10-13T17:40:13.472Z Application: Restart Count: 4 2024-10-13T17:40:14.746Z Application: Companion process stopped 2024-10-13T17:40:14.845Z Application: Companion process started

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

• OS: Windows 10 Pro
• Browser:
• Companion Version: 3.4.2

Additional context

No response

[Julusian]

Do earlier versions launch? Maybe try 3.3 and 3.1. I'm wondering here if this is something we broke in the latest release or a long time ago.

Is there antivirus on your machine that could be blocking it? Or is this a corporate machine where they might be adding restrictions which cause this

[oleljos]

3.1 is working, did not try 3.3. there is non added antivirus program to the machine, and it's not a corporate machine

[Julusian]

I've added a library that will log certain crashes that wouldn't have been logged before. It's only in the betas for now

If you're willing to try running that and sharing the log that it produces, that should help narrow down the cause of this

[oleljos]

it's look like its the same log... i downloaded "companion-win64-3.5.0+7491-main-cbe6c31e.exe"

and i got this log now:

2024-10-25T14:19:34.830Z Application: Companion process started 2024-10-25T14:19:35.299Z Application: Companion exited with code: 3221225478 2024-10-25T14:19:35.299Z Application: Restart Count: 1 2024-10-25T14:19:36.848Z Application: Companion exited with code: 3221225478 2024-10-25T14:19:36.848Z Application: Restart Count: 2 2024-10-25T14:19:38.385Z Application: Companion exited with code: 3221225478 2024-10-25T14:19:38.385Z Application: Restart Count: 3 2024-10-25T14:19:39.938Z Application: Companion exited with code: 3221225478 2024-10-25T14:19:39.938Z Application: Restart Count: 4 2024-10-25T14:19:42.729Z Application: Companion process stopped 2024-10-25T14:19:42.841Z Application: Companion process started

[Julusian]

What version of windows 10 are you running?

Im struggling to think of what the problem could be, or how to go about diagnosing this

[ericbusby77]

I was having a similar issue for a couple of weeks with betas on my RPi, too. But then one day it worked (somewhere around 3.5.0+75XX) and betas have been working since.

[oleljos]

What version of windows 10 are you running?

Im struggling to think of what the problem could be, or how to go about diagnosing this

[Julusian]

Is this still a problem with the 4.0 releases or 4.1 betas?