sdRohan sdRohan

Fences 3.10 Beta Issue Report Thead

Fences 3.10 Beta Issue Report Thead

 
314,864 views 115 replies
Reply #76 Top

Quoting basj, reply 71


Quoting MMonsen,

I gave up on Fences a couple of years ago due to a bug that causes two UAC prompts to pop up every time I boot my computer. If I deny them both, Fences still seems to run OK. Maybe there is functionality that is missing because I deny them. If there is, I haven't noticed.

Anyway, I installed the Fences 3.1 beta hoping that this issue was resolved, but unfortunately it was not. It would be really nice if this could be fixed.

I have tried using the "purge_fences.bat" file as detailed in this post, but it did not help.

I really love the functionality that Fences provides, but this UAC prompt issue has forced me to live without it.



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.

Reply #77 Top

Quoting sdRohan, reply 72


Quoting MMonsen,

Anyway, I installed the Fences 3.1 beta hoping that this issue was resolved, but unfortunately it was not. It would be really nice if this could be fixed.



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 Drohan
Stardock 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.

Reply #78 Top

Quoting MMonsen, reply 76

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.

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 Drohan
Stardock Support Manager

Reply #79 Top

Quoting sdRohan, reply 78


Quoting MMonsen,

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.



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 Drohan
Stardock 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.

Reply #80 Top

Quoting MMonsen, reply 79

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

Sean Drohan
Stardock Support Manager

Reply #82 Top

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.

 

Reply #83 Top

Quoting frankschoenberg, reply 82

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

Reply #84 Top

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.

Reply #85 Top

Quoting frankschoenberg, reply 84

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?

Thank you,

Basj,
Stardock Community Assistant

Reply #86 Top

Quoting nagy4536, reply 13






 

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!

Reply #87 Top

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

Reply #88 Top

Quoting Andrey7, reply 63

Stardock Fences 3.1.0.5 running W10x64 always does if I save a new file to the Desktop:

      

Can you fix this to have new icons being places outside fences rather than behind, please?

Any updates on this issue?

Reply #89 Top

Quoting wedward2, reply 87

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

 

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.

Reply #90 Top

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

 

Reply #92 Top

Quoting sintemal, reply 91

The almost known "touchpad" bug is still there with teh beta version.

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.

Sean Drohan
Stardock Support Manager

Reply #93 Top

Quoting wedward2, reply 90

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

Go here:

C:\ProgramData\Stardock\Fences3

Delete the license.sig and reactivate

Sean Drohan
Stardock Support Manager

Reply #94 Top

Quoting sintemal, reply 86

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.

The something is wrong \ running on that profile that is killing Fences.  If I had to guess, it is annother Windows Shell app.

Sean Drohan
Stardock Support Manager

Reply #95 Top

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.

Reply #96 Top

Quoting sdRohan, reply 94


Quoting sintemal,

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.



The something is wrong \ running on that profile that is killing Fences.  If I had to guess, it is annother Windows Shell app.

Sean Drohan
Stardock Support Manager

 

What would be another "windows shell app" e.g.?

best regards!

Reply #97 Top

Quoting sintemal, reply 96

What would be another "windows shell app" e.g.?

The list would be endless. Generally, it would be items listed in a right-click context:

Sean Drohan
Stardock Support Manager

+1 Loading…
Reply #98 Top

Quoting sdRohan, reply 97


Quoting sintemal,

What would be another "windows shell app" e.g.?



The list would be endless. Generally, it would be items listed in a right-click context:



Sean Drohan
Stardock Support Manager

 

My system is really vanilla in this case/menu.

Do you think you will release a tinytool to detect what crashes?

 

Reply #99 Top

Quoting sintemal, reply 98

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

Sean Drohan
Stardock Support Manager

Reply #100 Top

Quoting sdRohan, reply 99


Quoting sintemal,

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

Sean Drohan
Stardock 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!