I am using beta 3.03, but I still have no luck with this working with the latest Windows Insider preview build 14936.

Same problem for me. Fences 3.03 beta does not work with Insider Preview 14936.

The beta has stopped working with build 14936. Grrrr. It was working. But the start menu was not working. I had to make a new user account, and when logged in with it, I got the did not close properly message, and nothing would make fences work again.

Same problem.  i reverted back to previous Windows build (14931) and works.  I'll standby to see how this is addressed by Stardock by monitoring this string.

Too weird. Some have problems and some do not.

I had no problem once I "fixed" it using Revo Uninstaller Pro and totally eliminated all Fences files and registry entries via the aggressive scan prior to reinstalling.

My wife's computer never had a problem. We are on the same version of Windows Preview. Some of my clients had a problem, some did not.

Now with 14936 I still do not have a problem, my wife does not have a problem, but I installed the 3.03 Beta anyway. Both of our computers still work. None of my clients that had a problem in the past have had a problem since I "fixed" them using their version of Revo Uninstaller Pro. Some are updated to 14936, some not yet.

How the heck do you even begin to analyze the cause????

Works like a charm, thank You very much!

Funny, but not really helpful.

Yes, it only happens on some computers. It is not working on one of my 3 windows machines. I think it is related to the user account somehow, since when I changed it, Fences stopped working.

It would be nice to have some response from Stardock.

I would like to add that we appreciate having feedback on our software with the BETA builds of Windows.  We'd like to fix any problems.  We are aware though that MS is doing things that may be temporary (like the 14915 build that broke Fences last time) and we cannot devote all our resources to fixing a problem that may not be broken in the next build.

"Nothing on earth is forcing you to install the beta versions. It can get rough on the bleeding edge. " -- Kris Kwilas, 'Essays on Mind and Matter'

Used Revo Uninstaller free version in medium mode to remove Fences and then re-installed Fences, did not work. 

Used Revo Uninstaller free version in aggressive mode to remove Fences and then re-installed Fences, did work!

Thanks for the help. 

Thank you Jim. Since I do a lot of trials,  I good not get along without revealing uninstaller pro. I have set the default scan as aggressive and it has never failed me or caused me harm. My very busy,  low Tech clients rely on Fences for portals and screen organization. I only have less busy clients in Windows 10 fast preview and I have learned how to keep all those clients happy as well.  It just takes more time. 

I am very pleased to see that the Stardock team pays attention to these bugs.  I know they cannot always jump, but it would certainly help if they keep us posted. As a matter of fact your failure 😣 with Mexican scan and success with aggressive should help them. 

My 2 cents worth:

If you have had ANY version of Fences installed on your computer PRIOR TO THE WINDOWS UPGRADE that is now causing your problem; all traces of that install must be deleted. Those using 3rd party software to do this are reporting limited results.  I offer these suggestions only because they worked for me.

1) After standard uninstall of FENCES (possibly ALL Stardock products, I don't know, I'm only using Fences)  use whatever method you prefer to do a thorough search and destroy of every entry of STARDOCK FENCES in your registry. (Please be careful, it is hard to imagine a registry entry that includes f.e.n.c.e.s, that ISN'T Stardock, but who knows?)

2) Using Windows Search (or any other reliable search program), scour and delete from your OS drive (probably c:\) all STARDOCK folders/entries . Remember, this will find Fences files as well as any other installed STARDOCK products.

3) Double check these folders for STARDOCK sub-folders: Programs, Programs (x86), Program data, All three APP DATA folders for any and all users.

4) Want to be thorough?  Do it again.

5) Have a Registry cleaner?  Use it.

6) Re-start.

7) Set a system restore point (it's insurance).

8) Download and install a fresh version of Fences...and START FROM SCRATCH.  Do NOT try to use any snapshots you cleverly stored from previous installations.

Good Luck.

Kevin

I used IO Uninstaller and registry cleaner, and still get the "Fences has detected that Explorer was not closed properly" message, and 3.03 does not work on my laptop.

Try using Revo Uninstaller free version in aggressive mode.

Jamesrome,

Just so I'm clear.  I wrote the post directly above yours.  Did you follow those steps before getting the "not closed properly" error?

Kevin

Same thing after using Revo uninstaller Pro in advanced mode. And if cleaning is really the issue, Stardock needs to fix their uninstaller.

It would be interesting to see if that's the issue, wouldn't it?  Do a REVO, then a thorough search (manual is best) and see if STARDOCK shows up anywhere.

I tried that too... I just think the issue is something else since it works on other machines.

So...after a REVO and a thorough search for STARDOCK, you found no STARDOCK (registry, files, folders, app data, etc) but were still prompted, "not closed properly"?

YES!  After a reinstall of the beat and reboot, the screen blinked twice and gives the "not closed properly" message.

1) You say, "reinstall of the beat", don't follow you.

2) The point would be that no install/re-install happen UNLESS there's a thorough purge of all STARDOCK files, first...and each time another install is attempted.

3) Do you have any other STARDOCK products installed?

I had Start10 also installed and using revo pro had no affect on it. 

"Using revo pro had no effect on it."

IT?  Had no effect on WHAT?

No need to answer. I think we're at a dead end here.