Changes compared to 25.3.7
NOTE: The Impossible Cloud eu-central-1 region has been deprecated. Existing Storage Vaults and Storage Templates using this region will remain configured.
Changes compared to 25.3.7
NOTE: The Impossible Cloud eu-central-1 region has been deprecated. Existing Storage Vaults and Storage Templates using this region will remain configured.
Changes compared to 25.3.6
Comet makes use of in-memory indexes to optimise backup and retention pass jobs to maintain a list of where the data is in the Storage Vault. For larger Storage Vaults, this can lead to a large amount of data held in memory. On devices that have a lower amount of RAM, this can cause a job to fail as there is not enough available memory to complete the job. Comet's solution is to store the indexes on-disk using temporary files instead. This is because devices can often have more free disk space than available RAM.
When a scheduled backup or retention pass requires more RAM than is available, Comet will now automatically switch to store the indexes using temporary files on disk.
Comet 25.3.7 updates the translations for 13 languages. These are Danish, German, Spanish, French, Hebrew, Croatian, Italian, Dutch, Portuguese (Brazil), Portuguese (Europe), Russian, Polish and Thai.
When the policy setting "Prevent opening the application interface" is enabled, clicking the "Show Interface" button from the Comet Backup desktop app tray icon on Windows will now open the login dialog prompt.
This change allows another user to log into Comet Backup. Previously, this button had no action.
Changes compared to 25.3.5
It is now possible to cancel running jobs in bulk from the Job Logs page on a Comet Management Console. This is an effective way to stop all currently running backup jobs with one click.
Changes compared to 25.3.4
Changes compared to 25.3.3
In previous versions of Comet, the "Select all except..." option for Microsoft 365 Protected Items was provided as an alternative way to select accounts, allowing for the automatic inclusion of new accounts and potential exclusion of others. User feedback was that the behaviour of this option was unintuitive, and so we have elected to remove this option in favour of a more intuitive alternative.
In Comet 25.3.4, we are introducing the new "Back up everything" option for Microsoft 365 backups. This option provides a simple way to back up everything within a domain, including any accounts that are added later.
To back up everything with exceptions, users should instead create a group in Microsoft 365 and have the group auto-assign to new accounts. Users to be excluded can be removed from the group, and this group can then be selected in Comet.
Changes compared to 25.3.2
Comet uses a custom Linux kernel driver backupsnap61 to snapshot a block device during a Linux Disk Image Protected Item backup.
In previous releases, backupsnap61 had to be installed manually using the backupsnap61-install.sh script found in the Comet Backup install directory.
Without backupsnap61 installed, Comet can't guarantee it can get exclusive read access to a block device. This will appear as a warning in a Linux Disk Image backup job log.
Now, backupsnap61 is installed automatically by Comet to ensure a snapshot driver is always available before starting a Linux Disk Image backup.
Changes compared to 25.3.1
Creating the Linux recovery environment ISO using Comet Backup on a Linux endpoint can now be done without requiring Docker to be installed. This simplifies the install requirements to build the Linux recovery environment and also reduces how long it takes to build the recovery environment.
VMware Protected Items that have been configured to use the Latest VM state (Changed Block Tracking) mode will now fallback to performing a full VM backup when Comet detects that more than 50% of the disk has changed. This speeds up the backup peformance when large parts of the VM has been modified.
Changes compared to 25.3.0
Changes compared to 25.2.0
As part of our efforts to improve the experience of using Comet, in Comet 25.3.0 we have added functionality to automatically change Storage Vault access keys for some of our supported storage providers, allowing admins to manually unlock compatible Storage Vaults without the risk of data loss.
Vaults can also be automatically unlocked when specified criteria, configured in user policy settings, have been met.
The following Storage Vault types are currently supported:
Comet 25.3.0 adds support for setting yearly schedules and retention rules - great for long term storage, archival, and compliance requirements.
Changes compared to 24.12.5
As part of our efforts to improve the usability of Comet, all Comet Server Roles have been renamed.
These changes better reflect the capabilities of each role making it easier for new and existing customers to understand what each role does.
As part of this change, the Comet Server Service Manager (CSSM) has been renamed to the Comet Core Service Manager (CCSM).
The Comet Server web interface has also been update to reflect this changes, grouping the related side menu pages and settings under each of the new names.
Self-Hosted Comet Management Console Only
Storage Templates are Comet's recommended way to configure and deploy Storage Vaults for your backup infrastructure. Findng the Storage Templates settings on a Self-Hosted Management Console has been made significantly easier.
In older versions of Comet, the Storage Template settings were found as part of the Management Console (previously Auth Role) settings. This has now been moved to its own settings section which is a lot easier to find.
Changes compared to 24.12.4
Comet 24.12.5 introduces the ability to restore virtual machine Protected Items directly into new Hyper-V virtual machines.
This brings:
Direct restores into Hyper-V is available from the Comet Server web interface and from the Comet Backup desktop app. The following screenshots are from the Comet Server web interface.
NOTE: For direct Hyper-V restores, the Comet Backup desktop app must be running on the same endpoint as Hyper-V is installed on.
Comet 24.12.5 introduces the ability to restore virtual machine Protected Items directly into new VMware (vSphere or VCenter) virtual machines.
This brings:
Direct restores into VMware (vSphere or VCenter) is available from the Comet Server web interface and from the Comet Backup desktop app. The following screenshots are from the Comet Server web interface.
Comet 24.12.5 introduces the ability to restore Disk Image Protected Items directly into a new Hyper-V or VMware (vSphere or VCenter) virtual machines.
This brings:
Disk Image restores into Hyper-V or VMware (vSphere or VCenter) is available from the Comet Server web interface and from the Comet Backup desktop app. The following screenshot is from the Comet Server web interface.
Previously, deleting a default Protected Item from a Policy would delete the Protected Item from all Users and Devices the Policy is applied to. This meant it was impossible to remove the Default Protected Item from the Policy, but keep the Protected Item.
In Comet 24.12.5, new Comet Server web interface dialog prompts have been added to give admins greater control over what Default Protected Items should be kept and should be removed. This means admins can make changes to Policies at any time without impacting the Default Protected Items configured.
Changes compared to 24.12.3
When Comet skips a file during a Microsoft 365 Protected Item Backup, this can be due to the file being reported as Malware by Microsoft 365 or because Comet does not have the correct permissions to access the file. Now, Comet will list the exact URL of the file it failed to backup and list the reason why. This makes it much easier to debug and diagnose why a file was not backed up correctly.
After restoring LVM2 partitions, Comet will now automatically show the new devices in the recovery environment. This means you are able to confirm the Disk Image restore worked as expected without needing to leave the recovery environment.
Changes compared to 24.12.2
Self-Hosted Comet Server Only
To improve secure access to a Comet Server, in Comet 24.12.3 it is now possible to configure allowed IP addresses for admin accounts when logging in. This means Comet will only allow admin logins from a predefined list of IP addresses. These addresses can be configured in the Comet Server web interface.
Changes compared to 24.12.1
NOTICE: In this release the Windows System Backup Protected Item has been removed. All Windows System Backup Protected Items will be converted to Disk Image Protected Items upon upgrading.
In Comet 24.12.2, Impossible Cloud has been added as a new location when configuring a Storage Vault for a endpoint. This makes it easier to roll out Impossible Cloud as a cloud storage destination.
In Comet 24.12.2, Granular Restores from Disk Image, Hyper-V or VMware Protected Items will complete up to three times faster. This means faster restore times when you need to restore critical files as fast as possible.
In Comet 24.12.2, support for Impossible Cloud regions eu-east-1 and eu-west-1 has been added.
Changes compared to 24.12.0
Changes compared to 24.11.0
In Comet 24.12.0, it is now possible to group users in the Comet Server web interface. This will allow users belonging to a department, company, cost center, etc. to be grouped logically inside Comet. This makes it easier to find customers belonging to the same group as well as easily roll out policies for everyone assigned to a group.
In Comet 24.12.0, a new User setting is available to choose if devices that share the same user account login should back up Protected Items to a shared Storage Vault or isolated Storage Vaults. There are pros and cons of each option:
Pros of shared Storage Vaults: Data from multiple devices stored in a shared Storage Vault can take advantage of Comet's deduplication, reducing overall storage requirements.
Cons of shared Storage Vaults: Devices are able to see and restore all data from the other devices, and it is possible for backups to be delayed or missed on a device due to the Storage Vault being locked for retention jobs.
Pros of isolated Storage Vaults: Devices cannot see or restore data from other devices, and there is no risk of delayed or missed backup jobs due to the Storage Vault being locked.
Cons of isolated Storage Vaults: Backup data will not be deduplicated between devices increasing overall storage requirements.
To configure isolated Storage Vaults, when configuring a new user account select the "Provision storage vaults automatically ..." option under Storage Vault Provisioning. For existing users, head to the users account page and set the "Automatically create Storage Vaults for newly registered devices" option to a Storage Template.
To configure shared Storage Vaults, when configuring a new user account select the "Provision storage vaults once ..." option under Storage Vault Provisioning. For existing users, head to the users account page and set the "Automatically create Storage Vaults for newly registered devices" option to (none).
Self-Hosted Comet Server Only
In Comet 24.12.0, a new Admin Accounts setting is available to enforce that the password for the admin account is changed the next time they log in. This feature can be used to regularly enforce that passwords used to log in to a Comet Server web interface are changed.
Self-Hosted Comet Server Only
In Comet 24.12.0, a new License & Access setting is available to block users and IP addresses after repeated unauthorised logins. This feature should be used in combination with other security features such as Multi-Factor Authentication to protect against malicious attempts to gain access to your Comet Server.
Changes compared to 24.9.7
Changes compared to 24.9.6
Changes compared to 24.9.5
Changes compared to 24.9.4
Changes compared to 24.9.3
Changes compared to 24.9.2
Changes compared to 24.9.1
Changes compared to 24.9.1
Changes compared to 24.8.1
.avhdx
filesChanges compared to 24.6.8
Changes compared to 24.6.7
Changes compared to 24.6.6
Changes compared to 24.6.5
Changes compared to 24.6.4
Changes compared to 24.6.3
Changes compared to 24.6.2
Changes compared to 24.6.1
Changes compared to 24.6.0
Changes compared to 24.5.1
Changes compared to 24.3.8
Changes compared to 24.3.7
Changes compared to 24.3.6
Changes compared to 24.3.5
Changes compared to 24.3.4
Changes compared to 24.3.3
Changes compared to 24.3.2
Changes compared to 24.3.1
Changes compared to 24.3.0
Changes compared to 23.12.9
Changes compared to 23.12.8
Changes compared to 23.12.7
Changes compared to 23.12.6
Changes compared to 23.12.5
Changes compared to 23.12.4
Changes compared to 23.12.3
Changes compared to 23.12.2
Changes compared to 23.12.1
Notice: The deb and rpm installers for Comet Server now require glibc 2.25 or later. There are no changes to the system requirements for the tar package version of Comet Server.
Changes compared to 23.12.0
Changes compared to 23.11.1
Changes compared to 23.9.10
Support new "Latest VM State (Changed Block Tracking)" option for Hyper-V for improved backup performance.
Added support for VMware ESXi hosts running on a free license. Comet now supports both the free and paid versions of VMware for backups and restores.
Added the ability to enforce policies created by a top-level administrator onto tenant administrators and tenant users. This allows top-level administrator to enforce settings and preferences across an entire Comet Server.
Changes compared to 23.9.9
Changes compared to 23.9.8
Changes compared to 23.9.7
Changes compared to 23.9.6
Changes compared to 23.9.5
Changes compared to 23.9.4
Changes compared to 23.9.3
Changes compared to 23.9.2
Changes compared to 23.9.1
Changes compared to 23.9.0
Changes compared to 23.8.0
Changes compared to 23.6.11
Changes compared to 23.6.10
Changes compared to 23.6.8
Changes compared to 23.6.7
Changes compared to 23.6.6
Changes compared to 23.6.5
Changes compared to 23.6.4
Changes compared to 23.6.3
Changes compared to 23.6.3
MonthOffset
was set to 0 when configured using the API or editing the raw user profileMonthOffset
value not being respected when set to 31 (the 31st) and being changed to 30Changes compared to 23.6.1
Changes compared to 23.5.0
NOTICE: The "Run when PC Starts" option will now also apply to devices waking up from Sleep
Changes compared to 23.3.8
Changes compared to 23.3.7
Changes compared to 23.3.6
AdminPoliciesNew
APIFileOptions
that allow users to log all events to file for audit or other purposesChanges compared to 23.3.5
Changes compared to 23.3.4
Changes compared to 23.3.3
Changes compared to 23.3.2
Changes compared to 23.3.1
.vhdx
files using a custom path structureChanges compared to 21.3.0
Changes compared to 23.2.0
This release makes some changes to how codesigning works in Comet Server, which includes bundling a PKCS#11 engine.
Changes compared to 22.12.7
Changes compared to 22.12.6
Changes compared to 22.12.5
Changes compared to 22.12.4
SECURITY NOTICE: This version of Comet Server fixes an important security issue related to administrator accounts. If you share your Comet Server with tenant administrators or limited-permission administrator accounts, we strongly recommend upgrading at the earliest possibility.
Changes compared to 22.12.2
Changes compared to 22.12.1
Changes compared to 22.12.0
Changes compared to 22.11.0
Changes compared to 22.9.9
Changes compared to 22.9.8
Changes compared to 22.9.7
Notice: The Authenticode certificate used by Comet has been renewed. When installing the Windows version of Comet Server or Comet Backup, you may see Windows Defender Smartscreen prompts for approximately one week as the replacement certificate builds reputation.
Changes compared to 22.9.5
Changes compared to 22.9.4
Changes compared to 22.9.3
Changes compared to 22.9.2
Changes compared to 22.9.1
This brings the behavior in line with creating new Protected Items in the Comet Backup desktop app: a wizard is used for initial creation, to help guide you through the process, but after initial creation a tabbed dialog is used, for quickly jumping to any setting.
Changes compared to 22.9.0
Remove support for running the Comet Backup client on Windows Vista, Windows Server 2008, and macOS 10.10 "Yosemite". The new minimum version is Windows 7, Windows Server 2008 R2, and macOS 10.11 "El Capitan"
Webhook and websocket events for the top-level Tenant will now include events from tenants
?allowList=4100
)Changes compared to 22.8.0
Previously this was only possible through API or hand editing the server config file.
Changes compared to 22.6.9
Changes compared to 22.6.8
Changes compared to 22.6.7
Changes compared to 22.6.5
Changes compared to 22.6.4
AdminDispatcherListActive
API call now takes an optional UserNameFilter
parameter to restrict fetched resultsEndTime
/ Duration
values for incomplete jobs in the AdminGetJobsForDateRange
APIChanges compared to 22.6.3
Changes compared to 22.6.3
Changes compared to 22.6.1
Changes compared to 22.6.0
Changes compared to 22.5.1
Comet Server supports using external authentication sources for admin accounts. If you have a highly-available LDAP server infrastructure using multiple servers, such as an Active Directory failover cluster with primary/fallback domain controllers, you are now able to configure multiple LDAP server addresses in Comet Server. When an admin user tries to authenticate at the Comet Server login screen, if a connection to the first entry on the list fails, Comet will try the remaining entries on the list before denying the authentication attempt.
Update Thai translation
Improve handling of temporary files on Synology devices using the SPK client installer
During backup jobs, Comet saves some temporary files in the system temporary directory. In the Synology DSM operating system, the default directory for temporary files (/tmp
) is a RAM disk. With this change, Comet switches to use a custom temporary directory. This reduces the RAM requirements for running Comet Backup on Synology devices, meaning that large backup jobs on RAM-constrained Synology devices will no longer cause slowdown or freezes due to running out of RAM.
Thank you to our partners for getting the Chinese (Traditional) localization started! The best-quality translations come from our customers, who better understand the software and the backup industry. We appreciate any translation assistance that is offered.
If you want to correct a translation in Comet, or if you want to translate Comet into a new language, further information is available via CometBackup/translations at GitHub.
This release comes with two key improvements to server self backup. Using the new slider component you can select 'faster' or 'smaller' to optimize the compression levels for the backup. A new option has been added to exclude the job database from the Comet Server self backup. It is best practice to keep regular backups of your comet server. Some very large databases can cause this to be a high cpu operation. In this case, we recommend having two backup schedules, one very regular backup that excludes the job database and another less regular backup that includes all databases.
We have also improved the onboarding experience for DSM-7. There is added guidance on how to configure permissions in the DSM 7 Synology SPK for the Comet client
Changes compared to 22.3.5
Comet Backup supports many different cloud storage providers (e.g. SFTP or S3-compatible) if you bring your own storage credentials. If you have configured Comet Backup to back up directly to a cloud storage provider, you should avoid reusing storage credentials across customers. For each customer, you should either create new cloud storage credentials manually; or proxy the data through Comet Server Storage Role; or ideally, have Comet Server allocate new cloud storage credentials automatically. Previous versions of Comet Server supported this "Requestable" provisioning for Backblaze B2, Wasabi Cloud Storage, and custom HTTP integrations. The latest version of Comet Server extends this support to Amazon AWS and to custom IAM-compatible cloud services.
Changes compared to 22.3.4
Fix an issue with the time zone of Synology devices being detected by Comet as UTC even when the device is set to another time zone
Fix an issue with email reporting table allowing duplicate email entries
Changes compared to 22.3.3
Changes compared to 22.3.2
This version contains an important security bugfix. Please upgrade as soon as possible.
Changes compared to 22.3.1
Changes compared to 22.3.0
We have improved Wasabi storage location detection. Try it out with the new Wasabi region "ca-central-1" based in Toronto, Canada.
Changes compared to 22.2.0
backup-tool
command to output the unique device IDChanges compared to 21.12.7
Changes compared to 21.12.6
You can get started with Synology by downloading your .spk
package from the Comet Server downloads page. For more details, check out the documentation.
The quick search component is now available in the header bar of your Comet Server. You can search for Storage Vaults, Protected Items and User Profiles.
Changes compared to 21.12.5
Changes compared to 21.12.4
You can browse and restore single files and/or folders from Disk Image backup by selecting "Restore files and folders" from the restore method wizard. The feature currently only supports for NTFS.
Changes compared to 21.12.3
Changes compared to 21.12.2
You can now select "If last job was Missed" from the schedule dialog. When a device re-connects to the server and detects that it has recently missed a backup, it will immediately start a new backup job. This replaces the previous option "When PC starts, if last job was missed". The "If last job was Missed" option bypasses any issues with fast startup, hibernation or sudden power off interrupting a backup schedule.
Changes compared to 21.12.1
Changes compared to 21.12.0
Deprecation: Comet Server no longer supports Windows Vista or Windows Server 2008. Note that the Comet Backup desktop app continues to support Windows Vista and Windows Server 2008; this only affects Comet Server. Windows Server 2008 R2 is still supported for both Comet Server and the Comet Backup desktop app.
Deprecation: Removed support for U2F for two-factor authentication for admin users due to the impending removal of U2F from browsers (see !https://groups.google.com/a/chromium.org/g/blink-dev/c/xHC3AtU_65A). Existing U2F 2FA will be automatically migrated to use WebAuthn when the Comet Server instance is upgraded; this requires no action on an admin's part, and the same U2F devices can continue to be used.
Changes compared to 21.11.1
Changes compared to 21.9.11
This release includes a change to the format of Comet Server's comet-jobs.db3 file. When upgrading to this version, there may be a one-time startup delay of around ~30 seconds as the database file format is migrated.
Changes compared to 21.9.9
Changes compared to 21.9.8
Changes compared to 21.9.7
Changes compared to 21.9.6
Changes compared to 21.9.5
Changes compared to 21.9.4
Changes compared to 21.9.3
Changes compared to 21.9.2
Changes compared to 21.9.1
Changes compared to 21.9.0
Changes compared to 21.6.16
Changes compared to 21.6.14
Changes compared to 21.6.13
Changes compared to 21.6.12
Changes compared to 21.6.11
Changes compared to 21.6.10
Changes compared to 21.6.9
Changes compared to 21.6.8
Changes compared to 21.6.7
Changes compared to 21.6.6
Changes compared to 21.6.5
Changes compared to 21.6.4
Changes compared to 21.6.3
Changes compared to 21.6.2
Changes compared to 21.6.1
Changes compared to 21.5.0
Changes compared to 21.3.7
Changes compared to 21.3.6
--also-removed-saved-passwords
was supplied but no saved passwords were foundChanges compared to 21.3.4
Changes compared to 21.3.3
Changes compared to 21.3.2
Changes compared to 21.3.1
Changes compared to 21.3.0
Changes compared to 21.2.1
Changes compared to 20.12.5
Changes compared to 20.12.1
Changes compared to 20.11.2 and 20.12.0
Changes compared to 20.11.1
/ISLOCALSYSTEM="yes"
silent installation flag to force the Comet Backup desktop app's background service to use LOCAL SYSTEM authenticationTrustXForwardedFor
option in cometd.cfg to support customer IP addresses behind a reverse proxy such as nginxChanges compared to 20.9.10
Changes compared to 20.9.9
Changes compared to 20.9.8
Changes compared to 20.9.7
/TRAYICON=disable
command-line parameter and HKLM\Software\backup-tool\TrayIcon
registry key, to prevent creating tray icon when installing Comet Backup on WindowsChanges compared to 20.9.6
Changes compared to 20.9.5
/SHORTCUT=disable
command-line parameter and HKLM\Software\backup-tool\Shortcuts
registry key, to prevent creating desktop and Start Menu shortcuts when installing Comet Backup on WindowsChanges compared to 20.9.4
Switching to use the PAX format causes spurious "PaxHeaders.0" directories to appear in current (19.00) versions of 7-Zip. This should be resolved soon by a new 7-Zip update. There is no such problem using GNU Tar or bsdtar/libarchive.
Changes compared to 20.9.1
Changes compared to 20.9.2
Changes compared to 20.8.2
AdminCreateInstallToken
API used with /TOKEN=
parameter)Changes compared to 20.6.7
Changes compared to 20.6.6
Changes compared to 20.6.5
Changes compared to 20.6.4
Changes compared to 20.6.2
localhost
or 127.0.0.1
in the Comet Backup desktop appChanges compared to 20.6.1
Changes compared to 20.6.0
Changes compared to 20.5.0
Changes compared to 20.3.7
Changes compared to 20.3.6
Changes compared to 20.3.5
Changes compared to 20.3.4
Changes compared to 20.3.3
Changes compared to 20.3.2
PLEASE NOTE: For privacy reasons, these features may be disabled by the customer using the "Allow administrator to view file names" option.
Changes compared to 20.3.1
PLEASE NOTE: this is a limited-security feature only, protecting only (A) registering new devices; (B) opening the desktop app; and (C) logging in to the Comet Server web interface as an end user. Because backup jobs need to run unattended without 2FA prompting, this feature does not provide full 2FA protection in all cases.
Changes compared to 20.3.0
Changes compared to 20.2.0
Changes compared to 19.12.7
.app
package, to comply with Apple TN2206.Changes compared to 19.12.6
Changes compared to 19.12.5
Changes compared to 19.12.4
Changes compared to 19.12.3
Changes compared to 19.12.2
Changes compared to 19.12.1
Changes compared to 19.12.0
Changes compared to 19.11.0
Changes compared to 19.9.6
Renew our company's codesigning certificate for Windows. This may cause temporary SmartScreen popups for 1-2 weeks while reputation is rebuilt
Hide Android 'coming soon' message in the Comet Server web interface, as this doesn't need to be customer-facing at this stage
Changes compared to 19.9.4
Changes compared to 19.9.3
This update introduces a new file storage format for Comet Server's jobs database file. The previous file format will be upgraded on first run. Older versions of Comet Server cannot read the new format; if you want to roll back the Comet Server version, you will lose job history unless you first recover the comet-jobs.db file from either the .old
file (produced by the upgrade process) or from your Server Self-Backup archives.
Changes compared to 19.9.2
Changes compared to 19.9.0
Changes compared to 19.8.1
Changes compared to 19.6.7
Changes compared to 19.6.5
Changes compared to 19.6.4
Changes compared to 19.6.3
Changes compared to 19.6.1
Changes compared to 19.5.1
Changes compared to 19.3.12
Changes compared to 19.3.10
Changes compared to 19.3.9
Changes compared to 19.3.8
Changes compared to 19.3.7
Changes compared to 19.3.6
Changes compared to 19.3.5
Changes compared to 19.3.3
Changes compared to 19.3.2
Changes compared to 19.2.0
Exclude ".dropbox.cache/placeholder.***" reparse points
Downgrade-incompatible on Linux
Changes compared to 18.12.1 and 18.11.4
Changes compared to 18.12.0 and 18.11.3
Changes compared to 18.11.2
Changes compared to 18.9.8
Changes compared to 18.9.7
Changes compared to 18.9.6
Changes compared to 18.9.5
Changes compared to 18.9.2
Changes compared to 18.9.0
Changes compared to 18.8.3
Remove support for Internet Explorer 8 (IE 9 or later is now required; IE 9 can be installed on Server 2008 via Windows Update)
Remove support for replacing CSS in the Comet Server web interface (may be reinstated in a better way in the future)
Remove support for TOTP-only logins with no supplied administrator password
Changes compared to 18.6.8
Changes compared to 18.6.6
Changes compared to 18.6.5
Display more detailed explanation when Let's Encrypt refuses to provide you an SSL certificate
Display more detailed explanation when the Delegate service fails to launch from saved credentials
Changes compared to 18.6.3
Changes compared to 18.5.5 and 18.6.1
Changes compared to 18.5.3
Changes compared to 18.3.13
Changes compared to 18.3.12
Changes compared to 18.3.11
Changes compared to 18.3.10
Changes compared to 18.3.7
Changes compared to 18.3.5 and 18.2.5
Changes compared to 18.3.4 and 18.2.4
Changes compared to 18.3.3 and 18.2.3
Changes compared to 18.3.2
Changes compared to 18.2.1 and 18.3.1
Changes compared to 18.3.0
Changes compared to 18.2.0
18.5.NEXT
Changes compared to 17.12.8
Changes compared to 17.12.7
Changes compared to 17.12.3
Changes compared to 17.12.1
Changes compared to 17.11.1
Changes compared to 17.9.8
Changes compared to 17.8.7 and 17.9.6
Changes compared to 17.8.6 and 17.9.5
Changes compared to 17.9.3
Changes compared to 17.9.0
Changes compared to 17.8.3
Changes compared to 17.6.13
Changes compared to 17.6.11
Changes compared to 17.6.10
Changes compared to 17.6.9
Changes compared to 17.5.5 and 17.6.8
Changes compared to 17.6.7
Changes compared to 17.6.5
Changes compared to 17.6.4
Changes compared to 17.6.3
Changes compared to 17.6.0
Changes compared to 17.5.1
Changes compared to 17.3.9
Changes compared to 17.3.8
Changes compared to 17.2.9 and 17.3.6
Changes compared to 17.2.7 and 17.3.4
Changes compared to 17.2.2