Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
timminator opened this issue Mar 5, 2025 · 0 comments

Comments

@timminator
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant