After running the script and trying to connect, Parsec gives error 15000

[bryceadam1]

I tried setting up a Parsec gaming server on an AWS EC2 g4dn.xlarge instance. I ran the script from RDP and logged into Parsec. Everything went off without a hitch, no error messages. After running the script, I restarted the instance and tried to connect via Parsec only to see a black screen for a few seconds, then the error message.

Any ideas as to why this might be happening or what I might need to do to work around this?

[bryceadam1]

After looking a little bit deeper into what happened, it looks like the drivers weren't actually installed. I looked into the GPUUpdaterTool.ps1 script to see what is happening, and it looks like there are some errors happening inside of the downloadDriver function. The reason that it seemed like everything worked seamlessly the first time I ran the script was because the powershell window closes immediately after the errors happen.

My powershell knowledge is very limited (next to zero), so I'm not sure what needs to be fixed in the script to make it work, but I was eventually able to get Parsec to connect to my instance by manually installing Nvidia gaming drivers and configuring windows to log on automatically using these instructions:

• Install NVIDIA drivers on Windows instances (Option 4, also tried Option 3 with similar results)
• Turn on automatic logon in Windows

However, now I have the issue that Parsec cannot change the resolution to anything above 1366x768. This may be an issue with the Nvidia drivers, but I am not sure. When I try to set Parsec to a resolution above 1366x768, it seems to revert to 1280x1024. This is confirmed by looking at the Nvidia Control Panel. Notice that I cannot add any custom resolutions because the button is grayed out (see the attached image).

For now, it seems like what I have done is only a partial fix, and I will have to live with the reduced resolution, because I can't think of anything else to try. Let me know if any of you have any suggestions.

[NickMoores]

I'm also seeing my Parsec session set to 1280x1024 when the EC2 instance is booted. I can change it by changing the resolution to 4k and back again in Parsec, but it's mightily annoying having to do that every time.

Anyone found a permanent resolution or workaround for that?

[Boston-of-Gilead]

Out of curiosity, if you run C:\ParsecTemp\Drivers\DisableSecondMonitor.ps1 , do you get this error?