Mouse Integration Bug Windows 10 April 18 Host - Pointer In Wrong Location

[C0dif0rn1c4t10n]

I have a VirtualBox Host running Windows 10 April 2018 Update, with a Guest VM also running Windows 10 April 2018, both configured to use the same 2 screens @ 1920x1080, both scaled to 100%.

I am running VirtualBox 5.2.18 with Guest Additions 5.2.18

Since the Guest was updated to April 2018 I have been unable to get Mouse Integration to work properly.

In Mouse Integration mode the Mouse Cursor is visible in the Guest but is showing at the wrong location. If I click bottom left corner on the Windows Start menu it correctly locates the click point and shows the Start Menu. However, as I move the Mouse around the screens the location of the Click Point drifts to the right(i.e the actual Point on the virtual screen moves progressively farther away to the right as I move across the screen, whilst the Mouse Cursor tracks as normal).

This has only started happening since the Guest OS was updated to Windows April 2018.

If I turn Mouse Integration off the Mouse Cursor and click Point behave correctly, which is usable but not ideal.

[Socratis]

1. It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

2. You were supposed to follow these steps when you filed the bug, and provide a VBox.log:
   Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

3. This sounds awfully close to #18016, but in that case, it's the guest that is the problem, not the host. And the guest is not at the April 2018 update (actually it's Mar/2018, aka 1803), but in 1809. Can you double-check by running "wivner" on both the host and the guest?

I have the suspicion that your guest was updated to 1809 (the Sep/2018 update) without you realizing it, i.e. a background update. But, the log from step #2 will also tell us that. BTW, it's also suspicious that you just noticed this, as soon as 1809 came out...

[C0dif0rn1c4t10n]

VBox Log

[C0dif0rn1c4t10n]

Winver Host: 1803 (build 17134.320) Winver Guest: 1809 (build 17763.1)

Attached log file.

[C0dif0rn1c4t10n]

This is probably a duplicate of: https://www.virtualbox.org/ticket/18016