Fix Premiere Pro NOT to crash when used remotely via RDP (Remote Desktop)
Adobe, please, it's 2020 and Premiere Pro still crashes when I log in to my work PC via Remote Desktop. Please fix these issues once and for all and don't tell us it's only supported as a "local" application. RDP is exactly accessing a "local" PC, I am forced working remotely in these times.
Vincent Gustin commented
With RGS from HP, working on remote location works correctly... and, on local network, I'm also using a VNC connection to work remotly without problem.
Quadro OpenGL plugins and drivers are made for proprietary Nvidia virtual desktop applications.
This is when you have Server with many Tesla graphic adapters and virtual environment. And you have all engineers log in from remote location with desktop stations equipped with Quadro cards. Then you have full hardware acceleration in virtual environment. Something like this:
But this have nothing to do with your desktop computer, RDP and adobe apps.......
RDP based on Microsoft only solution will never do the job. And seems Microsoft are interested to change it exactly as adobe are interested to monitor this threads and answer .......
So you really need good desktop application which will duplicate your screen buffer like VNC. VNC will do the job but it is not secure. So if you are not capable of setting secure VNC by yourself just get service that will provide it to you painless.
We have 100s of different services providing exactly this.
For example you can read below:
Just pick one and work, forget about fix from adobe or microsoft for RDP...........
Remco Consten commented
Ah yes!, that simular to the way I had to work with Nuke as well. Had to Login with chrome remote/teamviewer etc. , launch the program and project files as usual, disconnect, login with RDP and start working with it.
And repeat with every other project script..
I'm really glad that Nvidia tool fixed this for me though. To bad it doesn't seem to work by default on your Quadro. Would have hoped it did.
John Riker commented
Guess as I'm on a Quadro it won't probably work for me. I found a forum entry where someone said for them it helped to start Premiere thru remote desktop, then force the app to pause, then disconnect, allow it to load and then log back in. This way it properly loads the video drivers. I am currently trying RealVNC but not sure i that will help.
The suggested batch file where you disconnect after launching it and connect in again a minute later:
echo Launching Premiere
"D:\Program Files\Adobe\Adobe Premiere Pro CC 2019\Adobe Premiere Pro.exe"
Remco Consten commented
Not sure if this works or is related to premiere problems at all but hopefully it could be a solution to some issues.
A couple of weeks ago Nvidia released a new tool that makes OpenGL GPU acceleration possible within a Windows Remote session. (previously only for quadro cards)
This means that it should now be possible to run software more reliable that where having opengl graphical issues, wouldn't boot, or work at all.
As a compositor I used this to fix countless bugs with Nuke and RDP.
Of course a Nvidia graphics card is required.
Just so you know, I haven't tried this with premiere and don't know what effect it will have..
You can download it on the official Nvidia development website:
As a alternative to RDP and earlier mentioned VNC, I found Parsec to be really impressive. Only downside is that it doesn't support multiple screens at the moment.
Steven Yarbrough commented
So is this something that can't be fixed? I was blaming NeatVideo and installing a mass variety of versions of Premiere and Media Encoder. Only to find it may be a video switching issue. I know I can remote in and like start an encoding session and it works but if I drop and connect later or go to the physical screen on the actual PC it's locked. But it's still encoding, just not responding and when the encode is done for me the app is still hung, just the utilization goes down. See my fully comment here:
There are a lot of problems with RDP and graphic applications. And main reason for this is located in RDP server and protocol. And this is the way RDP is made and working on the first place for remote system administration! Not for remote use of applications. And this is Microsoft fault.....
What is the problem actually, RDP create a different graphic console with different monitor device which does not have all direct 3D and OpenGL functionality available!!! There is no way for some applications to work, and this are not only adobe products.
If you need trouble free remote work you need to consider different remote access application.
For free you can use some of the VNC applications.
Or you can get something like subscription based team viewer, logmein, anydesk and so on.
This 3rd party software duplicate your physical console and make possible your application to work like usual. And sometimes you need to have your monitor left powered on.
This is problem is not possible to be fixed from adobe side with one simple fix.
Possible solution could be if adobe is amble to migrate all they apps to their cloud and enable use of all your local resources. But this need to be based on proprietary protocols and services not on RDP.
Emmanuel Mebasser commented
We all need the feature fixed and it had been ignored for too long. The problem has to do with sound. If sound is disabled on remote desktop, no more crashes. Please fix ASAP.