Interloper 2.2.1

• Fixed: in 2.2.0 the checks that verify digital signatures did not run — scheduled tasks, registry autoruns, services, recently added executables, open ports/remote-access tools, kernel drivers and the NVIDIA GPU check showed "Check could not complete … [System.String] does not contain a method named 'ContainsKey'". The code that loads the live signature list reused the name of the signature-check cache and replaced it. Everything checks again; a regression test covers it.
• With the Watch plan active, the status line under the results says automatic scans are included and how to turn them on (instead of offering the trial).
• Fixed: uploading a report to your account could use all of the PC's memory and never finish. Windows PowerShell 5.1 attaches hidden file information to text read from disk, and its JSON converter packed that in too, growing without limit. Everything the app sends to its service now goes through its own JSON writer, which only writes plain data.
• Results show right away. The upload runs in the background after the scan; the verdict line says Uploading…, then Synced to your account or why it was not synced. A slow or broken connection never holds up a scan.
• Uploads are compressed (gzip, about a tenth of the size) and have firm time limits on connecting, sending and the answer, with plain messages ("Could not reach the account service…", "did not answer in time…"). The report always stays on the PC.
• Scheduled scans write the Desktop alert before uploading.
• Service: stores reports that contain NUL characters (from registry data), accepts uploads up to 16 MB after decompression, start-up message lists which database variables it can see, npm run local, and the tests can run against a real PostgreSQL (TEST_DATABASE_URL).