1 2 Previous Next 18 Replies Latest reply on Nov 26, 2016 9:32 PM by rhaskins Go to original post
      • 15. Re: Mouse problem on second display using WS 10 (regression?)
        schmosef Lurker

        Thanks AvalonWar, this has been driving me crazy!

        • 16. Re: Mouse problem on second display using WS 10 (regression?)
          DrKluge Lurker

          Workaround Solutions: Uninstall the Windows Updates listed below… they are causing the issue. Alternatively, change display settings as described below.

           

          I would describe the issue like this…

           

          Synopsis:

          Mouse click position jumps around making it difficult to navigate buttons, menus and most everything else.


          Configuration:

          Applies to VMware Workstation 10 and 11 on Windows 8.1 host.  Fails on Windows 7 and Windows 8.1 VM and probably others like XP and Ubuntu.


          Root cause:

          Several Windows 8.1 Updates create inability for VMware Workstation to query the scaling for secondary display, so it defaults to the scaling for primary display.  Reported mouse position is offset by the difference between the primary and secondary display’s scaling (around 80 to 100 pixels in X and Y direction).


          Troubleshooting: To navigate, click once, wait 1 second and click again without moving the mouse. The second click will work fine for selecting menus, etc. but you can’t do drag operations or double click anything. Do this over any screen element that doesn’t require a double click.  To see incorrect mouse position, single left click on desktop (not on an icon).  Now HOLD the left mouse button down without moving it. Must be in exact position of first click.  It will draw a “selected” rectangle on the desktop (it thinks you dragged the mouse). The opposite corner from the mouse represents how far off the x and y position are.


          Workaround 1:

          Don’t install the offending Windows 8.1 updates listed below.  Or uninstall them if your IT department allows it.  Don’t rely on Windows System Restore if issues… it will fail to restore.  Do a Ghost 15.0, Acronis or other full disk image backup.  Incremental might work too.


          Workaround 2:

          Change both displays to 100%.  To change, click Control Panel->Display->Change Display Settings->”Make text and other items larger or smaller”.  Then turn on “Let me choose one scaling level for all my display”.  Then keep or choose “Smaller – 100%” radio button.  If you can live with that tiny font on your 15” laptop screen, you don’t need to refrain from installing the above Windows updates.


          Offending updates:

          Update for Windows 8.1 for x64-based Systems: KB2967917, KB2975719, KB3000850, KB3042216

          Security Update for Windows 8.1 for x64-based Systems: KB2973201, KB2993651, KB3000061, KB3002885, KB3013455, KB3034344, KB3045171, KB3057839, KB3070102, KB3078601, KB3087039


          Note: there are earlier updates that also caused issue, but I  didn’t have those numbers handy.  Those older updates should be superseded if you have installed the latest Windows Updates offered as of 9/29/2015.  Any one of these updates creates the issue; it’s not a combination of these that is causing the issue.  I have been tracking these individually for over a year.  It’s probably one DLL file that is the issue… and that DLL file gets updated by many updates.

          !@

          Hope this helps!  I’ll submit this as a bug to VMware when I get a chance… but I don’t think they are doing anything wrong.  Perhaps they can contact Microsoft.

          • 17. Re: Mouse problem on second display using WS 10 (regression?)
            Dukekautington3rd Lurker

            The DPI scaling setting fixed it for me.  Thanks so much AvalonWar!  I was about to go insane.

            My set up is Windows 10 host with Workstation 10.07

             

            guest was Windows 7

             

            Regards

            • 18. Re: Mouse problem on second display using WS 10 (regression?)
              rhaskins Lurker

              Thanks AvalonWarAvalonWar! I never saw the problem with WS10 on Win8.1, but it recently started manifesting on Windows 10 (ugh!), and this fixed it!

              1 2 Previous Next