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

Windows API Returns Incorrect Monitor Info #6945

Closed
Mercerudy opened this issue Oct 1, 2020 · 4 comments
Closed

Windows API Returns Incorrect Monitor Info #6945

Mercerudy opened this issue Oct 1, 2020 · 4 comments
Labels
External Dependency This bug or feature isn't resolved, but it's following an external work item. Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy

Comments

@Mercerudy
Copy link

Mercerudy commented Oct 1, 2020

Opening new issue, as instructed by @enricogior:

@Mercerudy
you have two monitors with the same 1920x1080 resolution, correct?
The Windows API returns only one monitor. We should try to escalate this to the Windows team.
Can you please open a new issue adding the output of the WMI command you ran and the screenshot of the Device Manager?

Originally posted by @enricogior in #1777 (comment)


I have two Samsung 1920x1080 monitors with drivers installed on Windows 10 20H2 Build 19042.541.

Device Manager:
image

The following WMI commands, Get-WmiObject win32_videocontroller and Get-WmiObject win32_desktopmonitor, return the following output, showing only 1 monitor:
WMI_Monitor_Info.txt

This renders me unable to set desktop zones on each monitor independently via MS PowerToys FancyZones.

@ghost ghost added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 1, 2020
@enricogior enricogior added Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy External Dependency This bug or feature isn't resolved, but it's following an external work item. labels Oct 1, 2020
@enricogior
Copy link
Contributor

We don't have yet a link to the external issue.

@crutkas crutkas removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 1, 2020
@Mercerudy
Copy link
Author

@enricogior @crutkas

Did this ever get escalated to the Windows team?

Thanks!

@Mercerudy
Copy link
Author

Rolling back the monitor drivers from those provided by Samsung revealed that the TeamViewer monitor driver had been installed over the Microsoft Generic driver. The monitors were still named "Generic PnP Monitor," but the driver properties showed the Driver Provider as "TeamViewer GmbH," even though TeamViewer was no longer installed on the system. Downloading and running the TeamViewer portable executable (no install required), and navigating to "Extras," "Settings," "Advanced," and finally "Uninstall" monitor driver reverted the monitors back to the Microsoft provided Generic PnP.

I then uninstalled PowerToys 0.25.0, deleted the local PowerToys appdata, reinstalled PowerToys and set up FancyZones again via the editor. FancyZones is now working as intended, and I finally have separate zones for each monitor with no need to switch them ten times a day.

Thanks to the team for helping to diagnose and for such great apps built into PowerToys.

@enricogior
Copy link
Contributor

@Mercerudy
thank you for the follow up, I've add the information to https://github.com/microsoft/PowerToys/wiki/Application-Compatibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
External Dependency This bug or feature isn't resolved, but it's following an external work item. Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy
Projects
None yet
Development

No branches or pull requests

3 participants