Western Digital does not provide a versioned download URL. This means the installer binary's checksum will periodically change, and a newly released software version will break this package version. Consequently, FOSS users should generally consider older package versions to be obsolete and unsupported. Obsolete package versions may be unlisted if the Chocolatey CDN has not cached the download before obsoletion.
Consider internalizing this package if you require a stable binary, or the ability to install this specific version after a new version is released.
Two installer packages are published for Western Digital Dashboard: an online bootstrapper and offline (standalone) installer. This package consumes the offline installer to ensure the binary behaves consistently (i.e. always installs a given version), and to avoid an external dependency on connectivity to Western Digital's servers. Publishing of the offline installer package is occasionally delayed or skipped, so the packaged version may therefore lag behind what is offered via the software's update functionality (i.e. via the online bootstrapper).
Legacy versions of Western Digital Dashboard's installer (i.e. prior to installer version 5.3.2.2 and application version 3.7.2.5) did not support a silent (un)installation option. Upgrade operations will typically require the currently installed version to be uninstalled first. To ensure compatibility with legacy installations, the package depends on AutoHotkey to implement a best-effort workaround of scripting an unattended uninstallation via GUI automation. GUI automation is not 100% reliable, and may occasionally fail or require manual input to complete.
When Western Digital Dashboard is being silently uninstalled (during either a package upgrade or uninstall operation), you may see the following message printed to stderr:
ERROR: The process "Dashboard.exe" not found.Note that this only refers to an uninstall step that involves terminating the process if it is currently running. If Dashboard is not currently running, it is not indicative of an error condition, and can be safely ignored.
Because this is a non-critical error, it's recommended to ensure the failOnStandardError feature is disabled when upgrading/uninstalling this package.
For future upgrade operations, consider opting into Chocolatey's useRememberedArgumentsForUpgrades feature to avoid having to pass the same arguments with each upgrade:
choco feature enable --name="'useRememberedArgumentsForUpgrades'"