-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
wt.exe windows does not restore correctly after exiting full screen #17214
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
@zadjii-msft no, mine is intel core i9 vPro and independent GPU. Same hardware, no problem when I fall back to Windows 10, problem just comes up only with Windows 11. |
Thanks for filing! We're gonna mark this as a /dup of #14865. |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
@zadjii-msft @carlos-zamora Hi, is there a plan to identify and fix this issue? this seems to be a very old one, which was raised almost two years ago. |
We've got a line out to some DWM folks currently. They think it's a DWM bug, so we'll need to get them some traces. |
ah, good news, b.t.w, are these codes inherited from windows 10 or are they completely new codes introduced in windows 11? |
I can't say I have any idea how DWM is implemented 😅 |
Windows Terminal version
1.20.11271.0
Windows build number
10.0.22635.3570
Other Software
No response
Steps to reproduce
Expected Behavior
wt.exe window shall restore previous state
Actual Behavior
the wt.exe window does not restore normally, some of its full screen window remains stubborn on the desktop window.
The text was updated successfully, but these errors were encountered: