Hello!
I recently reinstalled/repaired Visual Studio, rebooted, and now the SenselApp doesn’t recognize the Morph.
Running Win11.
Tried to reinstall SenselApp and manually install firmware, still nothing.
Doesn’t seem to be found in Device Manager either: dm hosted at ImgBB — ImgBB
Would be VERY thankful if someone could help me out 
Thank u!
I use Morphs on a number of different Win 11 systems , and haven’t found any incompatibility. What specific version of Win11, and what specific version of Visual Studio are you running?
…Tim…
Hello Tim, thanks for your answer!
Visual Studio 17.12.4 / Windows 11, Version 22H2 (Build 22621.3007)
I recently tried to install SenselApp on a new computer (Windows 11, version 23H2 Build 22631.4317) and plug it in, then it recognizes!
Any clues…?
Cool, you’ve got it recognized on another computer, so you now know for sure that both the Morph and the cable work.
Now that you have a working environment (after a clean boot, I assume), you could install Visual Studio on the new computer (be sure to reboot again) to see if that installation alone triggered the issue, possibly due to PATH or DLL changes. If installing Visual Studio does trigger it, immediately uninstall Visual Studio to hopefully get back to a working system. I’ll be surprised if merely installing Visual Studio causes the issue, but it’ll be really interesting if it does.
On the old computer:
Tried to reinstall SenselApp and manually install firmware, still nothing.
You now know the firmware’s good, since it works on the new computer. Did you uninstall the SenselApp before installing it again?
If there’s nothing important on the old computer, the simplest approach to fixing the old computer would be to reinstall Windows on it to get a fresh start (like on the new computer). If you can’t or don’t want to reinstall Windows, just start comparing the two systems to remove differences (in PATH values, etc).
…Tim…
Hello again Tim, thank you for your answer!
I do not have Visual Studio on the other computer and could try to install it.
On the old computer I did uninstall and reinstall the SenselApp (twice), however my VS Sensel project also doesn’t find the sensel anymore.
You mentioned PATH and DLL, is that something I can check manually and fix before trying to reinstalling Windows?
Cheers!
DLLs are found by using PATH, so it’s really just the PATH you could check. If you bring up a cmd.exe window, you can type “echo %PATH%” to see the (often very long) PATH value. You can see and edit the path with a GUI in Windows as well - search for “Edit system variables”. It’s also possible a .dll file or a USB driver got hosed - using the Windows Device Manager you can see individual drivers - I had a (rare) audio program on a dell laptop that was only fixed by actually deleting the driver (using the device manager) and letting it install again (automatically).
,Tim…
SOLVED!
The Sensel was under COM & LPT in Device Manager, I uninstalled the driver, rebooted, plugged it back in and now it works.
For anyone who might have the same problem.
Thank you Tim for your willingness to help, VERY appreachiated!
Cheers mate!
Nice, thanks for the update! …Tim…
Hi,
A few days ago, I purchased two Sensel Morph devices on eBay. After speaking with the seller, I found out that these two Morphs have never been used and are running Firmware version 0.7.79. When I connected them to my computer, SenselApp displayed a message saying that it couldn’t connect to the server that provides the final firmware version.
In your post, I read that you manually installed the firmware. Could you please explain how to do it and where I can download the latest firmware version?
I would really appreciate your help.
Looking forward to your response.
Best regards,
Thomas
Hi, I am in a similar situation. I have owned a Morph for years but never needed to upgrade firmware until I got a new computer. Now I can’t load overlays. If you were able to upgrade the firmware, I would sure appreciate knowing how you did it! The Sensel website is just gonzo at the moment. I can’t tell from online resources whether they are defunct or now owned by Lenovo or some other company.
