Nvidia Driver 398.36 Breaks Fences

Fences has always had issues with Nvidia drivers on my three monitor system. Every time Nvidia updates the drivers all the fences mash together on the main center monitor and I have to drag them all around to get them back to where I had them and no saving a snapshot has NEVER worked so i dont even waste my time with that! Now however with the update released yesterday all the fences have as usual mashed onto the main screen, all overlapping and disgusting. Problem is I can no longer click on them and drag them, they are stuck right where they are and I can click on and bring it to the front so at least I have that but this has got to the point of making Fences totally worthless!

I even tried to uninstall Fences and reinstall but apparently uninstalling Fences is only an illusion since uninstalling, rebooting and reinstalling bring back all the old fences and as you probably guess they are all mashed onto the center main monitor. So apparently uninstalling Fences is not really uninstall at all! 

So how do I fix this? Or do I finally just throw in the towel and admit Fences is broken and find a better solution to managing my files and folders?

38,808 views 11 replies
Reply #1 Top

What version of Fences and what version of Windows?

 

Reply #2 Top

Sorry, Fences version 3.0.9 and Windows 10

Reply #3 Top

WOW, great support guess it is worth knowing when I buy something from Stardock support is optional and not guaranteed!

Reply #5 Top

Quoting earthrat, reply 3

WOW, great support guess it is worth knowing when I buy something from Stardock support is optional and not guaranteed!

This is only a  WinCustomize support forum. If purging and installing doesn't work then you would have to go to StarDock and fill out a support ticket.

Reply #6 Top

I'm using that driver too and Fences didn't break for me, and this is coming from someone who has had all sorts of issues with Stardock stuff lately on Win10. There must be some other issue at play with it breaking for you than just the driver.

Reply #7 Top

Thanks, the purge worked.

Khitteh, if you are not running a three monitor setup then what is happening to me is not the same issue that I am having. Would be curious to know if you are running multiple monitors though because if you are and not having these issues I need to look elsewhere for the problem.

Reply #8 Top

Sounds like it's something to do with multiple monitors then, I'm only running one (as well as having updated to 398.36), which didn't cause issues for me with Fences. I'd start looking there - check any settings Fences uses with multiple monitors.

Reply #9 Top

Yea not sure, made a few tweaks and will wait for the next update to see if it helps. There is only one parameter I can see that appears to have anything to do with multiple monitors and that is the one that says "Store my Fences' positions on a per-screen-resolution basis. Since all of my monitors are identical I did not consider bothering with this one because it deals with what I assume is monitors with different resolutions. Will enable it anyway and see if there is some hidden feature of this parameter that will stop this non-sense!

Thanks for sticking with me on this khitteh, if you are in the US have a happy 4th!

+1 Loading…
Reply #10 Top

I have a triple monitor setup and have had this problem for a while. Fences simply sucks at handling multimonitor systems, custom icon spacing, and hidpi scaling.

 

BUT, the good news is that there is a workaround. After installing the Nvidia driver update, reboot immediately. I think Stardock is using some wonky display enumeration (along with dimensions, offsets, icons spacing, and hidpi scaling), and rebooting before a snapshot is taken will allow fences to enumerate however it's used to doing it.

 

Now if I could just drag and select any icons in the left column of a fence without overshooting by half the screen, that would be nice...

Reply #11 Top
Neurohax2 - Unfortunately I dont see this ever getting fixed. I had opened a support ticket back when it was first happening and was told this is an Nvidia problem. Anyone with even basic coding background knows that is a load of crap and to think it should be the responsibility of a hardware driver to accommodate software is absurd. I have been hopeful a viable competitor sees the value in something like fences so I can drop this half baked software all together...