Yep unbelievable is right , how can this not happen in testing to their Software Developers ?
is the fix still to install Visual C++ 2015 and delete msvcp110.dll from the SetPointP folder to get it working ?
That hasn't helped me this time as it did in Janurary....
Logitech Setpoint Runtime Error Fix - Windows 10 Forums
Yes, I still use that one, but I had to reinstall VisualC++ afterwards, it did not work the first time.
Latest VC++ Pack: https://pastebin.com/raw/46rfrtBv
Last edited by TairikuOkami; 25 Apr 2019 at 15:39.
True, I missed that one. Setpoint if from 2015, they just updated GDPR policy in the last version. I just install all versions. From Technet forum: "msvcp110.dll is included in the redistributable for Visual Studio 2012."
I wonder, if it is caused by specific hardware, maybe with combination with Radeon, since some people mention it. I have not seen many people with issue either. I guess, it applies to outdated hardware, through they still sell it, like M705 or K360. Sadly Logitech does not care, since it applies only to a handful of people.
This one is from May 2018: Forums / This is the original, last post from December 2017: Forums
Yes it could very well be hardware specific, I have SetPoint installed on 3 different computers, 2 are custom built by me, and are fairly new. 3rd PC is around 8 or 9 years old, and still SetPoint runs fine on all 3. This is for the K350 and K800 keyboards.
The K350 has been around since 2009 thou. its quite old, even thou I just bought 2 of these recently.
The Computer I tried last night only had VC++ 2008 on it when I checked as Setpoint Errored out immediately on install , so I installed VC++ 2013 thinking that was the one I needed , which didnt help , so I checked my previous Post and found it was VC++ 2015 I need and I also needed to delete the msvcp.dll in the SetPointP Folder as well but to my surprise after several reboots it has not helped , I guess I'll have to try again.
I am only using older Logitech Mice / Trackballs like the Marble Mouse and TRB22 , so this isn't keyboard related for me at least.
KB.
For what it's worth: I own MX5500 desktop set (keyboard and mice) since early 2009 and never experienced this problem.
Quote
