Let me check with the software team regarding this. One quick suggestion I can make is uninstall the previous one and install the new one but that is a long process.
Will let you know the feedback from software team.
So, did any Eureka moment happen?
There is another problem, which starts from 3.13.1 (version 3.13.3 not solved it) - if any cyrilic symbom exists in the path to the .hex file the programmator say "FAILED! File does not exist or corrupted". Before this revision all was ok.