[GH-ISSUE #822] Opening a remote shell from file manager on a secondary drive fails #551

New issue

Closed

opened 2026-02-27 15:50:51 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 15:50:51 +03:00

Owner

Originally created by @ghost on GitHub (Jun 6, 2020).
Original GitHub issue: https://github.com/quasar/Quasar/issues/822

If you go to a secondary drive on a client (D drive in my example) and you right click to open a remote shell, it will try to cd to the directory but it fails and leaves you still at the root of the C drive. This seems to be an issue on 1.3.0.0 as well as the newest release 1.4.0

Since I switched to 1.4.0 remote desktop frame rates are about half of what they used to be on previous version.

Originally created by @ghost on GitHub (Jun 6, 2020). Original GitHub issue: https://github.com/quasar/Quasar/issues/822 If you go to a secondary drive on a client (D drive in my example) and you right click to open a remote shell, it will try to cd to the directory but it fails and leaves you still at the root of the C drive. This seems to be an issue on 1.3.0.0 as well as the newest release 1.4.0 Since I switched to 1.4.0 remote desktop frame rates are about half of what they used to be on previous version. ![Screenshot_1](https://user-images.githubusercontent.com/46517869/83939857-1663aa80-a7ae-11ea-83d3-13c82aca4203.png)

kerem

2026-02-27 15:50:51 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 15:50:52 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 6, 2020):

Thanks for the report, I can confirm that opening a remote shell on a secondary drive from the file manager doesn't work. It should be changed by d: first and then cd D:\Documents. However I can't reproduce the worse frame rate in the latest version.

@MaxXor commented on GitHub (Jun 6, 2020): Thanks for the report, I can confirm that opening a remote shell on a secondary drive from the file manager doesn't work. It should be changed by `d:` first and then `cd D:\Documents`. However I can't reproduce the worse frame rate in the latest version.

kerem commented

2026-02-27 15:50:52 +03:00

Author

Owner

@ghost commented on GitHub (Jun 6, 2020):

Even if you do cd d: it still fails to switch drives

Could it be a video card or driver issue? I do not have a great video card

@ghost commented on GitHub (Jun 6, 2020): ![Screenshot_1](https://user-images.githubusercontent.com/46517869/83940482-63e21680-a7b2-11ea-9045-e6c907efcbf2.png) Even if you do cd d: it still fails to switch drives Could it be a video card or driver issue? I do not have a great video card

kerem commented

2026-02-27 15:50:52 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 6, 2020):

Only type d: without cd. Currently the remote desktop frame rate is capped by the Windows Forms renderer which is slow and runs on the CPU only. In the future Quasar will change the GUI interface to a more modern one that supports GPU-acceleration. This will allow 30+ FPS RDP sessions.

@MaxXor commented on GitHub (Jun 6, 2020): Only type `d:` without `cd`. Currently the remote desktop frame rate is capped by the Windows Forms renderer which is slow and runs on the CPU only. In the future Quasar will change the GUI interface to a more modern one that supports GPU-acceleration. This will allow 30+ FPS RDP sessions.

kerem commented

2026-02-27 15:50:52 +03:00

Author

Owner

@ghost commented on GitHub (Jun 6, 2020):

Gotcha! Hopefully that bug gets sorted in an update. I'm glad to see you still support this project. It is really fantastic

@ghost commented on GitHub (Jun 6, 2020): Gotcha! Hopefully that bug gets sorted in an update. I'm glad to see you still support this project. It is really fantastic

kerem commented

2026-02-27 15:50:52 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 6, 2020):

Thanks, yes after a long period of silence I'll continue with it now.

@MaxXor commented on GitHub (Jun 6, 2020): Thanks, yes after a long period of silence I'll continue with it now.