Release LoadGen Insight Agent: 1.0.0.12937

Windows agents only: every change in this release applies to Windows agents. Linux and macOS agents are unchanged.

Bug Fixes

• Fixed Foreground Window Monitoring Still Missing on Remote Desktop Session Hosts - The foreground-window helper in each user session stopped two to three seconds after it started, logged as ServerAddin exited before delivering any data - ExitCode=0xC0000005, so session hosts still sent no foreground_window_metric or application_launch_metric data with 1.0.0.12928. The helper now keeps running and reports the foreground window in every session. A window too large to report is skipped, and monitoring of that session continues. This completes the Remote Desktop session host fix of 1.0.0.12928.
• Fixed Failed Agent Updates Restarting the Services Repeatedly - When the download of an agent update failed, the update stopped and restarted LoadGen Control and LoadGen Insight every two minutes, and the agent kept reporting its old version without saying why. LoadGen Control now downloads and checks the new version while both services keep running, and stops them only when the new version is ready to install. If a step after that fails, the previous version is put back and started again. Logging settings, the local cache and the agent logs are kept across an update. A failed update is logged once as a warning, for example Agent update to 12928 failed (attempt 1, stage download), with the reason and the time of the next attempt, and is retried after a waiting time that grows with each failure, up to six hours; another version offered by the Platform is tried at once. Agents also wait for their turn when the machine group updates in the Gradual rollout mode. The update to this version still runs through the updater of the version you have installed, so the new behaviour applies from the next update on.
• Fixed Insight Waiting for a Configuration After a Manual Install - When LoadGen Control already had its own configuration but the Insight configuration file was missing, for example after a manual install on a machine that had been enrolled before, Insight waited indefinitely and logged that the file is empty. Control now requests the full configuration from the Platform whenever the Insight configuration file is missing, empty or unreadable, and logs the reason once as Requesting the full configuration from the Platform. An empty configuration file is no longer created when none exists.