Release LoadGen Insight Agent: 1.0.0.12952

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

Enhancements

• Foreground-Window Helper Restarted After It Stops - When the foreground-window helper in a user session stops unexpectedly, LoadGen Insight now starts it again after a short wait, as long as the user is still signed in, so the session keeps reporting UX timing data instead of staying silent until the next logon. Restarts are logged on lines that start with Restarting ServerAddin in. A helper that delivers no data several starts in a row is left stopped, with an error in the Insight log, until the user logs on or reconnects.
• Hardened the permissions of the agent's configuration and state folders: only SYSTEM and administrators can read or change them. /install and /connect set these permissions before the first configuration is written, existing folders are corrected when LoadGen Control starts, and files in them that neither the agent nor an administrator created are taken over by administrators or removed, each with a warning in the Control log
• Hardened agent self-update: the program folders of an updated agent now take the permissions of the installation folder, as after a fresh install, and folders left with different permissions by an earlier update are corrected when LoadGen Control starts

Bug Fixes

• Fixed Application Launch Times Reading Low - Launch times in application_launch_metric read up to about two seconds low, because they started when the agent noticed the process and ended at a time rounded down to the second. Fast launches, such as Notepad or a second start of Excel or Edge, came out below zero and were not written at all, and the Platform counted them as timed-out launches. Launch times now run from the process's own creation time to the moment its window appears, with sub-second precision. Expect launch times, and the baselines built from them, to be somewhat higher from this version on.
• Fixed Process Starts and Stops Overwriting Each Other - Starts and stops of the same application and user collected in one upload were written with the same timestamp, so process_information_metric kept only one of them; an Edge launch, which starts several processes, kept just one. Each start is now stamped with its process's creation time and each stop with the time it was noticed, so all of them are kept. Points of one series in the same second no longer overwrite each other either.
• Fixed Windows Reported as an Unknown Process - A window that reached LoadGen Control before the start event of its process was reported with process_name=unknown and could not be launch-timed. Such a window is now held until its process is known, for a short time at most.
• Fixed Windows Matched to a Stopped Process - A stopped process stayed in LoadGen Control's list of running processes, so a window of a new process that reused its process ID was reported under the old process's name, with a launch time counted from the old process's start. Stopped processes now leave the list.
• Fixed programs without version information producing no start and stop events, and so no launch timing; they are now reported with version 0.0.0.0, and Process-stop-event occurred for unknown process is no longer logged for them
• Fixed process start and stop events and measurements occasionally being lost between collection and upload