This behavior ought to be fixed in the latest Service Release Candidate for 7.4 which, I believe, is slated to be released sometime later today, if all goes well. Feel free to switch to the Release Candidate and give it a try to confirm though! If not, if you just wait until tomorrow, the update should fix it. Please let us know if it does not.