Latest rig manager no longer recognizes Kemper - Windows 7

Quote from Eltzejupp

If it is so, why do so many crashes pop up immediately after the release of the „ stable“ update? I had the problem with win 7 and my colleague with win 10, like others here.

Never had a problem before. There must be something missing.

nobody is talking about crashes here. it's a common phenomena that you get a support peak once you turn a beta into a release. that's because loads of people install the version who were reluctant to install a beta. on top, there is always a certain percentage of people who face an issue when updating. it's just a fact of life.

what doesn't help is mixing things up: you talk about a crash nobody else is talks about here. and you talk about windows 10 whereas the issue here is purely windows 7 related and only if the installation is not up to date. that's not helpful.

Quote from RockmanCentralBob

I didn't know I had to update MS in order to run the newest RM...... never had to before and there was nothing warning me that there was an issue needing an update.And if I don't update RM, it turns into a Nag-Ware app that won't stop telling me to update it.

All I was looking for was the "KB" code for the specific update needed to fix the problem....
I don't think that's too much to ask for, nor do I think it's appropriate for Kemper to say, "UPDATE EVERYTHING", or "I don't feel like researching which update will fix this"!
People are having problems with an update Kemper pushed out, so yeah, I think they should be a little more specific about how to solve the issue.

And yes, I AM a software engineer, but I don't write device drivers, which isn't required to know that MS updates can totally mess up your system.
All I know is whenever I do MS updates, my system is almost invariably FUBAR'd and sh*t breaks....and I'm not the only one.

https://www.computerworld.com/article/321642…-contained.html

MS also likes to add in extra crap that ends up changing your preferences and settings to what THEY want them to be.
Some companies (Cough! - Apple - Cough!) even go as far as to push out updates that cause you issues to force you to upgrade your device.
So if I HAVE to do an update, I would rather do as few as possible to get it to work.

If you don't want Rig Manager to nag you about updates, please open the Preferences window and switch off "Automatically check for software updates". If you still want to update Rig Manager while keeping an outdated operating system, you might want to try KB3004394, followed by KB3024777. But I haven't explicitly tried only installing those on a fresh W7 installation.

Quote from G String

nobody is talking about crashes here. it's a common phenomena that you get a support peak once you turn a beta into a release. that's because loads of people install the version who were reluctant to install a beta. on top, there is always a certain percentage of people who face an issue when updating. it's just a fact of life.
what doesn't help is mixing things up: you talk about a crash nobody else is talks about here. and you talk about windows 10 whereas the issue here is purely windows 7 related and only if the installation is not up to date. that's not helpful.

Crash was the wrong word ( that native speaker thing)....
What i meant is, is doesn’t work without testing different procedures

Quote from RockmanCentralBob

Windows 7 is, by definition, an outdated operating system, but still works fine for what I need it for.
Thanks for the KB articles... that's all I was looking for.

But to anyone else out there looking to try this, better take a second look at KB3004394 before installing it....looks like it was a fiasco when it came out and might make things worse for some systems.
Reminds me of someone who said that MS updates always seem to cause a bunch of things to break.......... oh yeah, that was me!!

https://www.google.com/search?q=KB300…chrome&ie=UTF-8

And, it looks like KB3024777 (which was released to uninstall KB3004394) has issues too....

https://news.softpedia.com/news/Microsoft…es-481172.shtmlhttps://news.softpedia.com/news/Microsoft…es-481172.shtml

Regardless, neither of these worked to solve the issue.
RM still won't see my Kemper, so I've had to downgrade it back to 2.1.26

Display More

2.1.26 was the solution for my colleagues win 10. The new update can be installed but the kpa is not visible. Back to 2.1.26 , kpa is visible. Fix?

Quote from Eltzejupp

2.1.26 was the solution for my colleagues win 10. The new update can be installed but the kpa is not visible. Back to 2.1.26 , kpa is visible. Fix?

Though the thread was about Windows 7, the same applies for Windows 10 (and all other Operating Systems for personal computers): You should not prevent updates/certificate updates.

To determine what exactly fails you might contact support and check the device manager ("WIN+X" -> Device Manager) and check the Profiler device. If it has an exclamation mark on it, open the device properties sheet and check the error message.

Of course I can't tell for sure that it is not a bug on our side, but I am pretty confident.

Or, you could update Windows 7 critical updates until they're current, and also enjoy the new Rig Manager, and all the subsequent new RM's, that will also require a CA update.

A lot of us here are in the IT industry, myself included. If you want to tell us what you think is going to break, by upgrading your Win7 version, maybe we can help you with this.

Otherwise, you're stuck at one version of RM that still works, and there won't be much sympathy.

If you want help from Kemper support, create a ticket. This is a user forum.

The Win7 critical updates solve the problem you are experiencing, but you'd rather go on this tirade instead.

I don't see this thread going anywhere.