This should indeed be fixed in the next update (no ETA yet). It was marked to be fixed in the last major update, but the fix wasn't complete until after the update was finalised. For the 3.6.58.1306 hotfix, it was just specific new/critical fixes added to an update.