Originally created by @fpf3 on GitHub (Jun 23, 2023).
Description
Visual Studio 16.0 2019 configuration manager seems to leave behind invisible windows, which Komorebi attempts to manage. This leaves large portions of the screen inaccessible.
After Visual Studio is closed, these regions of the screen become accessible again.
To Reproduce
Open a solution in Visual studio
In the solution explorer, right-click on a project and select 'Properties'
If Visual Studio does not resize to fill only half the screen, close out of the properties window and try again (in my usage, this never takes more than two attempts)
Expected behavior
Either Visual Studio is never resized, or returns to filling the entire screen when the properties window is closed.
Screenshots and Videos
Operating System
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19045 N/A Build 19045
komorebic check Output
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\f.frey
Looking for configuration files in C:\Users\fpf3
Found komorebi.ps1; this file will be autoloaded by komorebi
Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is started
Originally created by @fpf3 on GitHub (Jun 23, 2023).
**Description**
Visual Studio 16.0 2019 configuration manager seems to leave behind invisible windows, which Komorebi attempts to manage. This leaves large portions of the screen inaccessible.
After Visual Studio is closed, these regions of the screen become accessible again.
**To Reproduce**
- Open a solution in Visual studio
- In the solution explorer, right-click on a project and select 'Properties'
- If Visual Studio does not resize to fill only half the screen, close out of the properties window and try again (in my usage, this never takes more than two attempts)
**Expected behavior**
Either Visual Studio is never resized, or returns to filling the entire screen when the properties window is closed.
**Screenshots and Videos**

**Operating System**
```
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19045 N/A Build 19045
```
**`komorebic check` Output**
```
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\f.frey
Looking for configuration files in C:\Users\fpf3
Found komorebi.ps1; this file will be autoloaded by komorebi
Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is started
```
adam
added the bug label 2026-01-05 14:49:06 +01:00
You should be able to look at the output of the state command and identify the window that is creating the ghost tile and add a float rule for it. Once you figure out the right rule, please also raise a PR to the app specific config repo for the benefit of other users in the future. 🙏
@LGUG2Z commented on GitHub (Jun 23, 2023):
You should be able to look at the output of the state command and identify the window that is creating the ghost tile and add a float rule for it. Once you figure out the right rule, please also raise a PR to the app specific config repo for the benefit of other users in the future. 🙏
Limited testing seems to indicate that this is resolved. I will comment/re-open if I find otherwise.
Thanks for the quick response!
@fpf3 commented on GitHub (Jun 23, 2023):
I think it's this guy:
```
windows": {
"elements": [
{
"hwnd": 464990,
"title": "WindowsFormsParkingWindow",
"exe": "devenv.exe",
"class": "WindowsForms10.Window.8.app.0.e2be13_r44_ad1",
"rect": {
"left": 963,
"top": 535,
"right": 944,
"bottom": 502
}
}
],
"focused": 0
}
```
Limited testing seems to indicate that this is resolved. I will comment/re-open if I find otherwise.
Thanks for the quick response!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @fpf3 on GitHub (Jun 23, 2023).
Description
Visual Studio 16.0 2019 configuration manager seems to leave behind invisible windows, which Komorebi attempts to manage. This leaves large portions of the screen inaccessible.
After Visual Studio is closed, these regions of the screen become accessible again.
To Reproduce
Expected behavior
Either Visual Studio is never resized, or returns to filling the entire screen when the properties window is closed.
Screenshots and Videos
Operating System
komorebic checkOutput@LGUG2Z commented on GitHub (Jun 23, 2023):
You should be able to look at the output of the state command and identify the window that is creating the ghost tile and add a float rule for it. Once you figure out the right rule, please also raise a PR to the app specific config repo for the benefit of other users in the future. 🙏
@fpf3 commented on GitHub (Jun 23, 2023):
I think it's this guy:
Limited testing seems to indicate that this is resolved. I will comment/re-open if I find otherwise.
Thanks for the quick response!