You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
ExplorerPatcher 22621.4317.67.1
Repro Windows Versions
Windows 11 24H2 Build 26100.2894
3rd party tweak software installed
none
Describe the bug
i have Windows 10 Taskbar (ExplorerPatcher) configured to be positioned on top .
after returning from sleep the taskbar won't show up when hovering top of the screen. this happens when applications are maximized and in focus. so far it happened to me with google chrome and deezer.
closing and reopening application or restarting explorer solves the issue
Expected outcome
the taskbar should appear when hovering the top of the screen
Actual outcome
the taskbar doesn't appear when other application windows are maximized
Additional info
No response
Crash Dumps
No response
Media
No response
The text was updated successfully, but these errors were encountered:
Before reporting your issue
Repro ExplorerPatcher versions
ExplorerPatcher 22621.4317.67.1
Repro Windows Versions
Windows 11 24H2 Build 26100.2894
3rd party tweak software installed
none
Describe the bug
i have Windows 10 Taskbar (ExplorerPatcher) configured to be positioned on top .
after returning from sleep the taskbar won't show up when hovering top of the screen. this happens when applications are maximized and in focus. so far it happened to me with google chrome and deezer.
closing and reopening application or restarting explorer solves the issue
Expected outcome
the taskbar should appear when hovering the top of the screen
Actual outcome
the taskbar doesn't appear when other application windows are maximized
Additional info
No response
Crash Dumps
No response
Media
No response
The text was updated successfully, but these errors were encountered: