Taskbar previewe failed when using Fences

icon of files moved to desktop after changed the name

Hi,

I have encountered 2 problems with Fences.


#1 Problem:

Windows11 22H2 + Fences 4.0.7.2

I have a new installation of Fences and have not customized any settings.
When I change the name of a file in one of the desktop partitions of Fences, it leaves the partition and appears in the desktop of Windows instead.

Here is a video about this problem: https://we.tl/t-ZLM8RRLzlM


#2 Problem (like this posts: https://forums.stardock.com/510988):

Fences 4.0.7.2 + Windows11 22H2 OS22621.675
And, I already tried purge and reinstalled and reboot, however, the problem still exists.

After installing and starting Fences4, moving the mouse cursor to the icon of Excel and other software(example Chrome) will show the preview window, but after selecting one of them and opening it, then moving the cursor to the icon of Excel and other software(example Chrome), the preview window will not be shown again.
You can only move the cursor at first, and click on other software, and then return to click on Excel to resume normal. (But the problem will reappear again in a short while)

For comparison, if disable or uninstall Fences, this problem does not occur again.

Here is a screen recording of the problem, I hope it will help you understand:
https://we.tl/t-Hz7IVT89fQ


Could you please help me to fix these 2 problems, thank you very much!

If you need more details, please contact me.

4,292 views 1 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues.


1) By default, Fences rule is set to send all new icons into desktop. When you rename a file or a folder. It will be consider as a new file or a new directory, Fences will relocate that "new" icons/folder to desktop. If you do not wish that to happen. Than you will have to assign all new icons be send to a Fences.


2) I can not reproduce you issue on my system. I made a short video below. As a suggestion, please try to update your Windows to the latest official release.

Thanks
Basj,
Stardock Community Assistant.