This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
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.
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.
Indeed that the graphics driver reset isn't going to work for many. It's not even a fix in any common understanding of the term. You're just purging the system of cached information that over time will re-establish and the issue will reoccur. Disabling protected view is a risk that no one should be taking in order to correct a scaling error within the OS. Especially a company that potentially has customers personal and professional information on stored databases. It's a vulnerability ripe for attack from a bad actor.
I know personally if I were the IT point man at a company I would avoid that workaround like the plague and the staff would have to suffer through the unsightly issue in order to maintain integrity of the protections in place to keep customer information secure. As for private home users that don't have that level of responsibility on their own systems this can be helpful as they don't have so much to worry about from outside attackers. They tend to focus more on companies than individuals as there's a larger "payout" (if you will) to attack a company.
Microsoft does need to address this issue. Specifically if they have professional users on devices that can be used to gain access into further infrastructure containing customer details using that workaround. If one company is using this workaround (speaking of disabling protected view in specific) then we can naturally assume many others are as well. This could end up being a major security flaw because of the human desire for symmetry.
Unfortunately that has not worked for me at all. Lately what I've found is that I have to go to options, pretend to change something, and then hit ok and it fixes itself. The wwindows-ctrl-shift-b has stopped working for me. And now this is happening in One Note but my options fix doesn't work.
Just to chime in, we've had a test group with protected view disabled for a good few months now and they haven't had the issue since.
Everyone saying to reset the graphics driver with that hotkey is all well and good, but if like us you are running in a Citrix environment that doesn't work.
Even if you don't use the office packages, but have them installed and protected view enabled it seems to be enough to cause the issue to occur.
Microsoft need to fix asap.
