https://www.displayfusion.com/Discussions/RSS/?TopicID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a DisplayFusion RSS: Second taskbar stops working after nVidia driver update Sat, 16 May 2026 21:05:17 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#6 Fri, 31 Mar 2017 20:03:45 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#6 DisplayFusion In the registry, if you look in this key: HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\Taskbars, are there subkeys for both 1 and 2? If so, do they both have a Position value? ]]> https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#5 Fri, 31 Mar 2017 12:29:10 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#5 DisplayFusion I'm confused, if monitor ID changes, but DF somehow really doesn't care, then why it stops working? ]]> https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#4 Wed, 09 Nov 2016 19:14:56 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#4 DisplayFusion Could be that the position setting has been set for the taskbar both when it was on monitor ID 1, and 2. DisplayFusion doesn't control the Windows taskbar position, but if you set the DF taskbar to left on monitor 2, then at some point that monitor switched to 1, and you set it to left again, DF will remember that position for both monitor IDs. ]]> https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#3 Wed, 02 Nov 2016 12:36:39 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#3 DisplayFusion Now I'm just curious, why the location of the taskbar doesn't change then?
On my main monitor it's at right side and on second monitor it's at left side, after driver update DF shows taskbar properly at left side of second monitor. ]]> https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#2 Fri, 28 Oct 2016 18:38:45 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a#2 DisplayFusion On some machines, when the NVIDIA drivers update, the monitor IDs get swapped, which would cause the issue you're seeing. Unfortunately you've found the best workaround, which is to reboot. Rebooting after the driver update resets the monitor IDs ]]> https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a Tue, 25 Oct 2016 03:19:27 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/second-taskbar-stops-working-after-nvidia-driver-update/?ID=d0e4d7f4-b2c5-4f00-bff4-4f36a845455a DisplayFusion Hello.

After each nVidia driver update (which doesn't require windows restart) DF taskbar on second monitor stops working. It shows windows built-in taskbar instead (however right click shows DF menu). So basically the size changes and shortcuts are gone. Restarting DF doesn't help. The only way to restore DF functionality is to restart computer.

Windows 10 x64 AU built 14393
DF 8.1 Beta 2
Main monitor connected to nVidia video card, second monitor (where DF is) connected to onboard Intel video.

Anyone else have this issue? ]]>