valinet / valinet/ExplorerPatcher
Second monitor issue
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 33.9k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before reporting your issue
- I have confirmed that this issue does not happen when ExplorerPatcher is not installed
- I do not have "register as shell extension" enabled
- I have tried my best to check existing issues
Repro ExplorerPatcher versions
Explorer Patcher 70.1
Repro Windows Versions
Win 11 25H2 26200.8457
3rd party tweak software installed
PowerToys v0.99.1 (but I think it is not important)
Describe the bug
After connecting secondary monitor (notebook --> through USB dock or directly HDMI port - both situation) AND while my Main panel is on left side, there is about 50% chance for:
Maximized window is about 1/4 window height and cannot be higher while not maximized can be any size;
When I move main panel down - windows shows corectly and it stay correct even if I move main panel back to left side ...
Expected outcome
maximized windows are maximazed on whole display
Actual outcome
maximized window use all width but just part of height of display
Additional info
No response
Crash Dumps
No response
Media
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce on Windows 11 25H2 build 26200.8457 with ExplorerPatcher 70.1, using a secondary monitor through the dock or HDMI and placing the main panel on the left. Compare maximized-window sizing before and after moving the panel; done means maximized windows consistently occupy the full display height in the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100