Fences not working with Windows 10 Insider Preview 14915.rs

 MS update my Windows 10 to new evaluation copy: Build 14915.rs_prerelease.160826-1902 since I on the fast ring.  Now Fences will not running because of error telling me "Windows Explorer don't shutdown correctly.  Go to my desktop and click on restart Fences"  When I click on restart Fences then my system starts to lockup and couple minutes later I get my OS back but still no Fences.  I tried to reload Fences and again no working Fences.  Right now my Fences are turn off until Stardock fixes the bug in Fences to work with new release.

179,480 views 89 replies +3 Loading…
Reply #1 Top

We are aware of this and will be looking into it.

Insider builds are a mixed blessing.  :)

Reply #2 Top

Quoting ZubaZ, reply 1

Insider builds are a mixed blessing.
End of ZubaZ's quote

More like a half-baked curse. :-"

Reply #3 Top

I get the same message on one PC with this new build and another ran through the upgrade just fine.  Very odd.

Reply #4 Top

Quoting psalibello, reply 3

I get the same message on one PC with this new build and another ran through the upgrade just fine.  Very odd.
End of psalibello's quote

Chances are your upgraded version of Windows 10 has not upgraded to the particular Windows build which is having the problem.  Does it say Build 14915 on the desktop?

Reply #5 Top

I also have this problem, I've tried doing reinstall driver nvidia and remove antivirus 360 total security but no one works

Reply #6 Top

 I`m a Chinese User, I just buy Fences 3 in this day..

AND, 14915..insider...

It`s couldn`t work at all.

So ,how to let it work again..

 

sorry for my English...

Reply #7 Top

Any update on this? I know it is a holiday weekend but we are working and not having Fences working is significantly affecting productivity.

I depend on Fences. Is that poorly placed?

Reply #8 Top

Quoting Parisi, reply 7

Any update on this? I know it is a holiday weekend but we are working and not having Fences working is significantly affecting productivity.

I depend on Fences. Is that poorly placed?
End of Parisi's quote

The use of Insider builds of Windows is not recommended by Microsoft for production systems.

I am afraid there will be no updates until next week at the earliest.  I am not aware of the cause myself, but it is entirely possible the problem is on the Microsoft side in which case you would have to wait for them to resolve the issue with an update.

Reply #9 Top

Just an FYI:  I also have build 14915.rs and I am also having this same problem.  I miss my fences!! X(

Reply #14 Top

Best solution today is to rollback to a previous version of Windows.  Do this by: Win+I, click on Update & Security, click on Recovery, then click on Get Started under "Go back to an earlier build"

Reply #15 Top

Yeah, I can confirm that rolling back does fix the problem. At the moment explorer just crashes and Fences throws up some errors. Sadly, developers are playing constant catch up when it comes to insider builds. It's crossing your fingers and hoping they don't break something. Then it's trying to figure out what changed and how you work around that without forcing all customers to uninstall builds. Throw in the automatic updates and it's incredibly irritating. 

Settings > Updates and Security > Recovery > Go back to an earlier build.

Cheers for your hard work guys. :)

 

 

Reply #16 Top

The solution is as follows and it it is a royal PIA!

Use an uninstaller like Revo Pro (the only one I have tested it on)

Completely uninstall Fences 3 and use the scanning function to remove all registry and other entries.

Reinstall Fences 3

Select the option for letting Fences 3 automatically build the fences.

Fences 3 now works, but NOT with your old setup. It requires you to reconfigure.

Yes, this is a pain, but if you absolutely must have Fences, this is the only way I have found to fix it.

I am going to try and find the place where the previous snapshots are, save them and then restore using that snapshot. I will let everyone know if I am successful.

I have found that Stardock is slow in fixing problems.

 

Reply #17 Top

Quoting alkolkin, reply 16

The solution is as follows and it it is a royal PIA!

Use an uninstaller like Revo Pro (the only one I have tested it on)

Completely uninstall Fences 3 and use the scanning function to remove all registry and other entries.

Reinstall Fences 3

Select the option for letting Fences 3 automatically build the fences.

Fences 3 now works, but NOT with your old setup. It requires you to reconfigure.

Yes, this is a pain, but if you absolutely must have Fences, this is the only way I have found to fix it.

I am going to try and find the place where the previous snapshots are, save them and then restore using that snapshot. I will let everyone know if I am successful.

I have found that Stardock is slow in fixing problems.

 
End of alkolkin's quote
I have spent 1.5 hours trying to figure out how to use the backup of snapshots for restoring when Fences fails according to my previous post, but nothing works. Since the clean uninstall erases everything, I first made a copy of the Fences folder and then tried using the appropriate snapshot to install into the location specified in the registry. Nothing changed and it did not show up.

I tried registry changes, restartaing and everything I could find. I just went about the process i described of a clean uninstall, and a reinstall using the automatic setup and then rearranged and reconfigured to my desire.

I wish that there was far better documentation of how all this works, but then them may be afraid of theft.

Very frustrating.

Reply #18 Top

I don't see how they're being slow? It was an insider release.

Nobody should be expecting stability for anything.

Reply #19 Top

Notice, I did not say that Stardock would be slow on THIS problem. There are bugs that many have submitted including ones that I have submitted. Though this one is MS Preview has caused, in general I hold fast to the idea that Stardock has been slow to fix bugs.

I still like, use and my clients use the products based on my counsel

Quoting TiredDeveloper, reply 18

don't see how they're being slow? It was an insider release.

Nobody should be expecting stability for anything.
End of TiredDeveloper's quote
, but the documentation of the product and speed of bug fixing is slow to materialize.

For example; the latest version lets you organize the Start10 in the same way that your Fences are organized. I have been unable after a lot of effort, to figure out how this works or if it indeed does. I could find nothing in the documentation.

If you are a Stardock developer, do not be defensive. I like your products but attention has to be give to those bugs submitted by your user base in an open way. Tell us what you have fixed and what you have not. document, document, document.

Reply #20 Top

Quoting alkolkin, reply 19

Notice, I did not say that Stardock would be slow on THIS problem. There are bugs that many have submitted including ones that I have submitted. Though this one is MS Preview has caused, in general I hold fast to the idea that Stardock has been slow to fix bugs.

I still like, use and my clients use the products based on my counsel

Quoting TiredDeveloper,

don't see how they're being slow? It was an insider release.

Nobody should be expecting stability for anything.

, but the documentation of the product and speed of bug fixing is slow to materialize.

For example; the latest version lets you organize the Start10 in the same way that your Fences are organized. I have been unable after a lot of effort, to figure out how this works or if it indeed does. I could find nothing in the documentation.

If you are a Stardock developer, do not be defensive. I like your products but attention has to be give to those bugs submitted by your user base in an open way. Tell us what you have fixed and what you have not. document, document, document.

End of alkolkin's quote

You need to do nothing to make it work in Start10.

The Fences appear in the all programs list automatically.  Should you wish to disable them you can do so by disabling the option to show the Desktop icons in the All programs list in Start10.

Reply #21 Top

Thank you for responding. I appreciate it.

Try right clicking on one in all programs to bring the folder over to Start10, to pin on Task bar, or any of the other right click functions. On my computer there is no response to the right click.

Though I thank you for that guidance, is it somewhere in the documentation? Please explain how to put it on the right side of the Start10 menu.

I grant you that this new feature has promise, but to "feature" it as an important update is an exaggeration in my opinion. It could become so, but it is not now.

Reply #22 Top

Quoting alkolkin, reply 21

Try right clicking on one in all programs to bring the folder over to Start10, to pin on Task bar, or any of the other right click functions. On my computer there is no response to the right click.

Though I thank you for that guidance, is it somewhere in the documentation? Please explain how to put it on the right side of the Start10 menu.
End of alkolkin's quote

Fences are only available in the All Programs area

Reply #23 Top

I noticed "Fences" folders appear in the "All Programs" menu with a "Fences" icon instead of the standard folder icon.

Reply #24 Top

I even tried running it in Windows 8 compatibility mode but no luck.

Reply #25 Top

1) I started fences.exe (the config app) and set layout option to 'Don't preserve my desktop layout and disabled Desktop Pages.

2) Clicked perform automatic layout (and took a snapshot), Closed the fences app.

3) Then just emptying the %appdata%\Stardock\Fences folder did it for me.

4) Restarting fences (re-enabled all disabled in step 1) and had my old layout once more. Not sure if the things under 1) where actually necessary.

 

So it seems a kind of access right problem as the log contained quite some lines like

00010683X - ACTIVATION PROBLEM - unable to read SAS License file.

1B5BBC3CX - FencesUI Start - /fixpermissions
1B5BBD17X - FencesUI End   - /fixpermissions
1B5BBE21X - FencesUI End   - /verifyintegrety .

+1 Loading…