This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
I'm using Win 7 (32 bit) with the MS arc Touch mouse software and drivers installed. Running on HP TX2 Touchsmart Tablet.
I'm facing a problem with my mouse with regards to the scroll function.
After "switching on" the mouse, there is a green led light and everything seems to work. The green LED then disappears, presumably to save battery.
However, after a short period of time, the scroll function will not work at all. There is no scroll "feedback" felt from the scroll strip either. But when I flatten the mouse and turn it back on again, everything works as per normal.
But after some time, the same problem resurfaces. Then, I have to turn the mouse off and back on again. Sometimes, the scroll function "turns" itself back on automatically. But most of the time, it just stops working altogether.
This is very irritating. It seems nobody else have encountered this issue.
Please help!!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Then again, another proof of the problem being on the software side - I have my mouse fully functional after the last Windows 10 update, launching the Arc Touch Bluetooth Mouse app and restoring default mouse settings.
Microsoft silently fixed it, though they should've kept us out of the dark ;) Nevertheless, I'm glad the mouse works as it was, no issues so far.
I hope you're right, but I don't think so. I have Win 10 and all the latest Updates here on my Surface Pro 3 and I'm still getting all the same mouse issues. Have also fully re-installed the Bluetooth drivers and Arc Mouse software too..
It is now July 2015, 4 years after this was first reported and the issue remains. I have found that a reboot is the only way I can restore scrolling.
I choose to travel small and light so I have had to accept the fact that this mouse is flawed and I will continue to use it until I can find another that travels so small.
Hi Sam,
Strangely, my mouse has been working successfully for the past week! Scrolling and haptic feedback have been working consistently. I haven't needed to close and open the mouse to restore scrolling, unlike in the past.
Before anyone gets too excited, it's possible that this is just a fluke. If, after a month of use, I continue not to have any problems, I'll feel more confident that something positive happened. Right now, I have no explanation for this surprising good news.
I upgraded to Windows 10 yesterday, 29 Jul 2015. However, the mouse seemed to work well for several days before then. It's possible that Microsoft may have released a firmware update that fixed a problem with either the mouse driver, or Bluetooth connectivity. It's also possible that I've gotten exceptionally lucky, and that scrolling will resume intermittently failing once again. I just don't know yet.
I have two Arc Mouse Surface Edition mice. After another couple of weeks of using my current one, I'll switch to the other one, to see what happens. This is going to be very interesting.
If others have noticed that their Arc Mouse Surface Edition mice are working since upgrading to Windows 10, please post and let us know the good news. That would help us to better understand if this was a software problem, after all, as opposed to a hardware defect with the mouse design or manufacturing.
I'll follow up in August with another post.
Thanks,
Steve
I had problems with my Arc mouse on a Surface Pro 3 where the scroll stopped working. I ran the Arc Mouse software and clicked on Restore Settings.... all working fine now. Looks like it is a software problem.
