Mice and Pointing Devices

[samhandwich]

Hi folks. I have an Anywhere Mouse MX, a laptop with Windows 7 x64 Ultimate, latest Setpoint. My mouse works fine until I put my computer to sleep. Then, when I wake it up, the scroll wheel behaves oddly; I have to scroll 3 or 4 clicks to get the page to move down one chunk in a webrowser. To scroll to the next page in a pdf document takes 7 clicks.

As far as I can tell, only a restart will fix the problem...until I put the computer to sleep again. I've tried reinstalling Setpoint, but no change. I've searched a lot, but haven't found solutions.

I have a Synaptics touchpad on the laptop so I'm not sure sure if that has anything to do with it, altough before I upgraded from XP Pro to Win 7 there was no problem running both.

Any help would be greatly appreciated.

[fillup]

I have the exact same problem!  Also running Windows 7 64 bit and Logitech Anywhere Mouse MX.  After waking from sleep, the mouse scrolls VERY SLOWLY.  Only a reboot will fix the problem.

[a10webb]

I can replicate this problem too. Win7 x64 Pro on an HP Pavilion dm1z. This doesn't appear to be specific to this mouse though. I have an MX1100 on my desktop and set it to sleep yesterday and the same thing happened. Instead of scrolling 3 lines, it's like it must go 3 revolutions to scroll 1 line. Desktop is Win7 x64 Ultimate, AMD 1090T @3.2, 2x4GB DDR3 GSkill Ripjaws 9-9-9-24 @1333, Biostar TA890FXE.

[alupsa]

Same problem with Win 7x64 and Logitech M705 mouse. Unplugging and plugging back receiver resolves problem with scrolling.

[vango44]

Same problem with Win7 64 and M705 mouse.

I can fix by opening the Setpoint software and disabling/re-enabling smooth scrolling but this is annoying.

Please Fix!!!

[kpeppard]

Hello samhandwich:

I am sorry to hear your Anywhere Mouse MX, when put to sleep, acts erratic when it wakes up.

You mentioned earlier that you have installled the latest version of setpoint. What I would suggest is uninstalling setpoint from your Programs and Features and then rolling back to a previous version of setpoint(see below) such as setpoint version 6.00 or 4.80.

ftp://ftp.logitech.com/pub/techsupport/mouse/

Regards,

Kevin

[drno31]

I'm able to recreate this with the Performance Mouse MX. After waking from sleep, the scroll wheel is very, very sluggish. Following the suggestion of another user in this post, I removed and replaced the receiver and the scroll behavior returned to normal, but this is not ideal as I don't want to move and reach behind my desktop everytime I wake from sleep. Can anyone confirm that rolling back to an earlier version of SetPoint software corrects this issue, or is Logitech planning on issuing a fix in the next version of SetPoint. Thanks!

[kpeppard]

Hello drno31:

Thank you for posting your issue to the Logitech Community Forums.

In a situation like this please do the following:

1)Start->Control Panel->Device Manager

2)go to Mice and Other pointing devices

3)uninstall, by right clicking on the Logitech Compliant mouse and selecting uninstall

4)remove receiver

5)power cycle your computer

6)when computer comes back up to normal operation then plug in computer

After the above steps have been completed then try your mouse. You may need another mouse if you have to put in a password to get in to your system.

Hope this helps

Regards

[BW42]

I'm using an MX Revolution and am having the same problem. Your suggestion didn't work for me. A generic, corded mouse works without problems. Using Hibernate, or restarting the computer fixes it... until I use Sleep again.

My OS is Widows 7 Ultimate 64 bit, with latest updates installed. SetPoint version is 6.20.50. Driver is 5.20.51.

[BW42]

Updating my previous post:

Setpoint reports the driver as 5.20.51, but Windows reports it as 5.20.12.0

I rolled back the mouse driver to the one supplied by Microsoft (6.1.7600.16385) and the problem disappeared. However, only the left-click, right-click, forward, back buttons, the normal and freewheeling scroll are functional. That's good enough for me right now.

I'd say that the Logitech driver is the problem.