With the Fences 3.10 release, we are creating this thread so that users can report any observed issues.
Obtaining Fences 3.10
Object Desktop members can get the release from within Object Desktop Manager
Individual purchases (as well as Object Desktop Members) can also be obtained from your account page: https://store.stardock.com/myaccount/products
For guest check-out purchase (no account), from this link: http://www.stardock.com/support/productkeyretrieval
Reporting an issue
Please include the following for anything found:
Thank you for your interest and any time you put into making Fences a better product.
Sean DrohanStardock Support Manager
We very much are working on it, yes.
Yes this fixed the problem,,,,,,,,,,,,,,,,thanks
Please add the release date for every releases on page https://www.stardock.com/products/fences/history
After updating I had the explorer error, removing an edge website shortcut fixed the issue, unfortunately I'm left with another issue, there are now no context menu entries for fences.
I responded to the Stardock email sent to me this morning advising that Fences 3.1 was available for download by clicking the 'download now' button in the message body.
A download was provided, installed and a reboot requested. However, what transpired as a result of the reboot was a Windows 'blue screen' suggesting that I should quote the windows stop code 0xc000021a to any engineer that turned up to fix the issue.
I'm not an expert but after finding a way (internet research) to revert my computer to a previous restore point, Windows finally (1hour later) rebooted to the desktop. All my Icons were present in a jumbled up order and a fences message that said
"Fences has detected that Explorer was not closed properly, as a precaution Fences has been temporarily disabled. To re-enabled Fences, right click your desktop and choose "Enable Fences".
My experience with right clicking was a few screen flashes, my Fences boxes appearing empty of icons and then flashing again to reveal the previous jumbled icon screen and the same 'Explorer not closed' message. However, at least my computer was working again and I could get on with some work!
Later in the day I tried re-installing Fences 3.1 and the same happened. I also attempted various suggestions from this and other Stardock forums - waiting in trepidation every time a reboot was required. From this forum I tried the purge and re-install - same again. so finally (2 hrs of attempts later) I followed the instructions to download 3.09 shown above - and what do you know, everything was returned to 'normal'. The reboot went smoothly and Fences worked perfectly with all my icons in their correct boxes as before.
As I've already said I'm not any kind of expert, I don't even know what Display Fusion and Wallpaper Engine are ( and I don't really want to know). Like many of your customers I just would like an update from Stardock to:
1. Improve the way Fences works (do what it says on the tin or email)
2. Install without any issues (after all, I think mine is a regular pc, if a bit on the old side!)
3. Not to attempt to destroy Windows and therefore access to all my computer files
4. Not engage me in 3 hours of my life to return to the same computer/Fences configuration that I had yesterday!
From the comments of others in this forum I conclude that Fences 3.1 is not fit for release and that extensive work needs to be undertaken to solve the problems indicated. Personally I think I'll stick with v3.09 as I know it works and does not result in a Windows 'blue screen' (I hope!)
System information - to assist:
My computer is a personally owned (not corporate) Dell XPS 8500 x 64 running Windows 10 Home version 10.0.19042 with a Dell A12 Bios.
I'm not a regular in this forum and hopefully won't have need to return so any 'solutions' you have will probably not be implemented. However, I do hope that version 3.11, when it is released, perhaps after extensive testing this time, will work as advertised.
Regards
TGN (just a regular customer and Fences user)
How do i roll back my fences version since my WPE doesnt work anymore?
never mind rolling back to 3.09
Hello,
Sorry to hear you are having trouble.
Please see:
https://forums.stardock.com/505007/get;3806834
Sorry for the frustration.
Is there a setting that can be applied to prevent future updates? We are a larger enterprise customer and explorer issue caused major problems in our organization.
We're happy to apply updates as they are provided but would rather have control over the process.
I feel sorry for people who installed 3.10 without reading this thread.
Lots of people having problems. (Has anybody reported smooth sailing? They're usually quieter!)
Support said they'd add a legit downgrade link to the changelog, but it's still not there. https://www.stardock.com/products/fences/history
Support's lazy "see here [link]" responses. ...You're not an unpaid Reddit moderator, your job is to support this software we've paid for. Please act a little more like you care.
No way in hell I'm 'upgrading' to 3.10.
Waiting for 3.10.1 or 3.11 or whatever :/
v3.12 worked for me as well - thank you.
It is in the top of this thread:
Believe me, we understand your frustration (we share it) but nothing about this was 'lazy' I assure you. Fences 3.10 was in beta (SD side) for months with relatively few issues reported and the ones that were like we are seeing now, we could not get many to hang with it to resolve them:
We were able to fix the crash issue but not the WPE one just yet. Even if we could have, releasing on a Friday in software is a no no.
That all said, we apologize for the frustration this has caused.
I now see the version 3.09 download in my account.
I currently have version 3.1.05 installed.
What is the correct process to do the downgrade?
Do I need to uninstall version 3.1.05 before downgrading?
If so what is the best way to do that? Use the purge batch file posted, uninstall thru Object Desktop, or thru Windows Programs & Features?
Your help would be appreciated.
Thanks
Hello! The background of my desktop has gone white with a strange shine, I have tried to uninstall it and reinstall it and it does not fix. The problem is Fences, when I uninstall it, the colors work fine again. Everything has happened since the last update.
https://i.imgur.com/Hc3dU3o.png
Sorry, I originally posted this as its own thread, then saw you had already created this thread for 3.10 update issues. So I've pasted my problem below:
I was prompted to update my Fences to the new 3.10. After updating, I rebooted my computer and Fences didn't autoload. When I right click on my desktop and select Enable Fences, nothing happens. I can select Stardock/Fences from the Start menu and see all of the configuration options and my saved icon sets, so everything appears to be installed, but Fences won't populate my desktop.
I've run Fences for several years now, without difficulty. My Windows 10 is Professional, I have an Intel I-9 processor, 64GB of RAM, and a 2080Ti graphic card. Windows OS build: 19041.985, Windows Feature Experience Pack 120.2212.2020.0
I deeply appreciate any help as everything I do runs through Fences' desktop icons.
Maybe I lucked out.
The installer would not let me change the install location to where I had the previous version installed.
It installed in the default location so I am still using the previous version.
Every time I reboot my PC, I get the same error message:
Fences has detected that Explorer was not closed properly. As a precaution Fences has been temporarily disabled. To re-enable Fences, right click your desktop and choose “Enable Fences”.
After I re-enable Fences, my Zone Alarm icon never appears in the System Tray, although the program is actually running. My automatic file backup program SyncBack SE is running in the background but also does not load the icon in the System tray. SyncBack must be launched using the system tray icon, so this is a MAJOR problem. After every reboot I have to open the Taskbar settings and re-enable the SyncBack icon.
There may be a conflict between version 3.105 of Fences and SyncBack. There were no issues prior to this Fences update.
I am running Windows 10 version 21H1with OS Build 19041.1110. I am also running ZoneAlarm Pro version 15.8.125.18466 and SyncBack SE version 9.5.22.0 (64 bit).
I am NOT using Groupy. I am NOT using Wallpaper Engine.
I would rather re-install Fences version 3.09 and deal with the upgrade reminders than put up with the problems this new version is causing.
Just a quick question.
I got your mail where it says that Fences 3.1 is avaiable, but when I use your download link within the mail, it directs me to 3.09.
Do I need to buy 3.1? I'm under the impression that I'm able to upgrade to 3.1 free of charge.
Fixed it for me.
But ran the Updates Checks script to opt out of future updates.
After update to V. 3.1.0.5 all my fences are gone and won't come back.
When I try to load a snapshot it also doesn't work.
Have WIN10 Pro 20H2 build 19042.1110
Sorry to hear you are having issues.
See this updated post https://forums.stardock.com/505007/page/1/#3806834
Thank you,
Basj,Stardock Community Assistant
From what I know the crash issues is resolved. As mentioned here : https://forums.stardock.com/505007/get;3806834. The Dev also mentioned to have a fix for Wallpaper Engine and currently testing it. Your patience is highly appreciated.
I hope Wallpaper Engine is fixed soon.
Just to pass along my experience; got the email, downloaded the update and applied it, and (somewhat crucially) didn't immediately restart because reasons (was watching TFaWS and didn't want to interrupt the episode further with a restart).
Sleep...
Turned on my computer this morning - no fences (like lots of you), so tried enabling - nothing (not even the Explorer dialog), go into the management app, notice that it's not seeing my activation code, so signed up for an account and got my activation code, then applied it. A quick restart and everything is back as I would have expected.
If this is a requirement (I don't know, it's what happened to me and it's "one-off" as far as I am concerned), would have been nice if it had been part of the "installation documentation", but hey ho. (Not saying this is "the solution", just what happened to me. YMMV.)
Thank you murray_crane it worked for me too.
There are many great features available to you once you register, including:
Sign in or Create Account
