brians2

brians2

Joined Last seen Member # 4969968
0 Posts 0 Replies 8,480 Reputation

No problem! Yeah that's why I thought it may have been the background slideshow. I also had Forcepoint and a desktop background slideshow on Windows 7 and there were no problems. But on Windows 7 when you set it for a slideshow with dual monitors both of them will display the same picture at the same time. However on Windows 10 when you do slideshow my left monitor shows a different background picture than my right monitor. So at the time I thought

9 Replies 31,764 Views

I just was upgraded from Windows 7 to Windows 10. Fences works fine as long as my background is set to a single picture, however when I choose to display a Slideshow it crashes with "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". I'm running a dual-monitor setup with the primary monitor on Display Port and the 2nd mo

9 Replies 31,764 Views

[quote who="AuthorGregLundberg" reply="2" id="3737091"] I have this exact same problem. It seems to occur when I change the display theme under personalization to run a slide show of standard windows backgrounds. I have the latest Fences software. I uninstalled and reinstalled Fences. I rebooted the laptop several times. When I disabled the slide show and went back to a single fixed background, the problem stopped. [/quote] The exact same thing happened to me.

12 Replies 32,174 Views

I get the same message too when I choose to select my desktop background to be a Slideshow, rather than just 1 picture. For some reason this screws Fences up on Windows 10. I have a dual desktop display and when I choose to show a Slideshow of images for my desktop background Windows chooses one image for my left monitor and another one for my right monitor. Maybe this screws Fences up? In any case once I go back to a single picture it doesn't crash. <

36 Replies 98,394 Views

Oh yeah, that happened to me too! I forgot to add. I did the old Control-Alt-Delete, then went to Task Manager, then went to the Process tab, found rundll32.exe, clicked End Process. After that I think I was able to delete those file and then run the Purge bat file.

7 Replies 16,346 Views

I think I figured it out! Here's how I fixed the Purge_Fences invalid uninstall control file problem: In C:\Program Files (x86)\Stardock\Fences\ I deleted 1xuninstall.cmd I then deleted this folder: C:\Program Files (x86)\Stardock\Fences\Uninstall I then re-range Purge_Fences.bat. It still gave me an error message, however at the end, Fences was actually removed. Afterward I was then able to install Fences 3.09. </

7 Replies 16,346 Views

Unfortunately purge doesn't seem to work either. After running Purge_Fences.bat (as an Administrator) it gives me "Invalid uninstall control file" Then it immediately goes to an installation setup which implies it never removed the core program. Settings are removed, but not the program itself: <img src="https://cdn.stardock.

7 Replies 16,346 Views

Upgrading from 3.08 to 3.09 I get this message: "The uninstall executable file could not be written out because it is already in use. Close all running uninstalls and click Retry to continue." No other uninstalls are running. I've performed this first thing after a reboot. I can attach the setup Log.txt file if that would be useful. (Notably, the purge doesn't seem to work either. I run the Purge_Fences.bat file as an administrator,

7 Replies 16,346 Views