Hello,
I believe I have found a reproducible bug in Portmaster 2.2.1 on Windows.
Environment
- Windows 10 Pro 22H2
- OS Build: 19045.6466
- Portmaster 2.2.1
- Fresh installation
Steps to reproduce
- Install Portmaster.
- Launch it for the first time.
- Do not change any settings.
- Restart Windows (or use the Shutdown option inside Portmaster).
- Launch Portmaster again.
Expected result
Portmaster should start normally.
Actual result
Portmaster Core fails to start.
Running portmaster-core.exe manually produces the following error:
failed to start Profile:
could not start database core (type sqlite):
migrate sqlite:
sql: Scan error on column index 1, name "applied_at":
unsupported Scan, storing driver.Value type string into type *time.Time
Temporary workaround
Renaming the following folder:
C:\ProgramData\Portmaster\databases\core
allows Portmaster to start again once.
However, after another Windows restart or Portmaster shutdown, the exact same problem occurs again.
Additional observations
- The issue happens even if I never change any settings.
- It is reproducible on every reboot.
- The UI gets stuck on "Connecting to Portmaster..." because the Core service never starts.
- The problem appears to occur after the database is created and then reopened on the next launch.
I am willing to provide logs, screenshots, or test experimental builds if needed.
Thank you.
Hello,
I believe I have found a reproducible bug in Portmaster 2.2.1 on Windows.
Environment
Steps to reproduce
Expected result
Portmaster should start normally.
Actual result
Portmaster Core fails to start.
Running portmaster-core.exe manually produces the following error:
failed to start Profile:
could not start database core (type sqlite):
migrate sqlite:
sql: Scan error on column index 1, name "applied_at":
unsupported Scan, storing driver.Value type string into type *time.Time
Temporary workaround
Renaming the following folder:
C:\ProgramData\Portmaster\databases\core
allows Portmaster to start again once.
However, after another Windows restart or Portmaster shutdown, the exact same problem occurs again.
Additional observations
I am willing to provide logs, screenshots, or test experimental builds if needed.
Thank you.