Thanks for the information as well as the found cause of this problem.
Yes, I will take a look at properly fixing this in the next update. Maybe even removing this update fix completely, since that is about for a year there now already and no longer really required.