Latest Revision sends user to version 2.1.0 which doesn't work (Easy Fix)

What exactly (significant bugs?) is causing Scopy 2.1 to not work for your students? I have 2.1.0-32ea83d46 (FW ver 0.33) installed on my Dell Windows 11 desktop computer and it seems to work properly. Have you reported these issues to the Analog Devices Scopy pages on GitHub so the developers can look into any issues you are seeing?

I'm not one of the developers just an occasional user. 

Well that is interesting.     I also have a Dell Laptop running Windows 11.    When running Ver 2.1.0 -r2, which is what you get from "Get Latest Release", the M2k Icon has a red "x" in the lower corner.    When you connect to the device is spends quite a bit of time in the calibration process and crashes.

I have two students that accidently found there way to V2.1 and they both had the same experience.     One was on a MAC and the other on a Windows 11 box.

The official Scopy Download Site is hosting V1.5.0 R1 which is what my class has been using for the last two terms without problem.    As AD is not hosting V2.1 on the official download site I figure they are aware of the bugs in V2.1.     At least that is a rational reason for continuing to present V1.5 on the official site.

I have not reported the problem on GitHub, but will do so.

Thanks Ed

That is indeed strange. As you can see in this screen shot I have Scopy 2.1.0 -rc2 calibrated and up and running. Which is the second one (Aug 21, 2025) on the GitHub releases page: https://github.com/analogdevicesinc/scopy/releases Maybe there is indeed something wrong with the Sep 16, 2025 release.

I've connected via IP vs USB here because I primarily develop Python programs at run in parallel with Scopy.