Can't see the text when renaming files in fences

When i want to rename a file or folder, the text backround changes, but the text color is the same as the backgroundcolor... so i can't see what i'm typing...

 

Koen

adoewa

24,535 views 20 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. But I can't see it. Please post a screenshot of your issue.


Basj,
Stardock Community Assistant.

Reply #2 Top

Hi, I have the same. I am running WindowFX, WindowBlinds, Iconpackager, Deskscapes and Fences.

Fence in normal view

Fence with icon selected but no mouseover

Fence with mouseover and selected

Photo of icon selected and rename (F2)

Oddly enough when I took a screenshot of the icon selected and renaming (F2) the screenshot showed me something I did not see.

This behaviour just suddenly started happening, I have no idea what triggered it but I would very much like this resolved too...

 

Reply #3 Top

Quoting robinedgar, reply 2

Hi, I have the same. I am running WindowFX, WindowBlinds, Iconpackager, Deskscapes and Fences.
End of robinedgar's quote

Hello,
Sorry to hear you are having issues. Need to know more on your system.

  1. Windows version, please use Winver.exe for full version numbers.
  2. Fences version.
  3. WindowBlinds version
  4. Need to know what Windowblinds theme you're using. And does the issue happened if you change to other Windowblinds theme such as Acrylic 7


Basj,
Stardock Community Assistant.

Reply #4 Top

Hi, thanks for getting back so quickly!

If I use default theme there is no effect. I have also tried all the substyles for Acrylic 7 and no effect.

Windows 10 version 1909 OS build 18363.1316 (winver.exe)

Fences 3.0.9.11

Windows 10 Enterprise (18362.19h1_release.190318-1202)
WindowBlinds 10.84 (059 - Windows 10 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                   2019/11/18 14:41:12
        Wblind64.dll                 2019/11/18 14:41:51
        Wbsrv.dll                    2019/05/04 05:29:46
        WB10Config.exe               2019/11/18 14:41:16
        Wbload.dll                   2019/05/08 21:13:37
        Screen10.exe                 2019/05/04 05:29:17

WindowFX 6.05

Iconpackager 10.03

DeskScapes appears to be activated on this PC
DeskScapes engine appears to be running

(Generic PnP Monitor) 1 is attached to NVIDIA GeForce RTX 2070 SUPER

Deskscape.dll                  2019/08/13 18:12:18
Deskscapes.dll                   2019/05/01 22:12:52
DreamControl32.dll                 2019/08/13 18:12:50
DeskscapesConfig.exe                  2019/08/02 20:34:08
UI\Deskscape.dll                2019/08/02 14:49:28
UI\DeskscapesVideo.dll         2019/05/01 22:12:54
DreamTasks.exe                   2019/05/01 22:12:29
DeskscapesVideo.dll              2019/05/01 22:12:22

Best regards,

Robin

Reply #6 Top

No luck with the cleanboot. I did notice that there were 2  Fences settings items which I kept both and also that I can rename in "normal" fences fine but the problem is only in the Folder Portals. This goes for both the new and the current user account. I don't use the "normal" fences so I hadn't noticed before...

Cheers

Robin

Reply #7 Top

Still, I can't recreate your issue on my system. Not really sure what is happening on your system. May I know what Iconpackager style you are using on your system? Also, noticed you're not updating to latest Windows version, V20H2? Any specific reason for not updating it? And have you tried "SFC /scannow" to check if you have corrupted system files?

Thank you,

Basj,
Stardock Community Assistant

Reply #8 Top

ok so a whole lot of rebooting later: did a sfc /scannow, then purge uninstallaed windowfx, windowblinds, deskscapes, iconpackager and fences. Found fencesmenu64.tbd hadn't been deleted so got rid of that. Reinstalled fences. Same behavour. Sfc /scannow again and still no luck :'(

Reply #9 Top

May I know what is your monitor/s resolutions and scaling applied to it (100%,125%,150% etc). And is the portal fences linked to local drive or network drive? Any problem if you update your Windows 10 to later versions?

Thank you,

Basj,
Stardock Community Assistant

Reply #10 Top

It's a 55" LG TV with HDR on, resolution 3840 x 2160 landscape, scale set to 100%

I have a both a portal to a local drive and to a mapped network drive and the behaviour is the same.

I don't have any updates under windows update. This is an Enterprise version of windows 10, which might be why?

Thanks!

Reply #11 Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #12 Top

Quoting robinedgar, reply 10

It's a 55" LG TV with HDR on, resolution 3840 x 2160 landscape, scale set to 100%
End of robinedgar's quote

Do you still see the issue on a normal monitor?

Sean Drohan
Stardock Support Manager

Reply #13 Top

Hi, I don't actually have a normal monitor, so it took a while. In the end I extended my desktop using SpaceDesk to a Samsung S7 tablet and dragged the frame there and... yes you can see it properly there (ie you can read the text when you rename / F2). So figuring it's somewhere in the connection to the TV I checked

Display Settings and turned Off "Play HDR games and apps".

This changed the behaviour on the TV so with HDR off I can see the text whilst renaming. Obviously I do want HDR enabled - Aside from a 55" screen being great for work, it's also great for movies and gaming!

Reply #14 Top

I have the same issue with my LG Monitor (not a tv ) Model #LG32GQ950B. Turning off Windows HDR fixes it and turning it back on the issues remains.  I cannot see the filename I am renaming. I'm also using an NVIDA RTX 4080 with the latest nvida Drivers 551.52.

Reply #15 Top

Same problem with a 55G2 Oled LG TV.

Reply #16 Top

Quoting Poet, reply 14

I have the same issue with my LG Monitor (not a tv ) Model #LG32GQ950B. Turning off Windows HDR fixes it and turning it back on the issues remains.  I cannot see the filename I am renaming. I'm also using an NVIDA RTX 4080 with the latest nvida Drivers 551.52.
End of Poet's quote

Quoting filouk, reply 15

Same problem with a 55G2 Oled LG TV.
End of filouk's quote

I believe its an issue when the HDR turned on. As a work around, try disable HDR and see if that help with the issue. Refer screenshot below. Its from Windows 10. If you have Windows 11 it should be around the same setting. Its in Setting->Display->Windows HD color.

Please try it and report back.

Thank you,

Basj,
Stardock Community Assistant

Reply #17 Top

Display HDR options had no effect on my devices. (half of which don't even support HDR)

However, I found a quick solution that did resolve this this issue on all my devices using fences.

1. Navigate to System > Display > Advanced display
2. Disable "Automatically manage color for apps"
*Note:
Be sure to do this for any display(s) with Fences portal

I was able to reproduce and resolve this issue on different monitors and different systems, so hopefully this works for someone else too. :grin:  

Cheers

Reply #18 Top

Quoting ChrisAnonymous, reply 17

Display HDR options had no effect on my devices. (half of which don't even support HDR)

However, I found a quick solution that did resolve this this issue on all my devices using fences.

1. Navigate to System > Display > Advanced display
2. Disable "Automatically manage color for apps"
*Note:
Be sure to do this for any display(s) with Fences portal



I was able to reproduce and resolve this issue on different monitors and different systems, so hopefully this works for someone else too. :grin:  

Cheers
End of ChrisAnonymous's quote

I tried to look for this setting on my Windows 10 system. But, I can't find it. Any idea where it is at in Windows 10?

Thank you,

Basj,
Stardock Community Assistant

Reply #19 Top

Quoting basj, reply 18

I tried to look for this setting on my Windows 10 system. But, I can't find it. Any idea where it is at in Windows 10?

Thank you,

Basj,
Stardock Community Assistant
End of basj's quote

Unfortunately, all of my systems run on Win11. Sounds like Win10 could have a different service conflict.