Fenced window now black, icons not visible on primary monitor (posible Start 11 conflict)

After an update of Start 11 and a reboot, all of my fences are showing black background and icons are not visible.  When I move a fence to a different monitor, the icons show up.

The background color was apparently reset and transparency was set to the extreme right.

When I adjust the transparency, the color does change.  On the second monitor, it works properly, on the primary monitor, it acts as if there is something interfering with it.

HDR is not on.

Fences version (after reinstall) is 6.46

The fences on the main monitor act as if there are two windows fighting each other, when I move the mouse over, it flickers.  During a boot, they show the icons, then they seem to get hidden.

When the same fence is on the second monitor, there is no flickering

 

I followed the steps listed in another thread:  https://forums.stardock.com/541565/fenced-icons-now-invisible-start-11-conflict

  1. Uninstall Fences
  2. Reboot immediately (important)
  3. Download latest version available in your account product download page: https://store.stardock.com/myaccount/products. 
  4. Install it
  5. Reboot immediately again. 
  6. Retest it

 

530 views 3 replies
Reply #1 Top

Should be fixed in a Start 11 update with fix coming shortly, v2.72. Thanks for the report!

Reply #2 Top

It's been 2 weeks since your reply.

Any word on when the Start11 update will be out?

 

I installed the beta for Start 11 2.7.2, it did not solve the problem

 

Disabling the enhanced taskbar in Start11 does seem to resolve the issue, however this is an unacceptable long-term solution since I use that functionality a lot

 

Reply #3 Top

Hello,

Sorry to hear you are having issues. There is a new Start11 v2.72 full released yesterday. Have you tried it yet? If you have not, Please try, uninstall Start11, reboot immediately (important), download the latest version available in your account product download page: https://store.stardock.com/myaccount/products. Install it, reboot immediately again. Retest it and report back.

Thank you,

Basj,

Stardock Community  Assistant.