Know when a network device goes offline

The update screen no longer reports a failure that did not happen

Every request the dashboard made gave up after a fixed 8 seconds, while the app is allowed far longer to reach GitHub and to download and verify an installer. On a connection that was not fast the screen gave up first and showed a browser error that told you nothing useful, even though the download had finished and the installer had launched. Each request now gets a time budget that matches the work, a request that really does run out of time says so in plain words, and the button reads Downloading while the installer is being fetched.

You can turn the automatic update check off

Settings, then Updates, then Check for updates automatically. With it off the app opens no outbound connection unless you press Check for Updates yourself. The setting takes effect without restarting the app. A setting the app cannot read leaves checks switched on, so a damaged configuration file never disables updates quietly. The Microsoft Store version does not perform this check at all, because Store installations are updated by the Store.

A scripted install no longer turns on Windows startup

The installer offers to start the app when Windows starts, and that box is ticked by default. A silent command line install applied the default without showing the page, so installing with winget switched it on without you seeing the choice. Silent installs now leave it off. The interactive installer is unchanged.

Fresh installs start from a four device example

A new install sets up four example devices so the dashboard has something to show before you add your own, and the build refuses to produce an installer carrying anything else. Updating an existing installation never replaces your own device list.