And the REVs of the OS and RM. Supposedly, there is a RM 4.1.14 to go with the Beta OS 14.1.0 on the Main Download Page. I see the OS but not the RM.
Set your RM Preferences to include Betas. Then check for updates.
And the REVs of the OS and RM. Supposedly, there is a RM 4.1.14 to go with the Beta OS 14.1.0 on the Main Download Page. I see the OS but not the RM.
Set your RM Preferences to include Betas. Then check for updates.
Thanks. I've always downloaded from kemper.com and not from inside RM. The performance laptop is not connect to www, but I'll see what I can do.
No go. Another wasted hour of my life... Here is what happened.
1 - Macrium Reflected Laptop to ensure reversion if another fiasco ensues
2 - RM was 13.10.13 and OS was 13.05.61295 (reverted successfully from 14 after previous problems).
3 - Allowed laptop to connect to WWW and kemper.com. Checked for Betas. Kemper.com requested to update both RM and OS. Allowed. Took a LONG LONG TIME. Maybe that watched pot never boils thingy??
4 - Kemper OS went to 14.1.0.65901B but RM stayed at 13.10.13. I have no idea why RM did not update. RM appears to be looking for Kemper and will not do anything else ("cannot find profiler"). Dropdown to check for updates is grayed out an not accessible. Can't find a way to update RM if RM will not allow a check.
5 - Loaded OS 13.05.61295 from USB in Kemper and laptop would connect again to Kemper.
6 - Just to make sure, the Laptop was reverted to earlier image.
I've had a Kemper since 2013 and never had this much of a cluster with an upgrade. Obviously, Kemper QA/QC is lacking.
Here is the link to download Rig Manager 4.0.61 for your Kemper OS
Thanks, but I have tried RM 4.0.61 along with the OS 14 stable and OS 14 beta. That upgrade is what started this last Friday. I think it's best if I wait until the dust settles from this disaster. The OS 14 and RM 4 were released on 3/30/26 and I waited almost a month. Typically, I wait until after initial release but that did not shield my system. I'll check this forum before I update again. Like I said, over the past ten years Kemper has lulled me into a false sense of security with their upgrades, but I damn sure learned my lesson this time!
Wrong window .,
I got excited and was beat down again by Kemper. Downloaded supposedly non-beta from website (RM 4.1.17 and OS 14.1.065901 - no "B" on end of this one).
1 - RM 4.1.17 downloads as 4.1.14 with a big red beta. This is not 4.1.17, guys... Somebody needs to fix the link. Those pesky details again... Just for kicks, I check the Mac and ARM links and those links download 4.1.17. Windows link is still 4.1.14.
2 - Upgraded OS to 14.1.065901 and appeared to work.
3 - Still get message to "update OS above 12.1..." This is with the RM 4.1.14 and OS 14.1.065901.
4 - Connected to WWW and was able to update to RM 4.1.17
5 - Same message to "update OS above 12.1..."
From my end, nothing has changed. I'll reload last nights disk image and revert to OS13. Not sure what's going on at Kemper, but they are not dotting i's an crossing t's.
UPDATE: Reverted laptop to disk image with RM 3.10 and set Kemper back to OS 13.05.06 and all is working as expected (other than delay, below). I have no idea why OS 14 and RM 4 will not talk to each other.
Another comment that I just verified. I have a backup rig that is the same laptop, software, hardware, mk1 Kemper, hub, dock, etc. that has not been monkeyed with during this Kemper debacle. That RM 3 and OS 13 start up instantaneously. The system that has been upgraded, downgraded, pushed sideways, etc. still takes 30-40 seconds to start. This delay started after the initial OS 14 and RM 4 and has not gone away. I hope when Kemper figures this out that startup delay goes away.
SteelWreath I had the same issue, it's because RM v14 after install reverts back to using older drivers for some reason. I received a fix from Kemper that deletes all the legacy drivers on the system, reboot and works perfectly fine now. I to was receiving that same message after my upgrade" Rig Manager complains that "Profiler requires an update. ....Please update profiler OS to version 12.1.."
Same issue here. Foolishly updated from 12.1 firmware to 14.1 and RM to 14.1.17 and now neither talk to another. Has anyone actually found a fix for this yet?
Same issue here. Just downloaded latest rig manager. After installation the app said "update OS above 12.1.." (was wondering why RM wasn't doing that by itself like in the years before?!). But ok, had to find an USB Stick, download the new OS, install it on the Kemper etc.
Rebooted both my PC and the Kemper multiple times, RM doesn't show the local library on the Kemper, instead after 15 seconds there is that yellow text ("Your PROFILER requieres and update yada yada....").
I understand often in software things break when implementing new stuff, but I'd really like a fix for that!
Seems like to me it's Windows Drivers Issue. When you install 14.0 it uninstalls the previous Device manager drivers. If Kemper made the drivers available for the profiler separately my guess is this would probably solve this issue. Plus whatever the 14 does to the drivers stop it from doing. I have tried all the fixes everyone suggested and no go. I'm going to write support and see what they say.
I just attempted to fix provided by Kemper Support and still no solution. The combination batch/powershell solution found ten old drivers and states the drivers are being removed. However, when the RM and Profiler are reconnected via USB the dreaded "Update OS...." popup still remains. The batch file window provides a list of the drivers that should be but are not removed, so I guess I'll do some research on removing unused drivers manually (USB Ghost or some other free programs comes to mind). But damn guys, I shouldn't have to learn assembly language to get the MFR running... We are musicians, not computer engineers (at least I'm not). This crap has been dragging out for over 30 days. Is Kemper trying to knock MicroSux out of bottom spot?
Since Kemper/Windows/Normal mode is not able to remove the 10 "old Kemper" drivers, I used a program called "Device Cleanup Tool" from
This shows LOTs of old drivers with a last used time; I had hundreds! My philosophy was if it hasn't been used in months, remove it (Drivers, Storage, Mice, BlueTooth, etc.). I ran this program (no installer, just run) and deleted what was not used. During this time, the Profiler was plugged in USB. I then ran the Kemper-provided Driver-Finder and there were still six drivers left. I then shutdown the Profiler and ran Device Cleanup Tool. It showed six drivers that were not connected in the last six seconds... Obviously, I now deleted those as those had to be Kemper-related. The Kemper-provided Driver-Finder then showed NO old Kemper Drivers. I thought, "Baby, we are getting hot now! All I've got to do is plug in the Profiler and Kemper will install the newest Drivers!!!" Not so fast...
I had no old drivers, ran 4.1.17 RM and 14.1.0.65901 OS. I even logged on to internet in case RM needed to find some NEW drivers! When I plugged the USB into the Laptop, the Profiler was setup and the SAME DAMN UPDATE >12.1 OS was displayed. When I ran the Kemper-provided Driver-Finder, there are now five old drivers...
This means that I wiped out the old drivers, proved I wiped out the old drivers, and then Kemper reloaded the old drivers. WTF?
UPDATE:
JFK I tried again. Cleared out all the non-connected USB devices and reconnected the Profiler then disconnected the Profiler to see what was disconnected in the last five minutes with "Device Cleanup Tool." There are eight USB devices loaded by the Profiler. Most are Microsoft drivers from 2006 and 2019. There are four "Profiler" devices that don't have much information. Nothing appears to be recent. As PrimalMax suggest, we are going to need updated drivers to possibly load/update manually because the old, non-compliant drivers are loading instead, even on a clean install.
This is what's installed on my device and evidently one or more of these will not play with the new RM.
Found 7 device(s):
Instance : USB\VID_133E&PID_0002&MI_04\D&275E6EB3&3&0004
Name : Profiler
Driver : wdma_usb.inf
[DryRun] Would run: pnputil /remove-device "USB\VID_133E&PID_0002&MI_04\D&275E6EB3&3&0004"
Instance : USB\VID_133E&PID_0002\KRDKUOJCU6K
Name : USB Composite Device
Driver : usb.inf
[DryRun] Would run: pnputil /remove-device "USB\VID_133E&PID_0002\KRDKUOJCU6K"
Instance : SWD\MMDEVAPI\MIDII_AE493180.P_0000
Name : Profiler [0]
Driver : c_swdevice.inf
[DryRun] Would run: pnputil /remove-device "SWD\MMDEVAPI\MIDII_AE493180.P_0000"
Instance : SWD\MMDEVAPI\MIDII_AE493180.P_0001
Name : Profiler [1]
Driver : c_swdevice.inf
[DryRun] Would run: pnputil /remove-device "SWD\MMDEVAPI\MIDII_AE493180.P_0001"
Instance : SWD\MMDEVAPI\{0.0.0.00000000}.{A0B9FF08-BB96-4343-A0DF-F82DBFA85999}
Name : Digital Audio Interface (Profiler USB Audio (Class Compliant))
Driver : audioendpoint.inf
[DryRun] Would run: pnputil /remove-device "SWD\MMDEVAPI\{0.0.0.00000000}.{A0B9FF08-BB96-4343-A0DF-F82DBFA85999}"
Instance : USB\VID_133E&PID_0002&MI_01\D&275E6EB3&3&0001
Name : Profiler USB Audio (Class Compliant)
Driver : usbaudio2.inf
[DryRun] Would run: pnputil /remove-device "USB\VID_133E&PID_0002&MI_01\D&275E6EB3&3&0001"
Instance : SWD\MMDEVAPI\{0.0.1.00000000}.{BC50C30A-33AE-463B-A45D-F929C681FB85}
Name : Digital Audio Interface (Profiler USB Audio (Class Compliant))
Driver : audioendpoint.inf
[DryRun] Would run: pnputil /remove-device "SWD\MMDEVAPI\{0.0.1.00000000}.{BC50C30A-33AE-463B-A45D-F929C681FB85}"
From OS14 on, there are no specific driver files needed anymore. Windows will do all driver installation by itself, just by connecting the Profiler via USB. This is the reason why all actual drivers listed in the device manager are from Microsoft.
The driver removal tool is primarily aimed at old driver entries that might be left over from previous installations.
My guess is that it is not the drivers that are the cause. Please continue to work with our support staff.
Yes, that makes sense. Kemper OS14 is not playing well with the available Microsoft USB audio and data drivers.
Chiming in to say I'm also having the same issue. Also on Windows. This was a USB stick firmware install and a fresh Rig Manager install because I got a new computer since the last time I connected my Kemper to it.
From OS14 on, there are no specific driver files needed anymore. Windows will do all driver installation by itself, just by connecting the Profiler via USB. This is the reason why all actual drivers listed in the device manager are from Microsoft.
The driver removal tool is primarily aimed at old driver entries that might be left over from previous installations.
My guess is that it is not the drivers that are the cause. Please continue to work with our support staff.
That error is exactly Kemper using older drivers. Received a fix to remove older drivers from support and it immediately worked.
That error is exactly Kemper using older drivers. Received a fix to remove older drivers from support and it immediately worked.
OS14 doesn't use a driver written by us anymore. The issues you're all seeing are related to Windows. Best thing you can do: Get in touch with support. We can send you a script to clean things up, usually it works but we've seen situations where even the script wasn't enough.
If you're getting the: "no profiler connected to system . . ." or "your profiler requires an update. The current software is too old for rig manager to connect. Please update your profiler OS to version 12.1 or higher."
This fix worked for me on Windows 11
1. Download and install current 14.1.1 Profiler OS via thumb drive.
2. Uninstall Rig Manager
3. Go to: https://thegeekpage.com/how-to-remove-…rom-windows-11/
Scroll down to: "How to safely remove old hidden device drivers" and follow the instructions."
4. In device manager under "Sound, Video and Game Controllers" right click and uninstall old legacy Profiler drivers as per instructions.
5. Download and install Rig Manager 3.10.13
6. Make sure Profiler is on and open Rig manager (3.10.13)
7. Follow the pop-up prompt to update Rig Manager
In my case, after update, it connected to the Profiler and started the file syncing process.
Hope this helps someone!
You should get in contact with support, they can provide a better help than the generic instructions on thegeekpage.