Yes I did without any success, however it's not a solution rather work around provided by Stardock avoiding upgradability bugs fixing
If it works, or does not, how is that a 'work-around'?
Exhausting Customers with annoying work arounds is not a solution of the Issue.
Again, can you point out where we ever cited a 'work-around' as a solution to the very few that are seeing this issue? To be perfectly honest, I wish we did have a work-around for it.
As for the issue at hand, I will try to put it in a way that may be more relatable.
There are 1 million X phones that work flawlessly with Type A battery, but very few don't work with Type B battery. Battery B works fine in other phones. What product has the issue: X phone or battery B? In this example, X Phone is Fences - we need to know what about battery B is causing an issue.
It could be an app, setting, lack of a Windows update, OS / file corruption and about 100 other different things - we just don't know what that is. But because we cannot reproduce it, and there are so many possibilities, we need to find what you all have in common.
Please do not mistake this as being flippant or dismissive - we really do want to solve this for you but it is not from neglect or ineptitude that it has not be solved.
Have you tried the clean boot if you still have the issue after:
https://forums.stardock.com/486084/fences-support-faq#cleanboot
Yes I did, however the Issue still exists
When it does work (not so in your case you said), that usually exposes that it is not Fences as it does two things:
- Is under a new Windows Administrator account
- It eliminates most all non-Windows apps and services (but not all)
People usually skip one of those (or both) as it can be prohibitive in a corp environment and / or time consuming. If you did both, the only thing I would add to it is to, under the new Admin profile is this - please try the following:
SFC Scan:
-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.
Let me know the results, please.