﻿Budgie Backup - post-build suspicious and threat scan
====================================================

Run finished : 2026-10-02 02:38:20 +10:00
Took         : 4h 14m
Build folder : P:\Simon\Code\Visual Studio\2026\latest_build
Files scanned: 16
Services     : VirusTotal
Mode         : hash lookup first, unknown files uploaded
Reports here : 16

Report naming: <Variant>_<Service>_<FileName>_report.txt

Per file and service:
  [ok  ] VirusTotal     Small CreateBudgieBackupFile.exe
  [ok  ] VirusTotal     Small RunBudgieBackupFile.exe
  [ok  ] VirusTotal     Small BudgieBackupUpdater.exe
  [ok  ] VirusTotal     Small BudgieBackupSysTray.exe
  [ok  ] VirusTotal     Small BudgieBackupSync.exe
  [ok  ] VirusTotal     Small Budgie Backup.scr
  [part] VirusTotal     Small Budgie Backup 3D.scr
  [part] VirusTotal     Large CreateBudgieBackupFile.exe
  [part] VirusTotal     Large RunBudgieBackupFile.exe
  [part] VirusTotal     Large BudgieBackupUpdater.exe
  [part] VirusTotal     Large BudgieBackupSysTray.exe
  [ok  ] VirusTotal     Large BudgieBackupSync.exe
  [part] VirusTotal     Large Budgie Backup.scr
  [ok  ] VirusTotal     Large Budgie Backup 3D.scr
  [ok  ] VirusTotal     Small BudgieBackupSetup-Small-0-9-26-274.exe
  [part] VirusTotal     Large BudgieBackupSetup-Large-0-9-26-274.exe

What the marks mean:
  [ok  ] a verdict, and every engine that can read the file answered.
  [part] a verdict, but some engines still timed out or failed after the
         rescans. The report names them. Common for very large files - the
         engines run out of VirusTotal's time limit, not out of patience here.
  [wait] no verdict yet - VirusTotal had not finished analysing it in time.
         Run this script again later; the hash lookup picks the verdict up.
  [new ] -LookupOnly, and VirusTotal has never seen this file.
  [FAIL] no answer at all - no API key, a rate limit, or an outage.
None of these marks mean a file was found to be malicious. Detections, if
any, are listed by engine name inside each file's report.

Detections are not automatically a problem. A freshly signed installer with no
reputation yet is routinely flagged by a couple of no-name engines and clears as
the certificate ages. Read the engine names, not the count.
