If you're needing to roll out/install Cradle from an IT admin perspective for a whole organisation, this is a good place to start.
Please note this is technical information for IT admins. To install Cradle on your Windows machine, please visit our main install page here.
.appx
For Windows users, Cradle is supplied in the form of an appx bundle. This is the file format that Microsoft provide on the MS Windows Store.
If you're trying to script the installation or install it on Windows Server 2016, you can download the signed app package here. If you're installing on architecture other than x64, please choose your download from this table.
The current version available at these links is 3.5.4, released on 3-Nov, 2023.
Full change-log can be found here.
Installation Options
You can install the appx bundle in several ways. We will give high level advice here, but we recommend that you install the app according to your own practices and policies.
Please note that any previous versions prior to the MS Store version (14.4.1 and earlier) must be uninstalled from the PC before installing this version. The Cradle directory in the Roaming folder should also be removed.
UI Installation
You can simply download the app link above, and double-click to install the appx. This requires Windows 10 (and won't work unless the store is available)
Installing with Powershell
You can install the app using the Add-AppxPackage command in PowerShell. We'd suggest reading through the MS documentation to find the most appropriate method of installation for your business.
PS C:\> Add-AppxPackage -Path "C:\path\to\Cradle.appx"
If you need to script the uninstallation of the appx, you can use the following PowerShell command.
PS C:\> Get-AppxPackage CradleLimited.CradleDesktop | Remove-AppxPackage
.exe or .msi
You must manage updates yourself, and check Cradle's change-log on your own schedule, to make sure that you have the latest version of Cradle on your computers.
Version 3.0.1 and onward of the exe installer will check for updates upon restart and notify the user if an update is present. Restarting the app will trigger the update to install. The MSI installer will not update on its own.
| Version | .exe Download Link | .msi Download Link | Release Date | Support Ends |
| 3.5.4 | Download | 3-Nov-2023 | 03-May-2024 | |
| 3.5.3 | Download | 31-Oct-2023 | 30-Apr-2024 | |
| 3.4.5 | Download | 23-Jun-2023 | 23-Dec-2023 | |
| 3.4.4 | Download | 14-Jun-2023 | 12-Dec-2023 | |
| 3.4.3 | Download | 12-Jun-2023 | 12-Dec-2023 | |
| 3.4.2 | Download | 18-May-2023 | 18-Nov-2023 | |
| 3.2.0 | Download | Download | 18-Oct-2022 | 18-Jun-2023 |
| 3.1.1 | Download | Download | 27-Jul-2022 | 27-Jan-2023 |
| 3.0.1 | Download | Download | 29-Apr-2022 | 29-Oct-2022 |
| 2.0.24 | Download | Download | 30-Sep-2021 | 30-May-2022 |
| 2.0.23 | Download | Download | 24-Sep-2021 | 24-Mar-2022 |
| 2.0.20 | Download | 7-Sep-2021 | 7-Mar-2022 | |
| 2.0.14 | Download | 19-Aug-2021 | 19-Feb-2022 | |
| 2.0.8 | Download | 5-May-2021 | 5-Sep-2021 | |
| 2.0.7 | Download | 28-Apr-2021 | 28-Oct-2021 | |
| 2.0.5 | Download | 20-Apr-2021 | 20-Oct-2021 | |
| 2.0.1 | Download | 31-Mar-2021 | 30-Sep-2021 | |
| 1.14.1 | Download | 25-Nov-2020 | 25-May-2021 |
URL Handlers for MSI Installs
When using the MSI installer, you'll likely need to add registry keys that create new URL handlers. Add the following registry entries:
HKCU "Software\Classes\callto" "" "URL:callto"
HKCU "Software\Classes\callto" "URL Protocol" ""
HKCU "Software\Classes\callto\shell\open\command" "" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
HKCU "Software\Classes\tel" "" "URL:tel"
HKCU "Software\Classes\tel" "URL Protocol" ""
HKCU "Software\Classes\tel\shell\open\command" "" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
HKCU "Software\Classes\cradle" "" "URL:cradle"
HKCU "Software\Classes\cradle" "URL Protocol" ""
HKCU "Software\Classes\cradle\shell\open\command" "" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
HKCU "Software\Classes\cradle.callto\shell\open\command" "" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
HKCU "Software\Cradle\Capabilities" "ApplicationName" "Cradle"
HKCU "Software\Cradle\Capabilities" "ApplicationDescription" "Cradle Desktop"
HKCU "Software\Cradle\Capabilities\URLAssociations" "tel" "cradle.callto"
HKCU "Software\Cradle\Capabilities\URLAssociations" "callto" "cradle.callto"
HKCU "Software\Cradle\Capabilities\URLAssociations" "cradle" "cradle.callto"
HKCU "Software\RegisteredApplications" "Cradle" "Software\Cradle\Capabilities"
HKLM "Software\Microsoft\Windows\CurrentVersion\Run" "Cradle" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
HKCU "Software\Microsoft\Windows\CurrentVersion\Run" "Cradle" "$INSTDIR\${APP_EXECUTABLE_FILENAME} %1"
The first line, for example
HKEY_CURRENT_USER
SOFTWARE
Classes
callto
"" = "URL:callto"
Cradle will then show up as a possible handler for these protocols:
