As VMware reps have repeatedly stated in this forum, they do not comment on upcoming releases. So there is no way to find out from this forum when the next version of Fusion will be released with a fix for this issue.
That does not mean VMware is not working on a fix. VMware is clearly working on a fix, since they asked for volunteers to help test one. But it does mean that they won't tell us when a new version with the fix will be released, no matter how much we ask for a status update and criticize them for not providing one.
Thus the only thing you do when you post such questions/criticisms in this discussion is waste the time of everyone paying attention to the discussion. Including folks like me who are just as anxious as you are to get a fix for the bug (and just as critical of VMware for not providing any status updates in advance of a release). So please refrain from doing that.