[Bug]: Fast Startup on Windows corrupts netclient .json/.bak config files, service fails to start and requires manual cleanup + re-join

Contact Details

[email protected]

What happened?

Bug description

When Windows Fast Startup (Fast Boot) is enabled, the netclient configuration becomes completely corrupted after the computer is shut down and powered on again. The service does not start, and manual start attempts fail with an error. The only way to restore functionality is to:

1. Navigate to the netclient installation folder (e.g., C:\Program Files\netclient)
2. Manually delete all .json and .bak files
3. Re-join the network using netclient.exe -join TOKEN

This is a data corruption issue, not just a service start failure.

Steps to reproduce

1. Enable Fast Startup in Windows:
   • Control Panel → Power Options → Choose what the power buttons do → Turn on fast startup (recommended).
2. Install netclient and successfully join a network: netclient.exe -join TOKEN
3. Verify the service is working (e.g., wg show shows interface, connectivity works).
4. Shut down the computer (do not restart).
5. Power on the computer.
6. After boot, check service status: Get-Service netclient
   • Service is Stopped
7. Attempt to start the service manually: Start-Service netclient
   • The command returns an error: Start-Service : Failed to start service 'netclient'
   • In services.msc, clicking "Start" shows: "Windows could not start the netclient service on Local Computer."
   • The service cannot be started by any means
8. Examine the netclient installation folder:
   • Configuration files (.json, .bak) are present but corrupted
9. Workaround applied:
   powershell复制

   cd "C:\Program Files\netclient"
   Remove-Item *.json, *.bak
   .\netclient.exe -join TOKEN

Version

v1.5.1

What OS are you using?

Windows

Relevant log output

Contributing guidelines

• Yes, I did.