I've got the same issue here with my rack profiler.
It seems like a bug. I would write to support.
I've had the same but since OS14 and had to remain on OS13 per Kemper Support. Contacting Support may help, but I was told to remain on OS13.
"Our development team is currently looking into cases where customers are experiencing this issue. Unfortunately, Microsoft’s driver documentation is not sufficient for our development needs. Of course, we will continue to provide updates for the MKI profilers. Unfortunately, some customers are currently experiencing this issue. Please be patient and continue using OS13.0.5 for now."
I've tried latest OS and still get the same update message. Need to keep RM at rev3, too, for Windows and Kemper to "talk." I keep watching this forum to see if there is a solution. Seems like many users are staying at OS13 for now.
I’ve stayed on OS13 for my Mk1 racks and RM3. I’ve also turned off updates in RM so I’m not getting any notices to update.
"Our development team is currently looking into cases where customers are experiencing this issue. Unfortunately, Microsoft’s driver documentation is not sufficient for our development needs.
When all else fails, blame it on Microsoft. It's what I do.
"Our development team is currently looking into cases where customers are experiencing this issue. Unfortunately, Microsoft’s driver documentation is not sufficient for our development needs. Of course, we will continue to provide updates for the MKI profilers. Unfortunately, some customers are currently experiencing this issue. Please be patient and continue using OS13.0.5 for now."
Let me just add that the wording is a bit unfortunate. There are cases where Windows doesn't successfully remove components and what you see here is related to that. It's nothing we can control. Good news is that it is pretty rare.
I have sadly to say that I am having the same problem.
I Installed both, the newest (!) rig manager, and the newest (!) profiler software like Andy and I got the same message.
Right now I was trying do downgrade as mentioned and I just installed OS 13.0.5 on the Kemper. Beware that you also have to install the elder Rig Manager 3.10.13. as well. At the moment the rig manager is finding the Kemper again - though I dont had the time now to check if all works again. 
having the same problem, on mk2
I figured I try to update again. This is the sequence of events.
Attempted to Install Latest Software
OS 14.1.2.66277
RM 4.2.12 Windows 10 64
I have the same issue. Is it really that rare?
I've got 2x mk1's, someone in this thread has an mk2, and there are several threads about this issue. I have no idea how many Kemper users are being affected by this software gaff, but I think the afflicted is not a small number. I can see some miscues on a software rollout, but dragging out for five months is beyond defensible. This is a total breakdown of RM4 and OS14; the updates do not work for some users. I've contacted support multiple times and the final word was stay on OS13 and RM3. This is one of the more expensive pieces of equipment I own and I expect something other than "just leave it alone..." The only power I/we have is to keep complaining because KEMPER DOES NOT CARE!
Kemper proponents continue to state "contact support," but that is not working. Anyone deciding to invest in an expensive piece of hardware like a Kemper might look at this forum and walk way. Kemper needs to fix it ASAP. To the people that this has not affected, it could be you next update!
I have a Rack MK2, and everything works without any problems. Latest updates installed.
The conclusions/possibilities:
Kemper is trying but cannot technically fix the problem (Hard to believe this is the case after five months; if this is the case, Management needs to clean Kemper house or hire some new blood)
Kemper is not applying resources to fix the problem (does not care about the customers that have been with them for over a decade and allowed them to build their business)
Kemper does not have the resources to apply as niche hardware amp market is being negatively impacted by the software amp offerings.
Your Windows installation apparently does not fully remove these components using the available Microsoft removal mechanisms. I'm sorry that you're experiencing this issue, but unfortunately there's nothing we can do beyond using the removal mechanisms that Microsoft provides.
Our tool simply automates the official Microsoft processes for removing components. Its purpose is to make the process easier and more convenient by providing a single click solution instead of requiring you to use command-line tools.
To provide some additional context: the underlying issue is that your Windows installation is unable to remove older components. The reason you can't connect with OS14 is not because anything in OS14 is malfunctioning. Instead, the older components that could not be removed are still connecting to your Profiler, which prevents OS14 from establishing its connection.
Your Windows installation apparently does not fully remove these components using the available Microsoft removal mechanisms. I'm sorry that you're experiencing this issue, but unfortunately there's nothing we can do beyond using the removal mechanisms that Microsoft provides.
Our tool simply automates the official Microsoft processes for removing components. Its purpose is to make the process easier and more convenient by providing a single click solution instead of requiring you to use command-line tools.To provide some additional context: the underlying issue is that your Windows installation is unable to remove older components. The reason you can't connect with OS14 is not because anything in OS14 is malfunctioning. Instead, the older components that could not be removed are still connecting to your Profiler, which prevents OS14 from establishing its connection.
So are there tools we can use to fix it?
Maybe it can be a simple fix in Windows Registry? If the components are known then someone can right a batch file to remove those keys and values so a clean install can be made.
So are there tools we can use to fix it?
We have a tool that essentially handles what an experienced user could also perform manually using command line. Support sends it to you on request with some instructions. The tool works great but it has limits. The limit is reached when the MS command line apps the tools is using cannot solve it anymore.
Maybe it can be a simple fix in Windows Registry? If the components are known then someone can right a batch file to remove those keys and values so a clean install can be made.
Not a chance, if it would be that easy we wouldn't have this conversation. What MS does there is extremely complicated you can only rely on the tools they provide. On top, the documentation is pretty sparse.
