Chrome Resets profile each start

I configured Chrome and added Secure Lockdown Chrome Edition.  I set it to use Chrome in Kiosk mode (most other settings I just used the default).

Every time Chrome starts, it creates a new profile and forgets all settings.  I've turned Secure Lockdown on / off.  Disabled all Chrome settings in Secure Lockdown.  Removed and reinstalled Chrome.  Removed Chrome, deleted chrome registry entries and folders in appdata, rebooted, reinstalled chrome.  Problem still persists.  Chrome starts fresh every time with a new profile.

I've searched the Internet, but have not found anything that can explain this.  Hopefully someone at Inteset knows what's happening and can help me get it straightened out.

This is a known bug. There is a fix coming that will be posted by the end of day today on our website (just go to the product page press the Download button).

After installing the latest version, the profile delete and recreate problem still persisted.

I ended up going another route.

This is not the case. Make sure you have Build ver 2.00.190

Using build 192 - same problem - need to keep the home page and other settings but they're being wiped every time Chrome is closed and reopened automatically.  ideas?

Please download the latest release of Secure Lockdown - Chrome Edition from our website. Also uncheck (disable) the Chrome Lockdown > General Options > Delete Cache option.

We want the delete cache option checked as the kiosk handles payment information.  How can we keep this checked and still have the defauly homepage stay set correctly?

We will be separating the Delete Cache and "Reset Chrome" feature in a future release, but currently the two features are combined.

The latest Secure Lockdown - Chrome Edition release now separates Delete Cache and Reset Chrome.

I have just upgraded from 2.0.190 to the latest version .199 and was seeing this issue.

Thought it worth mentioning that I disabled the delete cache option, enabled SL. Then disabled SL and enabled it again and that has fixed the issue. Or maybe a combo of that and some other uninstall / reinstall activities...