There have been at least two posts here of affected users (one of which required substantial amounts of troubleshooting) and we can assume that there’s a much higher number of affected users out there.
Thank you for the suggestion. However fixup is already on the way. Today we released 6.4.4 release candidate containing it.
If everything else goes well, 6.4.4 should reach stable branch very soon.