Microsoft’s next major update to Windows 10 is scheduled to be generally available around the end of May (though this is subject to change). This release, called Windows 10 version 1903 is expected to include a change in how certain USB mass storage drives are listed in the system hardware list. This change is expected to cause the Kanguru Defender Manager application (KDM*.exe) that runs on our hardware encrypted drives to be unable to communicate with the drive and therefore data on stored data unable to be accessed. Although the data itself on the drive will not be impacted, a KDM application update will be needed in order to gain access to it and to continue to login to the drive. The following is an example of the error any non-updated device will receive when attempting to use on such a system:
This existing Windows architecture has been in place for over 15 years with no changes, so this has been an unexpected situation to resolve. While we are attempting to work with Microsoft to revert this change, we have readied updates to our KDM application that are ready for download.
We recommend that these updates be applied to your Defender drives as soon as possible to avoid any complications from this Windows 10 update.
To assist with the update process, we will be starting to push these updates starting May 22, 2019 to eligible drives (as identified by the table below). Once the push updates are available, eligible KDM versions will receive an update notification after you successfully login, or you can manually check for update availability by clicking the “Check for Updates” option in the Kanguru system tray menu.
Note: Please contact your IT administrator if you are utilizing KRMC Enterprise to access the KDM Enterprise updates.
|
Product |
Minimum KDM version to receive push update |
Minimum KDM version that will work with Windows 10 version 1903 |
Download Links to Windows 10 version 1903 compatible KDM Cloud Updates |
Download Links to Windows 10 version 1903 compatible KDM Enterprise Updates |
|
|
|
|
||||
|
Defender 3000 |
4.0.6.5 |
5.1.4.0 |
|||
|
|
|||||
|
Defender Elite300 |
4.0.6.5 |
5.1.4.0 |
|||
|
|
|||||
|
Defender Elite30 |
4.0.6.5 |
4.1.1.9 |
|||
|
|
|||||
|
Defender 2000 |
4.0.6.5 |
5.1.4.0 |
|||
|
|
|||||
|
Defender Elite200 |
4.0.6.5 |
5.1.4.0 |
|||
|
|
|||||
|
Defender HDD/ SSD/ HDD300/ SSD300 |
1.0.5.8 |
1.0.8.4 |
|
||
|
|
|
||||
|
Defender Elite |
2.7.8.3 |
2.7.9.0 |
|||
|
|
|||||
|
Defender V2 |
Push update option not available. |
2.0.2.8 |
|||
|
|
|||||
|
Defender Basic+ |
4.0.6.5 |
4.1.1.9 |
|||
|
|
|||||
|
Defender Basic |
4.0.6.5 |
4.1.1.9 |
N/A |
||
Comments
0 comments
Article is closed for comments.