bug: Node not starting up properly on Windows after a system restart with tray app

[Ivvvor]

Code: YGC4CB

When testing Freenet across restarts on windows I've noticed the tray app comes up and often launches the node, but mostly the node either gets stuck and/or many times certain tray functions don't work as expected.

With the node itself, I manually bring up the local web dashboard and although it says it's connected to four peers, none of them are showing any traffic moving and under the 'node is healthy' banner I see External address: discovering... and it never gets beyond that and no new peers appear. The only way I can get the node to work is to restart it.

Now I believe this has happened every time I've done a Windows restart, but the node seemed to start up correctly on a cold bootup.

The behaviour of the tray app on restarts is also strange. Often the 'Open Dashboard' and 'View Logs' menu options do nothing, but I can stop, start, restart the node as usual from the menu. If I stop and start the service, the menu works as usual.

[github-actions]

🤖 Auto-labeled

Applied labels:

• T-bug (98% confidence)
• P-medium (85% confidence)
• A-networking (90% confidence)
• S-needs-reproduction (80% confidence)

Reasoning: The report describes incorrect/unexpected behavior (node fails to fully start, external address discovery never completes, tray menu actions non-responsive) so it's a bug. It appears to affect Windows restarts specifically and impacts functionality for the reporter but is not clearly blocking all users or releases, so P-medium is appropriate. Fix will likely require moderate investigation into startup sequencing, peer discovery and the tray app inter-process interactions, so E-medium. The problem involves peer discovery/external address and apparent lack of network traffic (A-networking) and also the tray app / startup UI integration (A-developer-xp). The issue would benefit from clearer, reproducible steps and logs to diagnose (S-needs-reproduction). Confidence scores reflect the clarity of the report and inferred areas of impact.

Previous labels: none

If these labels are incorrect, please update them. This helps improve the auto-labeling system.