Fences never restores icons to the correct monitor after connecting my docking station

FencesIssueReport_v6.0.0.2_2025-09-09_10-26-30 John Simon.zip

I uploaded an issue report about a problem where Fences never restores icons to the correct monitor after connecting my docking station.  I did not get any follow up communication.  Could you please confirm it was received?

Moved to Fences area

27,451 views 14 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. I have forwarded 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. Thank you.

Basj,
Stardock Community Assistant

Reply #2 Top


I uploaded an issue report about a problem where Fences never restores icons to the correct monitor after connecting my docking station.  I did not get any follow up communication.  Could you please confirm it was received?

Are you certain you are using this option:

Sean Drohan
Stardock Product Lifecycle Manager

Reply #3 Top

Hi John, following up on this, we got your report.

It does look like it's configured correctly, and we do see the transformation appearing (apparently properly, but apparently not so) upon adding and removing of screens. Hoping to get some more info to get started.

It looks like it's going from one screen at 2400x1600@200, to 3 screens [2560x1440@100][2400x1600@200][2560x1440@100], with "2560x1440@100" as the primary in the center, correct?

I wonder if you might submit another report, but before doing so take a couple of snapshots.

(1) Make a backup with the single monitor configuration, set up the way you want it for single monitor. After taking the backup, click on it and click rename to name it "Single monitor configured"

(2) Attach to dock. Assuming it comes up broken, take a backup, and likewise name it "Docked, broken"

(3) Fix the layout to be the way you want it, possibly using the "Swap monitor" option found in the Layout tab if it's helpful. Take another backup, name it "Docked, fixed"

(4) Undock. Take another backup, name un "Undocked #2".

(5) Dock again. Take another backup, name "Re-docked", without fix it it if it's broken.

 

Working to get an idea of what actually is going on here, as well as what you're expecting to help so that we can trace it in the logs. Thanks for the help.

 

Just to share context on what we're seeing here, we do see that entry for the 3 monitor setup [2560x1440@100][2400x1600@200][2560x1440@100], but it says that it's downgraded to 2400x1600@200, meaning that when all 3 monitors are present, only that one monitor is in use. I'm guessing though that you're wanting things on that middle screen, "2560x1440@100", correct?

And to confirm behavior, when you plug, it goes from the center screen 2560x1440@100 to the one screen 2400x1600@200, but does not go back to 2560x1440@100 when you plug back in?

Thanks again for help wrapping hands around the config.

 

 

Reply #4 Top

Yes, when I dock, I want the middle screen to be my primary screen.  You should be able to see the taskbar icons next to the clock to indicate which is my primary screen.  

 

I can't seem to find where the backup files are stored.  I looked in the install directory and poked around in the users directory.

Reply #7 Top

I just uploaded the files and referenced this thread in the text of the issue.

Reply #8 Top

These files have been uploaded.  Has anyone had a chance to take a look at them?

FencesIssueReport_v6.0.0.2_2025-09-25_08-54-26 John Simonq.zip

Backups John Simonq.zip

Thanks,

 

-John

Reply #9 Top

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

Basj,
Stardock Community Assistant

Reply #11 Top

Hi jsimon669 thanks for much for your report and effort (and patience) here.

The team has been able to pick the report apart, and thanks to your captures, they were able to find the tiny thing going wrong causing the big problem for you, and we think we have a resilient fix for this scenario. Stay tuned and we'll see if we can get out a patch for you to test.

+2 Loading…
Reply #12 Top

Thanks, this is great news!  Looking forward to getting the patch to test. 

Reply #13 Top

Hi jsimon,

Patch is ready for your testing! Fingers crossed, but we were able to exactly reproduce using the snapshots you submitted, so it's looking good that this will resolve.

https://www.dropbox.com/scl/fi/fxrz303c0dj3raitexubh/UpdatePatcher_Debug_2025_10_14__4_53_40_am.exe?rlkey=p0iiy402y39t8qeatczv9dmgo&dl=1

*update, fixed link

Version number should show up in the About pane as 6.05 (and 6.0.5.0 upon hover).

 

Of the snapshots, it was this sequence of 3 that allowed the reproduction, so in the hopefully very unlikely case it continues, these would be the 3 to retake.

 

"It should just work", but the fun technical detail, after going back from 1 monitor to 3, the registry field ResolutionLastScores in Settings should read something like the below. "1:[2560x1440@100]+" at the top, indicating that the "all icons are on the single monitor [2560x1440@100%dpi]primary-mon" profile is the one selected – redirected from the profile of "[2560x1440@100%dpi]primary-mon, and secondaries [2400x1600@200%][2560x1440@100%dpi]"

(0F133002B98FE59D) 1:[2560x1440@100]+ (upgraded)
(0F13300000000000) 3:[2560x1440@100]+[2400x1600@200][2560x1440@100] (exact) (redirected to 1:[2560x1440@100]+)
(0F100002B99008C4) 1:[2400x1600@200]+ (upgraded)
(0F1000029C73D5A0) 3:[2400x1600@200]+[2560x1440@100][2560x1440@100] (redirected to 1:[2400x1600@200]+)
(0F1000029C73D5A0) 3:[2400x1600@200]+[2560x1440@100][2560x1440@100] (redirected to 1:[2400x1600@200]+)
(0F00000000000000) 3:[2560x1440@100]+[2400x1600@200][1920x1080@100] (redirected to 1:[2560x1440@100]+)
(0F00000000000000) 3:[1920x1080@100]+[2400x1600@200][1080x1920@100] (redirected to 1:[1920x1080@100]+)
(0F00000000000000) 3:[2400x1600@200]+[1920x1080@100][1080x1920@100] (redirected to 1:[2400x1600@200]+)
(0F00000000000000) 3:[2400x1600@200]+[1920x1080@100][1920x1080@100] (redirected to 1:[2400x1600@200]+)
(0F00000000000000) 3:[2400x1600@200]+[2560x1440@100][1920x1080@100] (redirected to 1:[2400x1600@200]+)
(0F00000000000000) 3:[2400x1600@200]+[3840x2160@300][1920x1080@150] (redirected to 1:[2400x1600@200]+)
(0E133002A8277174) 2:[2560x1440@100]+[2400x1600@200] (redirected to 1:[2560x1440@100]+)
(0E133002A8277174) 2:[2560x1440@100]+[2400x1600@200] (redirected to 1:[2560x1440@100]+)
(0E1000029C73B524) 2:[2400x1600@200]+[2560x1440@100]
(0E000002A274817B) 2:[2400x1600@200]+[1920x1080@100] (redirected to 1:[2400x1600@200]+)
(0E0000028DEC5147) 2:[2560x1440@100]+[1920x1080@100] (redirected to 1:[2560x1440@100]+)
(0E0000025D83825F) 2:[1920x1080@150]+[3840x2160@300] (redirected to 1:[1920x1080@150]+)
(0E00000000000000) 2:[2400x1600@200]+[1920x1080@150] (redirected to 1:[2400x1600@200]+)
(0D100302B98FE4E1) 1:[2400x1600@200]
(0D0000028DD0B1BD) 1:[1920x1080@100]+

Hope this resolves and ty again!

Reply #14 Top

Hi jsimon,

Just following up to see if the test build at https://www.dropbox.com/scl/fi/fxrz303c0dj3raitexubh/UpdatePatcher_Debug_2025_10_14__4_53_40_am.exe?rlkey=p0iiy402y39t8qeatczv9dmgo&dl=1 was able to resolve the issue. (Details above)

In either case, looking forward to getting the bottom of this, and moreover, hoping issue is resolved! Thanks for letting us know.