ChrisAnd1998 / TaskbarX

Center Windows taskbar icons with a variety of animations and options.
https://chrisandriessen.nl/
MIT License
7.69k stars 482 forks source link

TaskbarX bugs after changing main monitor. #923

Open romanrsr opened 2 years ago

romanrsr commented 2 years ago

Describe the bug When I turn off my main monitor and turn on the second monitor, Taskbar gets buggy as you can see in the screenshot. The monitors have different resolutions, I don't know if this has to do with the problem. To fix it I have to restart TaskbarX

Screenshots image As you can see the bar is not centered, and the panel on the right (Time, Network, etc) is not visible.

Desktop (please complete the following information): Windows 10 21H2 19044.1566

Ectalite commented 2 years ago

I also have this problem after I wake my computer from the sleep, it doesn't show up the panel on the right. image

After restarting Taskbarx everything is fine.

Desktop: Edition Windows 10 Professionnal Version 21H2 Installed the ‎03/‎03/‎2022 Build 19044.1526

d-vrsky commented 2 years ago

I run into the same issue when switch from my laptop display to a monitor (not utilizing dual displays, switching primary display).

TaskbarX Ver: 1.7.6.0 Laptop Edition Windows 10 Pro Version 21H2 Installed on ‎2022-‎02-‎16 OS build 19044.1586 Experience Windows Feature Experience Pack 120.2212.4170.0

SuperTempAccount commented 2 years ago

I also experience this issue. This is the sequence of events in my case

  1. Use laptop without secondary display
  2. Close laptop and allow to deep sleep (doesn't seem to be an issue if just in sleep mode)
  3. Plug in a secondary monitor of higher resolution
  4. Open the laptop and log in
  5. Taskbar is cropped
  6. Restart TaskbarX

This happens when I'm working at one location with the laptop display then close the laptop, drive to another location, and use a secondary display.

Edition Windows 10 Enterprise Version 21H2 Installed on ‎31/‎03/‎2021 OS build 19044.1706 Experience Windows Feature Experience Pack 120.2212.4170.0

warduweram commented 8 months ago

I also have this issue during logon if my screen is off while Windows reaches the point during the startup process where I can log on. Also, my (4K) background image is rendered in 1080p in this case (this is how I reproduced the issue and started troubleshooting, I just rebooted and had my screen turned off till the login screen was available), I remember having quite a few issues with my 4K display back then on Windows 10 when it was turned off in certain situations that went away on Win 11 (and everything else got much, much worse, so don't take this as an incentive to switch :p I'm on Win 10 Enterprise LTSC IoT 21H2 now and I highly recommend it, it runs so much more smoothly especially than Win 11 which is just malware imo). This breaks my taskbar completely and I have to either restart explorer.exe and repopulate the systray by opening up its processes or log in again.

Temporary fix: I created a new scheduler task (maybe it works on the regular one if you adjust it, I haven't tried and won't since I'm happy for now) that delays the start of TaskbarX for 1 minute after logon. Strangely enough, it seems to be running already without the delay, but I don't get the issues.

@ChrisAnd1998 I think this might be more related to how Windows 10 handles sleep/reconnect on 4K resolutions rather than anything else, but it might also be related to multiple connected monitors (which I also have, but it just sits in the background and isn't turned on/off while these issues occur). Maybe the others can chime in whether they're all using 4K screens.

DeadmanCarnival commented 2 months ago

I have same problem although I use 1 Ultrawide monitor 49 inch, that when I work split for 2 sources. After work I switch to my personal computer to be ultra wide again and taskbarX seems to be blocked at previous resolution. Obiously fix is to restart taskbarX but it's kinda tideous to do it everyday couple of times.

Vald8 commented 1 week ago

I have exactly the same problem the op had 2 years ago, has there been any fix other than restarting the program when this happen ?