So, perhaps the Vista plugin is somehow interfering wioth the Constructor macro?
Yes, that is the same what I though. And my other thought was that maybe their save routine interfering with the Destructor macro or with the Custom fields saving.
But I looked all of these through and I don't see any possibility for that, however I don't see what the plugin is doing ... what I tested was is I saved stuff from a plugin and also saved stuff with the destructor macro the same time and debugged that and it works all OK. I also tested the 2017 screenset for saving and loading things back and that also works fine.
So, there must be something in the plugin which causes the issue, but I have no idea yet about how.
It would be one useful info though to know what I mentioned previously is to check if the keys not save or if they save just not loading back. Knowing this would narrow the location of the issue to the saving or loading part.