›  Cloud Backup  ›  Release notes  ›  Windows  ›  7.x

Release notes for Cloud Backup for Windows 7.x

On this page


Support for direct data restore from the object storage

The app now receives and applies caching settings (if they are configured) from the Dashboard. (Caching settings received from the Dashboard override those configured locally in the app.)

During backup, Microsoft Outlook data files (PST) are processed as locked using VSS to avoid errors when opening Outlook caused by files in use

Remote restoring could end up with only partial data being restored

The app treated file versions as new files and failed the backup as if the cloud space quota for the account was exceeded

After backing up the files located at the root of a disk volume, the app did not show them in the View / Restore window


OBRM now supports the new backup and retention policies

Backup accounts with a new backup and retention policy assigned to them have a limited OBRM user interface

OBRM now retries to perform the restore instead of stopping the operation because of the exceeding connection timeouts (error System.InvalidOperationException: Timeouts are not supported on this stream)

Backup and restore could fail for backup accounts with usernames exceeding 90 characters


The app now requires .NET Framework 4.8 that can be downloaded and installed prior to installing or updating the app. (If .NET Framework installation fails, please contact or refer to Microsoft Support.)


OBRM now supports Windows 11

If OBRM cannot run a scheduled backup task for whatever reason, it automatically creates and runs a new scheduled backup task identical to the existing one

Backup failed because of the specific file or folder naming (error Index (zero based) must be greater than or equal to zero and less than the size of the argument list or error Input string was not in a correct format)


Single sign-on authentication for backup accounts

OBRM now does not support Windows Vista and Windows Server 2008

After enabling SSO for a backup account, all backup jobs (scheduled and in progress) in OBRM will fail until the user logs in to OBRM using SSO

Users with backup accounts belonging to a company that uses SSO cannot reset their passwords from OBRM and use account types other than regular

OBRM reported the Access is denied error in its backup reports for Windows user folders that are system junction points while the data was still backed up successfully


Replaced EULA with Terms of Service to be accepted before OBRM installation

OBRM now does not record the backup file exclusions in its logs

Scheduled backup tasks were re-scheduled each time OBRM synchronized the backup policy remotely


TOTP authentication when signing in to OBRM

OBRM would incorrectly process a hard drive if its drive letter in the backup policy was specified in lower case

Remote data recovery failed with error ‘Illegal characters in path’

Each time OBRM synced the backup policy, a previously scheduled backup task was re-scheduled, and backup was run again


OBRM could spend about 14 hours to apply retention policies to backups that resulted in poor application performance


OBRM failed to access and back up a number of Windows user folders that are the default system junction points and do not have to be backed up, and thus falsely reported the backup error (Access is denied)


OBRM SDK: Implemented automatic reloading of the settings on the client.SetInternetSettings() method that does not require the service restart

Improved the way OBRM retries to recover files and folders in case of a network connection issue

OBRM retention policy failed with the error System.UriFormatException: Invalid URI: The hostname could not be parsed

OBRM folder backup failed with the error System.IO.FileNotFoundException: The target file is a directory, not a file (Microsoft cloud files API)


OBRM now does not automatically create a LiveProtect scheduled task if this option is not actually used

OBRM was unable to execute a remote command (for example, remote update) because of the script failures

OBRM was unable to write its events to the Windows event logs

Backup of files and folders with LiveProtect enabled failed if the rebranded company name was longer than 64 characters

OBRM could sometimes fail to use a USB drive as the storage for local backup


Ability to recover files not only by date, but also by time of backup

OBRM SDK: Support for recovering file versions

OBRM SDK: Support for configuring proxy

After you remove a scheduled backup from OBRM, the system also removes it from monitoring in the Dashboard

When creating a trial account, OBRM now validates the password strength

Monitoring events did not show in the Dashboard because OBRM sent incomplete backup data

OBRM was unable to complete backup if resolving the root directory referenced by a symbolic link

OBRM stopped responding when running a monthly scheduled backup on Windows 10

Bare-metal backup feature


Microsoft SQL Server 2019 support

Ability to stop a backup task if the computer switches to the battery power

Ability to use {machinename} as a wild card in the username template for custom MSI

Option to apply LiveProtect to all files protected with the backup policy

Ability to use Scan personal folders for all users on a computer with Use system account enabled

Modified report for the bare-metal backup without upload to the cloud

Improved OBRM update channel

Scanner could not find any files if Windows Subsystem for Linux was enabled (error There is already an object with name 'sys')

Poor resizing of OBRM dialogs and windows

Backup service used excessive CPU resources sometimes

Bare-metal backup progress bar showed incorrect numbers for Total Files Processed and Data Processed

Microsoft SQL Server backup: database folder and file names were generated using the UTC standard, while the backup dates used local time

Advanced Folder Backup temporary policy did not apply to the mapped drives that led to some files being skipped

Inability to log in to a backup account using the admin account if multi-factor authentication was enabled for a part of the accounts

Inability to select folders for backup if display scaling in Windows was set to 150% or higher

OBRM showed an application error after clicking its tray icon while the Backup Progress window was open

Rebranding did not apply to the tray icon of and the product name in OBRM if LiveProtect was enabled

OBRM could not access a file during recovery because it was used by another process

Scheduled backups failed to start sometimes with error NtfsScanner dispose


OBRM could occasionally skip a number of files during backup due to misinterpretation of symlinks and original file paths


LiveProtect could stop working sometimes and did not restart until the next Windows sign-in


Ability to run OBRM without administrator privileges

Option to run a scheduled backup task as soon as possible after a scheduled start was missed

Option to automatically wake the computer to start a scheduled backup task

Option to start a scheduled backup task only if the computer is on AC power

Parameters to configure the data upload failover

Extra options when creating a custom OBRM MSI in the Dashboard (automatically create a backup account for the protected device, and disable automatic user login)

Improved algorithm of uploading files to the cloud on unstable channels

Microsoft SQL Server and Exchange Server backup options are now always visible

Some bare-metal backups were not deleted if Do not upload BareMetal backups to the cloud option was selected

Bare-Metal backup events were sent to the Dashboard as manually run instead of scheduled

No error message if a bare-metal backup failed

File and folder backup occasionally completed with error Actual and stored hashes mismatch

Starting a Microsoft SQL Server backup while another one was in progress resulted in the incremental backup instead of the full

Failure to complete a Microsoft SQL Server backup due to an attempt to back up a database not selected for that

Failure to back up a Microsoft SQL Server database due to case-sensitivity issues in the database name

Failure to upload or recover backup data due to strict Windows security settings (error Invalid Encryption Key)

Failure to back up a Microsoft Exchange Server mailbox database due to case-sensitivity issues in the database path

Failure to send the backup monitoring events (error Failed to get Central Management settings)

Failure to get the list of protected files due to unsupported characters in a file name (error Invalid character in file name)

Canceled package was uploaded continuously within each file batch until the backup completion

Activation of the new retention policy sometimes resulted in the endless recovery process

In some language versions, OBRM stopped working when configuring backups (error File format is not valid)

User interface layout flaws on 4K displays when selecting items for backup

Scanner exclusions specified in the remote backup policy were missing in OBRM

Failure to recover files with unsupported symbols in their names (error Invalid characters in path)

ShadowProtect backup events were not stored sometimes, therefore No backup for X days event was generated

Occasional failure to start a backup job (error The creator of this fault did not specify a Reason)

Failure to upload the locked files (error Deletion of snapshot failed)


Backup failure for UltraSafe accounts (error Invalid Encryption key. Failed to receive response from remote server)


LiveProtect for folders

Microsoft Exchange Server 2019 support

Option to set locale (language, dates, time formatting, and so on) during installation

Email reports are not required to enable retention policy

Backup account login credentials are encrypted in custom MSI

Improved bare-metal backup by optimizing and compacting increments

In case of several Windows accounts on one computer, files of different users could be backed up together

Failure to restore files due to Unicode characters in the device name

Failure to back up locked files to the local storage, if they were backed up to the cloud before the local backup option has been enabled

Failure to start backup (error Encryption key is not valid)

Missing user interface localization

Failure to exclude five default folders when configuring backup of personal folders with remote backup policy via API

Multi-factor authentication failed via proxy

Application crashed after rebranding (error Requested range extends past the end of the array)

Application crashed when a backup task was manually modified via Windows scheduler

Failure to back up locked files (error Index (zero based) must be greater than or equal to zero and less than the size of the argument list)

Microsoft Exchange Server backup failure (Error occurred during database reupload)

Backup report date format did not conform to the user regional settings


Remote backup policy: Bandwidth throttling and daily upload limiting

Custom MSI building: Auto-login for automatically created backup accounts


File upload speed did not show in the backup progress window


Remote backup policy: Ability to scan personal files and folders of a user without providing the relevant Windows user credentials

Remote backup policy: Option to include or exclude specific files and folders to or from scanning

Support for Microsoft Windows Server 2019

Support for Microsoft SQL Server 2017

Reduced memory consumption when backing up and recovering with the retention policy applied

Reduced memory consumption and improved performance for the backup sets containing a lot of small files

Improved performance when backing up large data sets locally

Include folders section was shown, if Scan all folders has been selected

Inaccurate number of the processed files during recovery, if Recover all file versions was selected

Occasional backup failure, if several locked files were uploaded in a large set

Backup sets containing large files were occasionally uploaded in one thread

Layout collapsed on 4K displays with 150% scaling

Application update from the Dashboard led to the warning message from the Interactive Services Detection (if enabled)

Automatic proxy configuration in Microsoft Internet Explorer was not applied

Backup exchange failure due to PowerShell could not find the terminator

Occasional failure when backing up huge files (error Package size exceeded)

Continuous failure when backing up the locked files despite proper VSS

AccountCreatorRunner module execution failure on 32-bit operating systems

Application crashed during the schedule setup (error Cannot load Counter Name data because an invalid index)

Advanced Folder Backup failure (error Nullable object must have a value) if Move Files to Cloud was selected

Incorrect counters when recovering all file versions

Scheduled time for the bare-metal backup and the advanced folder backup changed after modifying the backup settings

Occasional backup failure (error OutOfMemoryException)

Remote backup policy: Long file paths resulted in the files being removed by the retention policy and then processed again during each next backup

Occasional recovery failure (error NullReferenceException)


After upgrading from version 6.8 (or previous) to version 7.2, users could not sign in


Option to restore data to the original locations, that is, before backup

Link to the backup history page in the main application window

Support for Microsoft SQL Server backup in the cluster

Automatic download of Microsoft .Net Framework during installation, if needed

Huge backup sets: Reduced delay before a backup starts

Huge backup sets: Increased speed of the files deleting via the recovery view

Huge backup sets: Reduced delays when changing a backup set

Microsoft SQL Server and Microsoft Exchange Server incremental and differential backups are optional now

Improved stability of the Advanced Folder Backup

Increased speed of the local backup processing

Bare-metal backup: Boot failure after recovery of a Microsoft Windows Server 2008 system with an EFI volume

Recovery from a local backup: Inaccurate number and sizes of the recovered files in the progress window

Backup progress indicator showed twice larger size of a bare-metal backup, a Microsoft SQL Server or a Microsoft Exchange Server backup

Filenames with non-Latin characters were case-sensitive

Scheduled backup tasks ignored the daylight savings time changes

Hourly scheduled file and folder backup on a Windows 10 device restarted 10 seconds after the previous backup was completed

Files with periods at the end of their filenames could not be backed up

Failed Microsoft Exchange Server backup led to the failure of the next backup

Scheduled Microsoft SQL Server incremental backup became full, if a file and folder backup occurred between two Microsoft SQL Server backup jobs


Improved recovery speed

Improved search performance

Increased speed of getting the list of files for recovery

Reduced CPU load during recovery

Retention policy for files deleted locally was not applied to the data on UNC shares

Local backup: Could not protect locked files

Local backup: False positive in case of lack of the space in target folder

Local backup: Stability issue for backup to password protected network storage

Bare-metal backup: Guest account credentials were required if the target folder was not password protected network share

Bare-metal backup: Sometimes could not create bootable ISO/USB on Microsoft Windows Server 2008

Needless cache files were not removed in case of backup cancellation and after deletion of the files according to the retention policy

Unhandled exception happened when starting application having it already running and minimized

Sometimes Microsoft SQL Server backup was failing with error Process cannot access the file

Backup of a file fails if it gets locked during the backup

Advanced folder backup with replicate policy: Old file versions were not purged if the whole drive was selected for backup

Sometimes using proxy settings could cause a stuck of the backup at uploading step


Reduced backup duration. This prevents sending of excessive reporting information to the monitoring system

Algorithm for interacting with local databases. Backups start faster


Bare-metal backup: Option to skip upload to the cloud and store only locally

Bare-metal backup: Microsoft Windows Server 2016 support

Bare-metal backup: Microsoft Windows Server 2008 and 2008 R2 limited support (no UEFI systems supported)

Single application build for Home and Business users

Security: Verify digital signature of update package before executing

Recovery view: Search through locally backed up files

Option to protect OST-files, which are skipped by default

Bare-metal backup: New backup will not be created until previous one is fully uploaded to the cloud

Now destination folder is used as a temporary folder during recovery

Old local backup will now be removed automatically

Bare-metal backup: Recovery failure for machine with dynamic system disk

Bare-metal backup: Upload issue when backing up from a network share

Microsoft SQL Server backup leaves temp files on the network share

Backup failure when processing locked files with characters { or } in the filename

Local backup was unable to process locked files

Sometimes backup reports were not sent

Inaccurate text align on the sign-up page

Application crashed after clicking the View/Restore button

Inaccurate sorting by file names on network folders in the backup wizard

Inaccurate sorting by folder size on recovery view

Messaging module did not work properly if application is installed in non-default folder