Windows 10, multi Monitor, maximized window blank/empty space on top of screen

Anonymous
2018-08-22T16:21:29+00:00

This problem happens with all windows when maximized. 

When the window is maximized there is a bar at the top of the screen through which i can see my desktop. Its like that range that the window can maximize has been shortened.

Here is the link from reddit and this is the exact issue i am having. 

https://www.reddit.com/r/sysadmin/comments/8imjva/windows\_10\_multi\_monitor\_maximized\_window/

We did install all the latest and greatest patch that are available of today and nothing seems to work.

Any help please

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2018-10-22T16:55:14+00:00

In that Reddit thread, there is a suggestion that worked for me.

Right click desktop, go to Intel HD Graphics settings. Select Display and then choose the option Scale Full Screen. Make sure the option Override Application Settings has the checkbox marked.

Was this answer helpful?

700+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2018-09-26T07:27:15+00:00

Same annoying issue here on Windows 10 x64 1803 with all updates until now!

The issue appears on several apps (chrome, IE, eagle, ...) so it does'nt depends on the app.

My setup is: 2x HDMI/DVI 24" Monitors on an Radeon HD 5450. Internal Intel GPU is not used.

The issue just happend recently sind a few weeks.

I have found an workaround which helps at least for me:

 * Open Task Manager

 * Goto Tab Details

 * select dwm.exe and click "Kill Proccess"

dwm.exe will be closed and restarted automatically from windows and issue is gone.

Yeah i'll know, its a rather annoying workaround but the quickest for me until a real solution pops up.

Was this answer helpful?

500+ people found this answer helpful.
0 comments No comments

274 additional answers

Sort by: Oldest
  1. Anonymous
    2019-04-18T17:38:39+00:00

    I have the same issue on two different triple monitor setups with Windows 10:

    1. Gigabyte Laptop - all latest drivers
    2. Self-built Desktop - all latest drivers

    Affects primary monitor only, when an application is maximised. Not application specific.

    It went away for a while, appears to have been reintroduced by a driver update recently.

    The shortcut to restart the graphics driver fixes it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-04-29T02:24:20+00:00

    Not sure how many people are seeing this at the moment , Can any one advise if they've opened a job with Microsoft in regards to this issue?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-04-29T06:26:57+00:00

    We ran into this issue at my work and I found this thread. Someone said something about it only affecting the default monitor, so I thought "What if we switch the default monitor?" So we made the secondary monitor default and it made the problem go away, then we switched back and it remained fixed for now. Not sure if it will work every time or is a long term solution, but it's definitely easier than rebooting your computer.

    TLDR: Swapping the secondary to primary monitor and back made the problem go away for us.

    Hey, I've been using this work around for months now, its a super annoying bug. It happens only with 2 screens connected, but across all kinds of different computers.  We' ve a bunch of dell desktops it happens to, but also to all the MS Surface products using a dock. Changing the default monitor and swapping it back has worked temp for some and for others it doesn't seem to have come back ... yet! So can't quiet get to the bottom of it. Glad there's threads on it now, when I first looked for some info last year there wasn't much to be found. It has been going on for a long time. :-(

    Was this answer helpful?

    0 comments No comments