11-25-2011 07:16 PM
The problem: I open my Device Settings for G9x, G500, and G700 Gaming Mice but the program says "SetPoint did not detect any supported devices..."
I have tried numerous methods that were suggested on the forums such as going into device manager and switching my drivers, re-installing Setpoint, diabling startup on Setpoint, and trying to open Setpoint II but it wont open.
Solved! Go to Solution.
01-09-2012 02:17 AM
I (& many others), have/had the same problem.
I'm afraid Logitech Support wasn't much help, but this is what I did to resolve my issue.
Disable any reference to Setpoint starting up with Windows via MSConfig. Find the DeviceSettings.exe file (C:\Program Files\Logitech\SetPointG on my Win7x64 system). Rightclick on the file & select 'Properties' > 'Compatibility' Tab & check the box 'Run this program as an administrator'. Click 'OK'
Now when I start my PC & want to play BF3 or MW3, I click a shortcut to this file on my taskbar & it recognises my G700 & all the allocated mouse configurations EVERYTIME
You could probably have MSConfig start the DeviceSettings for you & work, but if it aint broke, don't fix it I say
Hope this helps some other frustrated players as I was out there......Happy Fraggin'
02-19-2012 03:42 PM
Suicidal - don't do it; life is too short as it is, particularly if you have to waste most of it mucking about with SetPoint...
Many thanks - this actually is the resolution to this problem - after trawling through reams of uninstall, reinstall, sacrifice chickens, and all sorts of other disappointing nonsense, I finally came across this.
LOGITECH - PLEASE NOTE - You have a genuine problem here, and Suicidal's solution should point you quickly to the root cause - To summarise:
Prevent Setpoint from executing at boot/logon (using msconfig, autoruns or whatever to prevent it starting)
Then, once logged on, run as Administrator "C:\Program Files\Logitech\SetPointG\DeviceSettings.exe" and bingo, setpoint fires up and recognises the G700.
Don't do that and a significant proportion of people's setpoint installs repeatedly fail to recognise the G700.
Please take this opportunity to review the issue in the light of this workaround, and fix this extremely frustrating problem once and for all.
In the interim all ye who want to put this to bed and get to actually do something with the G700 - Listen to the words of SuicidalPig, he speaks the truth.
04-14-2012 07:29 AM
You are personally my HERO. I got the G700 as my last shot with Logitech products. I previously got the G930 headset that was having issues with the driver software as well. It wouldn't play the Dolby 7.1 surround, show the battery status, give any warnings, and the buttons didn't work. I reached out to Logitech for support, and after a few failed solutions, my situation was "escalated" to management. I never heard so much as a status update from them (escalation happened on 11/19/2011).
I was angry about that but figured it was a one time thing. I go the G700 because I wanted the wired/wireless option and I had the same issue that everyone was having. I knew Logitech couldn't care less and was about to return the mouse when I decided to give it one more shot searching for solutions. I tried yours and it fixed BOTH the G930 and the G700. Now I not only get to enjoy the mouse, but I also get the enjoy the headset too.
They should send you something because you will no doubtfully save a lot of people from frustration, and you essentially solves a major issue that Logitech couldn't be bothered with. YOU ACTUALLY SAVED THEM MONEY, because a lot of customers like myself who would have returned Logitech products with this issue will now be able to use and keep them.
So Logitech, if you are reading this:
1. Send SuicidalPig some serious swag; heck, you should offer a job for what was done.
2. FIX THE ISSUE now that you have some idea of what is causing it.
07-04-2012 11:49 PM
THANK YOU I thought I had a hundred dollar paperweight!
You must cleanboot, making sure not to start any logitech or setpoint processes at startup, and then run DeviceSettings.exe as administrator .
I've spent so much time trying to get my mouse to detect. Thanks again!
07-04-2012 11:59 PM
OK, i had better luck after killing setpointII.exe and then doing the update driver method through device drivers, then running devicesettings.exe.
Only problem is it doesnt save the button configuration i setup. I dont think i disabled setpoint from running on startup though, will have to try it again.
All in all, this is completely retarded for what we paid for this mouse.
09-16-2012 06:32 AM - edited 09-16-2012 06:34 AM
Pleased I could help you out & it's working for you na51hog
mrsone911 - shucks Pleased it worked for you as well. I haven't heard anything from Logitech by the way No free offers, no job offers.....not even a thank you
gnatecage & Aevar, great stuff that it's now working for you.
I've got that warm fuzzy feeling being able to help some frustrated users
Hope to catch you all in a game one day for a frag