Soteria Cloud KB
Soteria Cloud KB
Breadcrumbs

10.97 — Releases, Compatibility, Advisories and Lifecycle

Releases, Compatibility, Advisories and Lifecycle

Coverage

  • Acronis Cyber Protect Cloud release notes and hotfixes

  • Component and protection-agent build changes

  • New features, changes, fixes and known issues

  • Data-centre rollout and feature availability

  • Supported operating systems and workloads

  • Browser, hypervisor, application and database compatibility

  • Integration-version compatibility

  • Security advisories and required action

  • Deprecations, end-of-support and end-of-life notices

  • Replacement features/products and migration guidance

Official verification routes

Use the source that matches the question; do not rely on a copied version number or catalogue page alone.

Validation baseline — 28 September 2026

The official Cyber Protect Cloud documentation now identifies the console guide as 26.09. Acronis's managed-protection agent release history still lists 26.8.43120 (September 2026) as the newest published agent entry, part of Acronis Cyber Protect Cloud 26.08 Hotfix 2, preceded by 26.8.43043 as 26.08 Hotfix 1.

The dl.acronis.com agent-history route is still behind at 26.8.43043, while Acronis's managed-protection route lists 26.8.43120. The public Cyber Protect Cloud release-note shortcut still resolves to 26.07, last documented there as updated on 11 August 2026, while the public console documentation is labelled 26.09. These official source states are asynchronous and do not prove that any build, hotfix, feature or component is commercially enabled or deployed in a particular tenant or data centre.

The 26.8.43043 agent entry and the Acronis advisory database now agree that advisory ID UPD-2609-d35d-6ebd applies to the Acronis Cyber Protect Cloud Agent C26.08 Hotfix 1 on Windows, Linux and macOS. Continue to verify the exact installed build and advisory applicability before recommending remediation.

Acronis documentation warns that some features may not yet be available in every data centre. Before recommending an update, workaround or feature, verify the exact tenant, data centre/region, workload, enabled service or offering item, console version, agent/component build and the release/advisory applicability conditions.

Forward compatibility notice

The public 26.07 release notes announced that, starting with the 26.09 release, the Cyber Protection Agent for Mac no longer supports macOS 12 and earlier; macOS 13 is the stated minimum. The console documentation is now labelled 26.09, but the public release-note shortcut remains at 26.07 and the newest published agent entry remains 26.8.43120. Treat macOS 13 as the compatibility boundary for a 26.09 Mac agent, but verify the exact tenant-visible Mac agent build and approved change window before recommending or approving an update.

Do not infer Soteria Cloud commercial availability, local hosting, South African data residency, tenant entitlement or support ownership from an Acronis product page, release note, documentation topic or advisory.

Current 26.08 agent support-impact cross-check

The current managed-protection agent release history records these support-impact fixes. Use the issue ID, exact symptom and current build to recognise a possible version match; do not treat this list as an instruction to update or as proof that a build is available in the tenant.

26.8.43120 — 26.08 Hotfix 2

  • ABR-443264: backups using file filters could finish with the warning “The mask cannot be resolved”.

  • PLTFRM-94370: the agent could send excessive network-availability check requests to the cloud.

  • ABR-445264: on Linux machines using multiqueue block devices, unloading the snapshot driver—for example during an agent update—could cause a kernel NULL pointer dereference and operating-system crash.

26.8.43043 — 26.08 Hotfix 1

  • ABR-439605: recovery with reboot to different hardware could fail with “Recovery with reboot terminated unexpectedly”.

  • ABR-440315: recovery with reboot could fail on Windows Server 2025.

  • ABR-441446: recovery with reboot could fail on certain Windows configurations.

  • ABR-437168: diagnostic logging for recovery-with-reboot failures was improved.

  • ABR-439874: WinRE-based bootable media could take about five minutes to load because of a network-initialisation timeout.

  • KERNEL-21454: internet connectivity could stop on machines with Transparent Proxy Protection enabled.

  • ABR-441780: Managed Machine Service could terminate during dynamic feature removal and fail to restart.

  • AMP-57084: websites using certain encryption algorithms could be inaccessible while the agent was in FIPS mode.

  • ADP-56217: remote-session recording upload could remain stuck when the recording file was corrupted.

  • ADP-53416: the remote desktop server component was updated to guacd 1.6 with FIPS compliance.

26.8.42957 — 26.08

The earlier 26.8.42957 entry records the following resolved symptoms:

  • PLTFRM-93001: the console showed “Backup failed” although the latest backup succeeded.

  • PLTFRM-91965: plans showed “Succeeded with warnings” without corresponding errors or alerts.

  • ABR-414476: Microsoft 365 mailbox backup browsing or indexing failed with an internal error when email items had no parent folder.

  • ABR-429059: backups to an SMB share failed with a credentials error when several plans used the same share.

  • ABR-329053: file recovery to a GPT disk failed with a read error when its protective MBR was incorrect.

  • ABR-314208: policy-rule file backup failed when the parent directory contained more than 5,000 items.

  • ABR-434800: Linux systems using multiqueue block devices could crash during backup.

  • ABR-435922: Windows ARM64 agent installation intermittently failed with error 1603.

  • DEVLOCK-7164: enabling DLP could stall SMB access and freeze or crash Windows Explorer.

  • PLTFRM-69757: a new partner-tenant folder could fail to inherit enabled applications, causing tenant moves to fail with “application is not available”.

  • ADP-55564: customised report names reverted to defaults.

  • ADP-32882: web remote desktop could remain interrupted after an earlier failed authentication attempt.

Safe resolution boundary: first compare the exact symptom and current agent/component build. If the environment is on an earlier affected build and the exact issue matches, confirm the build actually offered in that tenant and the approved change window. If the environment already runs the build that records the fix, or any applicability condition differs, do not assume the same defect; preserve activity, error and version evidence and continue normal diagnosis or escalation.

Release review

Each release or hotfix triggers checks for:

  1. console navigation and screenshots

  2. prerequisites and supported platforms

  3. agent and component builds

  4. data-centre availability and rollout wording

  5. quotas, licensing and enabled-service dependencies

  6. API and integration behaviour

  7. fixed issues, known issues and security advisories

  8. lifecycle or deprecation impact

  9. Soteria operational and customer-journey impact

Record the official source URL, document/release identifier, validation date, exact product/workload, applicability conditions and whether the tenant/data-centre state was independently confirmed.

Source hierarchy

Use the current product documentation, official release notes, agent/component release history, security advisory database, Support Portal articles and the matching lifecycle category. A cached or copied article is never authoritative when the official source has changed. If official sources disagree or appear to be at different rollout stages, preserve both links, state the mismatch and stop before claiming availability or applying a version-dependent change.