More woes continue for fresh Windows 8.1 users – now, it seems that some Logitech users are reporting issues with the Logitech Gaming Software in Windows 8.1
We took a break from reporting Windows 8.1 issues and problems, but we’re back at it again. According to recent forum post on Logitech’s support forums, at least one user is reporting problems in Windows 8.1 with the Logitech Gaming Software. Here’s what he said:
I recently upgraded from Windows 7 Ultimate x64 SP1 to Windows 8.1 Pro x64. This was a clean install. Everything i installed thus far is working without any problems (this includes all my other devices). I own a lot of Logitech products but for this PC (my main PC) i use a Logitech G710+ keyboard and Logitech G400 mouse. Both of them make use of the Logitech Gaming software as a driver and profile manager etc. No matter what i have tried, the Logitech Gaming software will not install correctly, and after some trying… even if it does eventually install the application will crash repeatedly and randomly all over the place. Usually the setup just crashes and freezes the entire PC during step 4 of 5 upon installation. The freeze is so severe that the only resort you have is a hard reboot of the PC.
After the posting was made on the forums, more users have confirmed getting the same issue in Windows 8.1. Some users suggest uninstalling Logitech Gaming Software, and deleting the settings.json file, then reinstall LGS. The settings.json file should normally be located here: C:\Users\<username>\AppData\Local\Logitech\Logitech Gaming Software.
For most users experience this issue, even when making a clean install, it seems to stuck at ‘Step 4 of 5’. Also, running the Logitech Gaming Software installer under the Windows 8.1 compatibility mode seems to have solved the issue only for a few users. If you’re having the same issue, let us know in the comments box and we’ll try to search for a fix together.
Update – a big thank you to all of our readers who left comments with possible solutions, so just head below and have a look, just in case you might find a working fix for you.