OpenGL stops working when RDP disconnects

[KeinNiemand]

An application that runs on a headless VM needs OpenGL to run. Installing Mesa using the system-wide deployment got the application to work, however it stops working as soon as I disconnect the RDP session.

[RobPasMue]

Experiencing similar issues on my end...

Had an Azure VM, windows based, to which I connect using RDP. After installing Mesa3D from the releases in this repository, RDP stopped working. Had to revert to my old opengl32.dll and run sfc /scannow to remove all corrupted files... this allowed me to re-enable RDP.

How can we get this Mesa3D distribution to work with Windows RDP?

[pal1000]

You probably need to register Mesa3D OpenGL ICD to Microsoft Remote Display Adapter. Unfortunately I don't know the howto or even if it's doable in the first place.

[KeinNiemand]

Experiencing similar issues on my end...

Had an Azure VM, windows based, to which I connect using RDP. After installing Mesa3D from the releases in this repository, RDP stopped working. Had to revert to my old opengl32.dll and run sfc /scannow to remove all corrupted files... this allowed me to re-enable RDP.

How can we get this Mesa3D distribution to work with Windows RDP?

This sounds like a diffrent issue, RDP is still working for me, my problem is that OpgenGL stops working as soon as the RDP session goes inactive (when it's disconnected or minimized).
The workaround that worked for my problem is to move my application to the console session with this command
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (tscon.exe %%s /dest:console)