describe the bug
Upon a fresh restart of my desktop, Screenpipe will open with a recording status and then immediately switch to red. Rebooting the software from tray or task manager do not seem to fix it. Logs report that the port is busy.
I looked at my port usage with netstat and the only thing occupying port 3030 is a Docker process with a Screenpipe parent. I've tried killing the process, rebooting Screenpipe, and rebooting Windows 11 and this happens everytime. If I run via CLI with a custom port, it will work briefly before finding the same error.

system info

• os: windows 11
• screenpipe version: 0.2.23

additional context
add any other context, screenshots, or error logs here.

In the CLI, I enabled verbose Rust backtrace logging and this is what I get:

�[2m2025-01-06T11:18:24.460216Z�[0m �[32m INFO�[0m �[2mscreenpipe_audio::core�[0m�[2m:�[0m starting continuous recording for Realtek Digital Output (Realtek(R) Audio) (output) (30s segments)
thread '' panicked at D:\a\screenpipe\screenpipe\screenpipe-audio\src\core.rs:474:22:
Failed to build input stream: BackendSpecific { err: BackendSpecificError { description: "0x88890008" } }
stack backtrace:
�[2m2025-01-06T11:18:24.470478Z�[0m �[31mERROR�[0m �[2mxcap::platform::utils�[0m�[2m:�[0m GetFileVersionInfoSizeW error: WIN32_ERROR(1813)
0: 0x7ff6c4cd54e3 - onig_get_right_range_by_callout_args
1: 0x7ff6c47681ea - onig_get_start_by_callout_args
2: 0x7ff6c4cb2497 - onig_get_right_range_by_callout_args
3: 0x7ff6c4cd6f85 - onig_get_right_range_by_callout_args
4: 0x7ff6c4cd6dbd - onig_get_right_range_by_callout_args
5: 0x7ff6c4cd73ba - onig_get_right_range_by_callout_args
6: 0x7ff6c4cd7069 - onig_get_right_range_by_callout_args
7: 0x7ff6c4cd6fbf - onig_get_right_range_by_callout_args
8: 0x7ff6c4cd6fae - onig_get_right_range_by_callout_args
9: 0x7ff6c62efa81 - onig_unicode_define_user_property
10: 0x7ff6c62efe80 - onig_unicode_define_user_property
11: 0x7ff6c45ead0e -
12: 0x7ff6c462ec9e -
13: 0x7ff6c46357b9 -
14: 0x7ff6c4cd0ecd - onig_get_right_range_by_callout_args
15: 0x7ffe9af3259d - BaseThreadInitThunk
16: 0x7ffe9c5eaf38 - RtlUserThreadStart

Lastly, this may or may not be unrelated, but Screenpipe is inable to find monitors or audio devices in the UI, but the logs do reflect that they are seen.