Baixar Arq 7.49.0.0 per a Windows

Improvements
- Building the backup set database (needed after "adopting" a backup set) is much faster for large backup sets.
- Improved OneDrive performance in the case of unstable or slow internet connectivity.
- Updated the Mega S4 region picker to use the latest endpoints. Existing Mega S4 storage locations are unaffected.
- Budget enforcement now removes unreferenced data first, so that the stored size is measured accurately before any backup records are deleted. The stored size before and after enforcement is logged.
- The Arq Premium storage dashboard's note about deleting oldest backup records now makes clear that this happens only if a storage budget is set.
- When adding an S3-compatible storage location, if the URL entered includes the bucket name as part of the host name (for example https://mybucket.s3.nl-ams.scw.cloud, as shown in Scaleway's console), Arq now removes the bucket name and uses the provider's endpoint.
Bug Fixes
- Fixed a backup plan's sidebar icon staying frozen at "play" after the Arq window reconnected to the Arq7Agent service while a backup was running, even after the backup finished with errors.
- Fixed a backup run that failed during its cleanup steps (stopping workers, deleting VSS snapshots, running the postflight script) being recorded as still in progress.
- Fixed the Arq window showing stale state when the service failed to deliver a status update to it. The service now closes the connection instead, and the window reconnects and reloads everything.
- Fixed in-progress backup records never being deleted from storage locations with immutable backup records. Arq now leaves an in-progress backup record alone until its immutability period has ended, and deletes it on the next backup after that.
- Fixed backup plans whose storage location had already been deleted still appearing in ArqMonitor's menu and in "arqc listBackupPlans", and still running on schedule, even though the Arq window didn't show them. The Arq7Agent service now deactivates such plans when it starts.
- Fixed new backup plans on Scaleway Object Storage (and other S3-compatible providers that declare XML namespaces differently than the way AWS does it) failing with "Backup plan has no encryption key" or "Backup set directory ... is missing or empty", because Arq's parsing of the object listing found no objects.
- Fixed a missing object encountered while initializing the backup set database during a back-up-and-validate run being recorded as a backup error. That blocked retention rules and budget enforcement and forced a full rescan on the next backup. Arq now logs the unreadable backup record and continues, as it does in a normal backup.