Important: Downgrading the device to an older software or firmware version is not supported and can potentially cause data loss or impairment to the device functionality.

Version 6.3.1
Released 4/20/2020

Supported Devices: Sentry K300

New Features:

- Added support for Device Sanitization, resets the device without needing to be reactivated

- Added support for Anti-Malware Quarantine, isolating infected files stored on the device.

- Added support for reformatting as fixed or removable media

Other Changes:

- Improved ZoneBuilder Certificate Validation, added certs fingerprint validation

- Improved AD Credential prompt, auto-fills current logged in user

- Improved Reset status reporting in SafeConsole

- If a unique token is available in the Windows registry, the user will not see the unique token prompt

- Improved Reset Reporting in SafeConsole.

- Drive size and usage in SafeConsole

-Trusted accounts and Quarantined files tables have been changed to a light background for easier viewing

Version 6.3.0
Released 1/3/2020

Supported Devices: Sentry K300, Sentry One, Sentry One Managed, H300, H350, Sentry EMS


New Features:

- Support for Device Audit Mode (Requires SafeConsole 5.6, not compatible with K300)

- Support for Restrict device login until Anti-malware update has finished (Requires SafeConsole 5.6)

- Added support for Custom URL for Anti-Malware definitions in SafeConsole

- Added support for Unlock Screen Message (Requires SafeConsole 5.6)

- Added Contact Info (Email address and phone number) from SafeConsole policy to the password help screen on the device

Other Changes:

- Remove two-minute wait after unlock before updating device policy

- Only allows the device to be unlocked once per recovery code if offline (Requires the device to be unlocked while connected to SafeConsole Server before a new recovery code is generated)

- Disables reformat button in control panel if 'Disable Users from resetting device policy' is enabled

- Improved pre-registration and basic to managed functionality

Known Issues:

-  Existing unlock message is wiped when basic devices are updated to v6.3 

Version 6.2.2
Released 10/18/2019

Supported Devices: H300, H350


New Features:

- MacOS 10.15 Catalina support for H300 and H350 devices

Version 6.2.1
Released 08/12/2019

Supported Devices: H300, H350


New Features:

- Prevent users from accidentally resetting their drives, by requiring manual user interaction

- New reset info stored on the device and sent to SafeConsole during next registration

Bug Fixes:

- Resolved Audit Logs not recording resets to SafeConsole for H300/H350 devices

- Resolved a visual UI issue regarding the device hardware ID when managed with SafeConsole

- Resolved a visual UI issue with strong password enforcement

Known Issues:

- MacOS 10.15 Catalina not supported on H300 and H350 devices.

Version 6.2.0
Released 06/28/2019

Supported Devices: Sentry K300, Sentry One, Sentry One Managed, H300, H350, Sentry EMS


New Features:

- Full 64bit macOS Support

- Support for automatic Updates through SafeConsole with next available device update

- Support for strong password enforcement (FIPS compliant password) 

        - Can be controlled by policy on SafeConsole

        - User optional on devices activated against EMS

- Minimum password length requirement for all devices is now 8 characters. 

- Support for newly added SafeConsole policy, "Control Panel Application List"

- Support for SafeConsole policy, Publisher

- Support for newly added Maximum number of logins without a connection to SafeConsole as defined in the Device State policy

- Support for Web Proxy Auto-Discovery Protocol on both Windows and macOS

Bug Fixes:

- Fix for File Audit Logs regarding Unicode characters

Known Issues:

- Updated device version is not displayed correctly in EMS after updating Sentry devices using v6.2 updater

- MacOS 10.15 Catalina not supported on H300 and H350 devices.

Version 6.1.5
Released 03/08/2019


New Features:
- Added SafeConsole Support to the K300

- Implement StandAlone mode for the K300

Bug Fixes:

- Error when loading antimalware could trigger a false positive malware detection

- Crashes when registering to SafeConsole outside Trusted Network

Known Issues:

- K300 can be unlocked using the Password Reset Code from SafeConsole only once. If the password is changed and subsequently forgotten before checking into SafeConsole, data can be lost. It is important that users immediately unlock their device in SafeConsole mode after a password reset. Resetting password will also reset the available Standalone logins. 

Version 6.1.2
Released 08/06/2018

New Features:
- Anti-Malware support on MacOS (EMS and SafeConsole)

- File Auditing on MacOS (SafeConsole only)

- File Blocking on MacOS (SafeConsole only)

- Hardware Id field added to Device Info tab and device Configuration dialog (opened by ctrl+click on the logo)

Known Issues:

- MacOs users updating H3xx device with version 6.1 and older need to rename the private partition manually. This can be done before or after the update to v6.1.2. If the private partition is not renamed, users will experience Control Panel issues with Application screen, capacity meter and Anti-Malware.

Suggested steps:

1) Unlock the drive

2a) If you are using Windows:

  • Using Explorer, navigate to “Computer”,  right click on the H3xx device private partition and select "Properties"

  • In the “General” tab, change the label from  "PRIVATE USB" to "PRIVATE_USB"

  • Click Apply and Save

2b) If you are using MacOS

  • Using Finder, right click on the H3xx device private partition and select "Rename PRIVATE USB"

  • change the label from  "PRIVATE USB" to "PRIVATE_USB" 

3) Lock & unlock again

4) To proceed with the update unlock the drive on Windows computer and run IKUpdater_H300_H350_v6.1.2

Note: if you have already updated your device to v6.1.2 and experience described issues on MacOS, please follow steps 1-3 above. 

- Device info incorrectly shows the H350-Enterprise PID on all H300 and H350 devices in Device Info under device settings. This does not affect the actual PID of the device and should be ignored.