But in any case, this pretty much confirms that I'm seeing the same issue as these previous users, it's just that a VirtualBox update fixed it for most of them and not for me. Although one user at the end of the thread in late October reports that they were still seeing this problem.