[GH-ISSUE #70] Config wizard fails to create config file when started with --config-wizard on Windows #13

Closed
opened 2026-02-26 18:43:12 +03:00 by kerem · 3 comments
Owner

Originally created by @unclesp1d3r on GitHub (Dec 24, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/70

Originally assigned to: @devnullvoid on GitHub.

There appears to be a second, related issue on Windows when launching the configuration wizard directly via the command-line flag, rather than letting pvetui create the default config first.

When running pvetui 1.0.15 on Windows with the --config-wizard flag, the interactive configuration wizard allows all fields to be filled out but fails when saving. The tool creates the pvetui configuration directory, but no configuration file is written.

Steps to reproduce

  1. Install pvetui 1.0.15 on Windows using Scoop.

  2. Open PowerShell and run:

    pvetui --config-wizard
    
  3. Fill in the configuration form, including valid authentication details (password or token).

  4. Select Save.

  5. Observe the error dialog:

    Failed to save config: open: The system cannot find the file specified.

Expected behavior

The configuration wizard should create a new configuration file and save the provided settings successfully.

Actual behavior

  • The pvetui configuration directory is created.
  • No configuration file is written.
  • The save operation fails with the error above.

Environment

  • OS: Windows 11
  • Installation method: Scoop
  • Version: pvetui 1.0.15

Additional notes (hypothesis)

My guess is that, in this code path, the wizard attempts to open an existing config file for writing rather than creating a new one if it does not already exist. This would explain why the directory is created but the save fails when no config file is present.

Happy to test a fix or provide additional debugging output if needed.

Originally created by @unclesp1d3r on GitHub (Dec 24, 2025). Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/70 Originally assigned to: @devnullvoid on GitHub. There appears to be a second, related issue on Windows when launching the configuration wizard directly via the command-line flag, rather than letting `pvetui` create the default config first. When running **pvetui 1.0.15 on Windows** with the `--config-wizard` flag, the interactive configuration wizard allows all fields to be filled out but fails when saving. The tool creates the `pvetui` configuration directory, but no configuration file is written. ### Steps to reproduce 1. Install `pvetui` 1.0.15 on Windows using Scoop. 2. Open PowerShell and run: ```powershell pvetui --config-wizard ```` 3. Fill in the configuration form, including valid authentication details (password or token). 4. Select **Save**. 5. Observe the error dialog: > `Failed to save config: open: The system cannot find the file specified.` ### Expected behavior The configuration wizard should create a new configuration file and save the provided settings successfully. ### Actual behavior * The `pvetui` configuration directory is created. * No configuration file is written. * The save operation fails with the error above. ### Environment * OS: Windows 11 * Installation method: Scoop * Version: pvetui 1.0.15 ### Additional notes (hypothesis) My guess is that, in this code path, the wizard attempts to open an existing config file for writing rather than creating a new one if it does not already exist. This would explain why the directory is created but the save fails when no config file is present. Happy to test a fix or provide additional debugging output if needed.
kerem 2026-02-26 18:43:12 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@devnullvoid commented on GitHub (Dec 24, 2025):

As always, I appreciate the detailed report. I will work on getting this fixed!

<!-- gh-comment-id:3689388568 --> @devnullvoid commented on GitHub (Dec 24, 2025): As always, I appreciate the detailed report. I will work on getting this fixed!
Author
Owner

@devnullvoid commented on GitHub (Jan 1, 2026):

Fix is on develop and verified (Windows). Config wizard now creates/loads a default config when launched with --config-wizard so Save succeeds. Release pending.

<!-- gh-comment-id:3704240464 --> @devnullvoid commented on GitHub (Jan 1, 2026): Fix is on develop and verified (Windows). Config wizard now creates/loads a default config when launched with --config-wizard so Save succeeds. Release pending.
Author
Owner

@devnullvoid commented on GitHub (Jan 2, 2026):

Should be fixed in latest release v1.0.16 -- let me know if you run into any further issues.

And as always, I appreciate your feedback.

<!-- gh-comment-id:3704356820 --> @devnullvoid commented on GitHub (Jan 2, 2026): Should be fixed in latest release [v1.0.16 ](https://github.com/devnullvoid/pvetui/releases/tag/v1.0.16)-- let me know if you run into any further issues. And as always, I appreciate your feedback.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pvetui#13
No description provided.