Not working here. Disabled SIP and no luck. Made a script as mentioned by someone and has it launch as an agent and daemon and no luck. With it running under daemon I couldn't click around, unplugged it and plugged back in and same thing. If I go into the MS PreferencePane then it works. Exit out and stop working. Ugg.....my favorite mouse for years! Even have a backup incase it fails!....lol
El Capitan and Microsoft Mouse (IntelliPoint) Not Working
After installing the El Capitan GM, the forward/back buttons (side buttons, 4 & 5) on my Microsoft Wireless Mouse 5000 are only registering as left mouse buttons. The most recent driver, Microsoft Mouse 8.2 is installed and shows up in the System Preferences, but appears to not be functioning. MicrosoftMouseHelper is in the login items. Suggestions?
[Moved from Community Participation Center]
There is not an appropriate category to post this question to!
Windows for home | Other | Devices and drivers
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.
56 answers
Sort by: Newest
-
Anonymous
2016-06-22T21:19:22+00:00 -
Anonymous
2016-05-24T13:34:49+00:00 Is someone from Microsoft even reading this?
-
Anonymous
2016-05-19T00:31:14+00:00 No dice on the script. All paths ok. Crontab ok. Made the script in vi. Triple checked everything. No go. The mouse is working with Apple's own drivers, but not the Intellipoint drivers (tracking, speed, button assignments all not working).
-
Anonymous
2016-01-27T23:08:04+00:00 I tried this, with no success. I'm wondering if there is something else missing here.
-
Anonymous
2016-01-15T17:04:16+00:00 Hi!
This fix actually caused major issues external USB volumes FYI mainly with FCP7
in a OS X El Captain non admin user Final Cut Pro 7 editing environment..
Errors reported from within FCP that it could no read or write to the USB Volume containing the Cashe / Render and files needed for editing any given protect.
Every Possible permissions modification was implemented and it wasn't until the csrutil was put back to "disabled status" that FCP 7 was able to access the External USB RAID enclosure...
I think MS is trying to say it's time to buy a new mouse.