Added display gets reported as internal display in Windows version 24H2

[timminator]

I noticed something weird on Windows version 24H2.

Until version 24H2 I could switch to just using the virtual display by typing in a command line window displayswitch.exe /external and it would disable the first monitor and just keep the virtual display active. This was also expected as the ParsecVDA is also reported as the second monitor in the display settings.

But after upgrading to Windows version 24H2 running displayswitch.exe /external disables the ParsecVDA and keeps the first monitor active. Now I would need to run displayswitch.exe /internal. But in the display settings the ParsecVDA is still reported as the 2nd monitor and not the main one.

Interestingly I could not replicate this on all devices. On my Laptop this behaviour did not change after upgrading to 24H2, but on a Desktop PC I could see this new behaviour.

Reproduction steps using 24H2:

1. Add a virtual display.
2. Open cmd and run a) displayswitch.exe /external or b) displayswitch.exe /internal
3. It disables a) the ParsecVDA instead of disabling the first monitor or b) disables the first monitor instead of the ParsecVDA --> Behaviour is exactly the opposite of what it should be.

I suspect this is not an issue with this app, but the ParsecVDA provided by Parsec, right?

[nomi-san]

Which GPU hardware and driver version are you using?
Have you ever used Parsec host with Privacy Mode enabled?

Interestingly I could not replicate this on all devices. On my Laptop this behaviour did not change after upgrading to 24H2, but on a Desktop PC I could see this new behaviour.

Laptop always has a immutable internal display.

I suspect this is not an issue with this app, but the ParsecVDA provided by Parsec, right?

Yeah you should report the issue to Parsec Discord.

[nomi-san]

Does it produce the same issue with Virtual-Display-Driver (newer IddCx) and your fork?

[timminator]

I actually noticed this problem the first time while using the ParsecVDA in Hyper-V VMs. I've created a fork of the original Easy-GPU-PV project that permanently adds a virtual display and uses it then exclusively by switching to it using displayswitch.exe /external. With version 24H2 this did not work correctly anymore. This was done with a GTX 1660 Ti passed through to the VM.
I thought this might be an exclusive problem related to Hyper-V VMs but that was not the case. I could also recreate it on an Athlon 3000G after upgrading to 24H2. Before that it worked correctly there aswell. So I'm pretty sure this is a general issue with the new Windows version.

I've never used Parsec with Privacy Mode enabled.

I cannot reproduce it with the Virtual-Display-Driver. On my fork it happens aswell I just thought maybe you know something about this :-).

On reporting it to Parsec Discord: This whole project is something that is not officially supported by Parsec and I also never had Parsec Premium with their VDD features, so I don't know how I should bring this issue to their attention. Or do you think it is not an issue talking about this project in their discord?

[nomi-san]

I'm sure that is 24H2 issue, let's wait for more reports on Virtual-Display-Driver repo.
Found some issues that may be related:

• https://answers.microsoft.com/en-us/windows/forum/all/why-does-win11-24h2-have-problems-with-my-second/1176e183-2eaa-42bf-8580-b81e50929849
• https://answers.microsoft.com/en-us/windows/forum/all/how-to-fix-2nd-display-not-working-after-24h2/97b1a4a9-b9d1-4610-8490-7dca2f56a45d
• https://www.youtube.com/watch?v=tpYBfzFInCs

On reporting it to Parsec Discord...

Unofficial way does not matter. You just tell that the issue occurs when connected to host with 1 additional virtual display (already Parsec Warped 😅), people will notice it.