[BUG] Windows 0.0.10: Startup at login registers python.exe instead of fluidvoice.exe

[stinp3r]

Describe the bug

In FluidVoice for Windows 0.0.10, enabling Startup at login left a per-user Windows startup entry pointing to a bare Python interpreter instead of the installed FluidVoice executable. After restarting the PC and signing in, FluidVoice did not launch automatically.

Reproduction steps

1. Install FluidVoice for Windows 0.0.10.
2. Enable Startup at login in the app settings.
3. Restart Windows and sign in to the same user account.
4. Observe that FluidVoice does not open automatically.
5. Inspect the FluidVoice value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.

This describes the observed sequence on the affected installation; the setting has not been toggled again to independently reproduce the registry write.

Expected behavior

The startup entry launches the installed FluidVoice application at user sign-in, using its correctly quoted executable path.

Actual behavior

The FluidVoice registry value was:

"C:\Users\<USER>\AppData\Local\Programs\Python\Python312\python.exe"

There were no script arguments. The installed application executable, also confirmed from the running FluidVoice process, was:

"C:\Users\<USER>\AppData\Local\FluidVoice\fluidvoice.exe"

Win32_StartupCommand independently reported the same Python-only startup command. No FluidVoice scheduled task was found.

Paths above are sanitized; <USER> replaces the actual account name.

App Version

Windows 0.0.10 (confirmed from the installed application's uninstall registry metadata).

macOS Version

Not applicable — this report concerns the Windows build. Exact Windows version/build was not collected during this investigation.

Architecture

Unknown / not collected.

Workaround and verification status

Replaced only the per-user FluidVoice Run value with the quoted, existing fluidvoice.exe path. Read-back confirmed the saved value, and the executable's existence was verified.

Automatic launch at the next Windows sign-in has not yet been tested. This report does not claim that end-to-end verification has passed.

Suggested investigation

Please check how the packaged Windows build resolves the executable used for startup registration. The observed entry suggests it may be selecting a Python interpreter rather than the installed app launcher; the underlying implementation cause is not confirmed.

The public windows-main branch currently contains only a release README and says the Windows source is not published, so we cannot prepare a source-level fix or regression test. If a public contribution path becomes available, please point us to it.

This report was prepared with AI assistance from read-only diagnostics and verification of the narrowly scoped local registry workaround.