Strange results on hasp_read() and hasp_write() -> memory written gets reverted.

We have some features and a read/write memory segment in our product.

During testing, we created a SL-UserMode license and updated with v2c/rehosted the license a few times.

Now this particular license is generating a strange result that the read/write memory gets reverted to old values even when performing hasp_write() or update().

This happens even when using the Sentinel ToolBox program

Steps to reproduce the problem with this license

1. Start Sentinel ToolBox or our app, and login to a feature -> status ok

2. call hasp_read() ->  status ok values displayed are ABCD

3. change the value to new value XYZ and call hasp_write() -> status ok

4. hasp_read() or logout/login then hasp_read() -> displays the changed value XYZ

5. terminate ToolBox or our app and restart and login and hasp_read() -> value gets reverted back to ABCD

Instead of step 3, if we apply a new memory value in EMS entitlement and apply the v2c file, the result is the same: Just soon after update, the new results are reflected, but if we restart the application, all the memory is initialized to same very old memory ABCD.

We tried running the program with admin privilege during write/update api calls, but the results are same.

This hasnot happened to other license or the demoma licenses. 

Version of LDK we are using is 7.9

Can you please help or give any advice on using read/write memory?

Thank you