ValveSoftware / ValveSoftware/Proton
Unable to run anything with a window with proton. NtUserEnumDisplaySettings Invalid device name L"" nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
I just get warn:system:NtUserEnumDisplaySettings Invalid device name L"". and 00c4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00c4:err:winediag:nodrv_CreateWindow The explorer process failed to start.
It works if I use something like Xephyr to create a nested X display, but that has it's own issues with 3d acceleration and stuff...
Note, I have a quite complex and potentially unsupported setup, HOWEVER it used to work and now it does not.
Let me know what logs you might want. To start, the entire desktop is virtual (Xvfb), but has acceleration (vkcube, glxgears, and steamvr all work). Wine works, but proton does not. Not even GE-Proton works. Note, cmd works, because it does not open a window.
Visually, when you launch a game that uses proton, the button says stop for a bit but soon switches back to play.
On a somewhat unrelated side note, VRChat's EasyAntiCheat keeps giving me error code #1 and I don't know what to do about that. But that can be saved for some other time or thread.
Any help is greatly appreciated! (e.g. quick fixes, workarounds; I'll take anything!!)
Also if this needed to be on the main proton repo, let me know, but I suspect the issue/fix lies here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NtUserEnumDisplaySettings and nodrv_CreateWindow errors, comparing a failing Proton launch on Xvfb with the working Xephyr case. Gather the requested logs and check the Proton launch path rather than the unrelated EasyAntiCheat report. Done means a windowed Proton application starts successfully on the reported virtual display without the driver or explorer errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100