virtualbox.org

I gave it a try. Using Windows 10 1809 on both host and guest.

After installing Version 6.0.0_BETA2 r126642 I was able to start the client but was still experiencing the mouse cursor issue. I tried installing the guest components but it blue screened the guest instance (looked like something about WDDM). After the restart the mouse was still broken but in a different way. Now I see two cursors and the further I go towards the bottom left of the screen the further apart they become.
If I turn off mouse integration, like I was doing before to fix this issue, the cursor works as expected.

ChangeNick00Name wrote:After installing Version 6.0.0_BETA2 r126642

I meant the Development Builds, sorry about any confusion.

Okay, after installing the guest additions everything looked like it was back to normal mouse cursor wise. Granted I only tried it briefly but seems to be fixed.

6.0 betta 3: wfm too. Thanks!

Using VB 6:

1) After upgrading VB to V6 beta, upgrading Windows to 1809, and before upgrading the extension pak, I still had the problem.
2) When I tried to install the V6 beta extension pak with VboxSVGA drivers and dual monitors, the system hung while updating the drivers and was unrecoverable. On forced reboot only a tiny sliver of the screen was visible and the mouse did not seem to work.
3) After restoring the system, switching to VBoxVGA driver and a single monitor, upgrading Windows to 1809, I was then able to install the V6 beta extension pak.
4) After switching to dual monitors and rebooting the the mouse pointer offset issue seemed to be resolved.
5) Switching to VBoxSVGA drivers with the extension pak installed again resulted in the problem of only a sliver of the screen being visible and the mouse not working.

...don,
Please avoid discussing beta issues in the general discussions area, there's a VirtualBox Beta / Release Candidate Feedback forum just for that purpose.

I was responding to your previous request: "Can you try with the 6.0.0beta? I think it's fixed there." I did not just want to say WFM, because it did not in all situations.

OK, fair enough, mea culpa...

Solved in 5.2.24, too