You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Add a virtual display.
Open cmd and run a) displayswitch.exe /external or b) displayswitch.exe /internal
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?
The text was updated successfully, but these errors were encountered:
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 rundisplayswitch.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:
displayswitch.exe /external
or b)displayswitch.exe /internal
I suspect this is not an issue with this app, but the ParsecVDA provided by Parsec, right?
The text was updated successfully, but these errors were encountered: