With the Fences 3.10 beta release today, we are creating this thread so that users can report any observed issues.
Obtaining the beta:
Object Desktop members can get the beta from within Object Desktop Manager with 'show beta downloads' enabled:
Individual purchases (as well as Object Desktop Members) can also be obtained from your account page:
https://store.stardock.com/myaccount/products
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.
Please refer to this https://forums.stardock.com/453303/get;3457350 and reply back here.Thank you,Basj,Stardock Community Assistant
I am not running Fences "As Administrator". I simply run the installer, reboot, and I get the UAC prompts. I uninstall, and the UAC prompts no longer pop up after I login.
It never was a problem with Fences. Almost every time we see this its because people have Fences to run as admin but should not:Sean DrohanStardock Support Manager
My steps are the following:
1. Install Fences.
2. Reboot when prompted.
3. Log in
4. Get two UAC prompts. Allow or Deny, doesn't seem to affect whether Fences works or not (but I could be mistaken)
5. Look at the properties on Fences.exe, the "Run this program as an administrator" checkbox is NOT checked.
6. Uninstall Fences
7. Reboot
8. When logging in, I no longer get any UAC prompts.
Is there any sort of logging information or other data collection I could do to help? I'd really like to solve this issue.
Do you have Windows 10 Pro? If so, please enable Sandbox.
After, install Fences on that running instance of it... Does it happen there?
Sean DrohanStardock Support Manager
Do you have Windows 10 Pro? If so, please enable Sandbox.After, install Fences on that running instance of it... Does it happen there?Sean DrohanStardock Support Manager
Yes, I'm using Windows 10 Pro.
As far as I can tell, there is no way to reboot a sandbox instance. Rebooting it resets the instance. I did some Google searches to see if there might be a workaround, but didn't find anything.
Yes, I'm using Windows 10 Pro.As far as I can tell, there is no way to reboot a sandbox instance. Rebooting it resets the instance. I did some Google searches to see if there might be a workaround, but didn't find anything.
Have you done a cleanboot with just Fences enabled?
https://forums.stardock.com/486084/fences-support-faq#cleanboot
Sort by | None
I did remove the software and reinstalled 3.09 and the issue was still there that I could not move the fences. The option "Lock fences" was not visible in the 3.09 downgrade. I then did a "Perform automatic layout". I did a reset of the fences, but they still are not manageable
I can draw a new fences frame, but can't enable it.
Have you tried this steps? :https://forums.stardock.com/486084/fences-support-faq#cannotmovefences
Thank you,
Basj,Stardock Community Assistant
Hello, yes i tried this, but it did not help. I removed all Fences references in the registry (HK_CU) i saw and did a restart. When I then started Fences, i got the Initializion screen how to use Fences. From thereon I was able to create and modify my fences again.
So, this is resolve, yes?
To be honest, I have the same issue.
Adid try out the other profile test and fences did work there.
Than I disabled ALL programms and tools in the "autostart" of my main profile.
Everytime with a reboot.
But still the same issue. No fences and this pop-up window.
Dear Sean,
I made a logfile, like you explained and linked here in the forum.
Can I send it to you via pm?
Thanks in advance!
I upgraded my Fences version for the Beta and it's been running fine with no issues, until this week. Now it's telling me that Fences is fixing to expire in 2-days. I've tried activating it (Object Desktop User) using my Userid/Password, but it tells me that it's already in use on another PC. I also have three other licenses for Fences that are used on two other Desktops and my LapTop, but these licenses are all in use.
Is this an issue with the Beta? Do I need to reinstall Fences and get off the Beta?
Thanks!Bill
Any updates on this issue?
Just an idea:
Go to stardock.com.
Log in your account.
Klick on your icon in the right corner.
Go to "my downloads".
"view product keys"
And there you can deactivate all your once used keys and devices.
Best regards.
No luck, For Fences I actually have four licenses; My Home Desktop, two Desktops in my Observatory and my Laptop. My Desktop uses the license from Object Desktop and it's good out thru 2022. But I'm getting a frequent message telling me that Fences will stop working in 1-day. Not sure if this is a problem with the Fences Beta or a license activation issue. I just reinstalled Fences OFF of the Beta and I'll reboot my Desktop in a few minutes and see what happens then.
Bill
By the way...to be honest.....damn improtant!!!!
The almost known "touchpad" bug is still there with teh beta version.
I tried it with my surface. All drivers are up to date.
Any known progress with this issue?
We tried very hard to work on that but it was to no avail. It's not going to get resolved for the few that have reported it.
Go here:
C:\ProgramData\Stardock\Fences3
Delete the license.sig and reactivate
The something is wrong \ running on that profile that is killing Fences. If I had to guess, it is annother Windows Shell app.
I've been Running Fences 3.1.0.5 for a couple weeks now. So far so good.
Windows 10 Enterprise v1809 64-bit, dual monitor setup on a laptop docking station.
The something is wrong \ running on that profile that is killing Fences. If I had to guess, it is annother Windows Shell app.Sean DrohanStardock Support Manager
What would be another "windows shell app" e.g.?
best regards!
The list would be endless. Generally, it would be items listed in a right-click context:
The list would be endless. Generally, it would be items listed in a right-click context:Sean DrohanStardock Support Manager
My system is really vanilla in this case/menu.
Do you think you will release a tinytool to detect what crashes?
Then it's likely a setting difference and perhaps easier to track down if you have not made many. This is a known one that would cause it:
https://forums.stardock.com/502301/page/1/#3792138
Then it's likely a setting difference and perhaps easier to track down if you have not made many. This is a known one that would cause it:https://forums.stardock.com/502301/page/1/#3792138Sean DrohanStardock Support Manager
Thanks Sean for your work!
But my knowledge and research ended up with this:
"Yes, that was to show the exact combination the fixed the issue, which was just doing a custom rule for Explorer.exe and Enabling "Don't use high entropy""
Don´t know how or where to do that to test it.
Any suggestions?
Best regards!
There are many great features available to you once you register, including:
Sign in or Create Account
