I updated the version, the connection problem disappeared, and 2 new ones appeared.
How can I take a screenshot in the program to show?
And then he writes to me that it is impossible to make them in this window.
1 problem:
The server I'm connecting to has Classic Shell 4.3.1 installed.
http://www.classicshell.net/downloads/
When you click on start, nothing happens, this problem has not been observed before.
Now I have closed the program and tried to open the original Start, even it does not work.
Hi,
To take screenshots, please disable the Protect data from screen capture option. You can find this setting under General > Security and Privacy in the application.
We also identified a general issue with the Open session functionality. A fix has been submitted and should be available as soon as it’s approved by the Google Play Store (expected by tomorrow or Saturday).
Once the update is available, please let us know if the issue is resolved. If it persists, we’ll continue investigating.
Best Regards,
Nicolas Dufour
I checked everything, the first problem that I mentioned above has not been fixed.
The second problem in the video: https://0x0.st/K9I2.mp4
For some reason, part of the screen is not used when connecting.
Hi, we will try to set up an environment to reproduce the issue with Classic Shell. Regarding the second problem, we attempted to reproduce it but were unsuccessful. Could you please provide your application version number and OS version, along with any other details (special setup or other ...) you think might help us reproduce the issue?
Best Regards,
Nicolas Dufour
Remote Desktop Manager 2025.3.1.7
HyperOS 2.0.205.0
I have disabled all other application settings, but this does not solve the problem.
It's probably worth considering HyperOS as an assumption.
Hi,
Thank you for the update. We have not been able to reproduce the issue on our devices, and unfortunately, we do not have a Xiaomi device available for testing. As a result, it's unlikely that we will be able to address this issue, given that we cannot replicate it on our end.
As for the first problem, we are currently waiting for our IT team to set up an environment with Classic Shell.
Best Regards,
Nicolas Dufour
Maybe then you can tell me what needs to be done to collect the logs and see this problem?
Hi,
We don't think the logs will help us identify the issue, as it's most likely related to a rendering problem or an overlay caused by the OS. Still, it's worth a try.
First, go to the application settings, then to Sessions, RDP, and at the very bottom of the screen, make sure Enable Logging is turned on.
Next, reproduce the issue by opening your RDP session. Move the minimalist toolbar around, then close the session.
After that, open the main application menu, select Help and Support, then Submit a Support Ticket. Fill in the required information and at the very bottom of the screen, check Include all logs. Finally, click OK to submit the support ticket along with the logs.
Best Regards,
Nicolas Dufour
Hi,
Regarding problem #1, what is the operating system and version of the server where you installed Classic Shell?
Best Regards,
Nicolas Dufour
Windows Server 2012 R2
I sent the ticket for the second problem!
Hi,
Regarding the first issue, we have installed Classic Shell and conducted several tests. Everything is working as expected, and we were unable to reproduce the problem.
We also reviewed the logs you provided and found them to be normal. There was nothing unusual or concerning in the entries.
Have you tried connecting to a different server that does not have Classic Shell installed to see if the issue persists?
Best Regards,
Nicolas Dufour