Based on their blog posts about Fences v5 being made "ready for Windows 11 24H2", I suspect that earlier versions will no longer work with 24H2. It also wouldn't surprise me if they're building planned obsolescence into their products now.
I have a fresh clean install of Windows 11 24H2 and I am attaching a screenshot of how my desktop looks (with fences 4) every morning when I wake up.
For context,
I have Fences 4 (latest version)
My desktop is 3840x2160 at 120hz with "Scale" at 200%.
Feel free to ask any questions you may have.
I have an update on the situation that I posted in my original post (referenced above).
I've been trying to troubleshoot the issue ever since I made that post, and this afternoon I made a significant breakthrough.
Turns out, my TV is (mostly) the cause of the bug.
I use my TV as my PC desktop monitor.
My TV is:
(From BestBuy receipt)
Samsung - 55" Class QN90A Neo QLED 4K UHD Smart Tizen TV
After my TV has been turned off for 16 or more seconds, once it's turned back on, the bug will occur. The problem is this bug doesn't happen with my TV on previous versions of Windows 11. (Basically, any version prior to 24H2)
After I discovered this, I tested every possible thing I could. I tried every type of power combination (wall, surge, & battery backup) for my TV, and multiple HDMI cables. Nothing had any effect with Fences 4 on Win 11 24H2.
Finally, I tried uninstalling Fences 4, rebooting my PC, installing a free 30-day trial of Fences 5, and rebooting again, to see if Fences 5 would fix it.
The results? It's kind of fixed now.
The bug still occurs but now it's automatically corrected after a few seconds instead of my desktop being left in a complete cramped mess for eternity until I load a previously saved loadout.
So, basically, instead of being 100% fixed, it now just corrects itself each time. I don't know what was added or changed with 24H2 that's allowing this to happen, but Fences 5 is basically the only successful workaround I've found.
Thanks to everything I've mentioned above, I now know that this is definitely a bug/problem with Windows 24H2 that effects both Fences 4 and to some degree, Fences 5.
This is why I say this is a 24H2 problem:
Before I did my clean install of Windows 11 24H2, I had Windows 11 23H2. I was having some software problems at the time and knew that I needed to do a clean install at some point since my OS install (at that time) was over 3 years old. However, even with those problems, I still had no issues with Fences 4 up to that point.
After 24H2 had been out for a short bit, I decided it was time for a clean install of windows using 24H2 as the base. After the install was complete, I installed Fences 4 and almost immediately started encountering this bug right away.
So, you see, this bug never occurred until after I was on 24H2. With a clean install no less.
Anyhow, that's my report. Just thought I'd keep everyone updated.