Fences causes constant desktop crashes / repaints on Win10

from Stardock Forums

Hi - I have Fences 3.09 installed on my Win10x64 PC.

I am having a Fences usability issue where Fences causes my Win10 desktop screen to constantly crash and repaint. Almost anything may cause a Win10 "Busy" cursor to suddenly appear when doing something minor on my desktop, such as moving an icon or doing a right-click for a context menu. Once the "busy" cursor appears, it won't clear until I do a left-click on my mouse. After I do the left-click, the entire desktop will white-out and clear momentarily (even clearing out the taskbar), and then the screen will repaint and reload to show my normal desktop. 

This looks exactly like what happens when the last instance of explorer.exe crashes in Win10, and explorer.exe auto-restarts.

I have fully uninstalled and reinstalled Fences, but it doesn't fix this problem. I have seen this occurring for a while now.

Is there a solution?

AzJazz

fences
19,393 views 19 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Need more information.

1) Windows version. Please use Winver.exe for full Windows 10 version numbers.

2) Fences version.

3) Is Forcepoint / Websense cybersecutiry running in the background?

Thanks

Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top
  1. Windows Version: 10.0.17134.1365
  2. Fences Version: 3.09.11
  3. No, I am not running Forcepoint or Websense
Curtains - Customize Windows with additional styles
Reply #3 from Stardock Forums Top

Please try the purge and reinstall steps as mentioned here : https://forums.stardock.com/486084/fences-support-faq#reinstalling

Just make sure to re-download the latest version from your account. Reboot after the purge. Reinstall using the latest version you just downloaded. Reboot after the installation. Retest and report back.

Thanks

Basj,
Stardock Community Assistant.

Reply #4 from Stardock Forums Top

Hi, Basj - I did the Fences purge and reinstalled. It didn't help at all.


AzJazz

Reply #6 from Stardock Forums Top

Quoting AzDude, reply 5

Hello ,

Would you Please do a Clean Boot: https://forums.stardock.com/486084/fences-support-faq#cleanboot

test and report back .


AzDude
Stardock Community Assistant
End of AzDude's quote

Hi, AzDude - Unfortunately, I can't do that. Fences is running on my work PC, and I don't have the capability to add any users.

I have noticed that my CPU and / or GPU are getting hit hard while using Fences. I can hear my cooling fan turn "on" at the maximum while the Fences issue is occurring.

AzJazz

Reply #7 from WinCustomize Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

 

AzDude
Stardock Community Assistant

Reply #9 from Stardock Forums Top

Please try the following:

-For Win8/10 Users: Open the Start Screen, and type 'cmd'. Right-click on the search result and select 'Run as administrator' from below.

-Type: sfc /scannow

-Wait for the scan to complete (this can take several minutes)

Some help on how this looks should you need it:

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

If the SFC finds errors, but cannot fix them, please also run the following command in the same command prompt window:

dism.exe /online /Cleanup-Image /RestoreHealth

Some help on how this looks should you need it:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

The above command should assist with replacing any damaged or problematic system files. Please note, however, since it may require restoring certain files, this process can take some time and you will need to be patient until it has completed.

Please let me know whether this resolves your problem or if you have any additional questions.

Thank you,

Basj
Stardock Community Assistant.

Reply #10 from WinCustomize Forums Top

Quoting AzJazz1, reply 6

Hi, AzDude - Unfortunately, I can't do that. Fences is running on my work PC, and I don't have the capability to add any users.
End of AzJazz1's quote

That is - your corp environment- where we see this issue most often.  While you note that you are not running ForcePoint / Websense, have you confirmed that this is the case with your IT people?

Sean Drohan
Stardock Support Manager

Reply #11 from Stardock Forums Top

@basj - I ran sfc /scannow, and it had no effect on the Fences problem.

@sdRohan - I talked to my IT dept. and they said, "WHAT do you have on your work PC?!??!? We're removing your admin rights immediately!!!" 8C  

So actually, I didn't ask my IT department about ForcePoint / Websense. However, I couldn't find anything in my Win10 Registry for Forcepoint or Websense, and I didn't find any of the Forcepoint executables, libraries, or services (such as, C:\Windows\System32\drivers\cwnep.sys or C:\Windows\System32\QIPCAP64.dll) on the PC or running in Task Manager. I think it's pretty safe to assume that Forcepoint / Websense isn't installed on the PC.

Reply #12 from Stardock Forums Top

May I know what kind of security software you have installed in your system.

Thank you,

Basj
Stardock Community Assistant.

Reply #13 from Stardock Forums Top

Hi, Basj - We have Windows Defender and McAfee Endpoint Security installed.

Reply #14 from Stardock Forums Top

Personally, I do think there is something blocking Fences from doing its job. And the only way that I know to iron it out is doing a cleanboot, as suggested before, and see which one of your background application is conflicting with Fences. I do believe that we can only move forward after that is done. There is possibilities that Mcafee endpoint and Forcepoint endpoint work in a very similar way.

Thank you,

Basj
Stardock Community Assistant.

 

Reply #15 from Stardock Forums Top

Are there any logs I can provide instead? There isn't any chance of a clean boot, since I can't create a new user on my PC.

On top of that, even if I could - The antivirus and other security related apps are automatically installed and controlled by my IT dept, so they would be active if I created a new user, too. I have seen them getting installed on lab PCs where new users are activated on the lab PCs.

Reply #16 from Stardock Forums Top

Hello,
I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #17 from Stardock Forums Top

Running sfc /scannow was a terrible idea, and should not be recommended to future customers except to fix existing BSODs. I wasn't thrilled with doing that when you initially recommended it (it is a "sledgehammer" type of repair), and now I am paying a big price.

My system has now been experiencing multiple spontaneous Win10 BSODs every day since running the sfc /scannow, and I am trying to get my system operational again. Apparently the system file check has corrupted the operation of a number of my previously installed device drivers (due to some files not being accessible to replace), and I am trying to get the right drivers reinstalled. Unfortunately, I see BSOD crashes just by opening Windows Explorer, so this has been challenging.

You should not be recommending the sfc "fix" unless the customer is already seeing BSODs. The System File Check can cause new BSODs, so this is not a good recommendation.

Reply #18 from Stardock Forums Top

Hello,

That is strange, from what I know, sfc /scannow has never introduce more problem into client system. From what I read, sfc /scannow suppose just to find and replace corrupted files, not the other-way around.

I have suggested sfc /scannow a lot of times, so far most will come back with no issue found, some come back with some corrupted files found and replaced. But, as far as I remember, none come back, it make my pc worst.

And after more reading, if sfc /scannow failed, it usually mean that there are hardware Driver corruption, Hardware failure or sign of beginning of failure. But, I guess, there are always unique cases.

Thank You,
Basj
Stardock Community Assistant.

Reply #19 from Stardock Forums Top

Quoting AzJazz1, reply 17

You should not be recommending the sfc "fix" unless the customer is already seeing BSODs. The System File Check can cause new BSODs, so this is not a good recommendation.
End of AzJazz1's quote

I am afraid that is just not so... If you are getting BSODs from a sfc scan, the PC had underlying issues to begin with.  SFC is recommended by MS themselves for any number of issues, not just BSOD.

That said, and more germane to the issue, can you ask your IT people if they have deployed \ enabled anything related to:

Windows Defender Exploit Guard
https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/create-deploy-exploit-guard-policy
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/enable-exploit-protection
https://www.thewindowsclub.com/windows-defender-exploit-guard

Sean Drohan
Stardock Support Manager