![]() ![]() Remember to record down the ticket number for future reference if needed. If that the case you can raise a Support ticket using the link below. Or lots of time user tend to have a typo in the email address when purchasing the product. Might be under your paypal email address, if you was using that payment method. Than it might be you have purchase under different email address. You can check using this guide if you purchase registered under same account as your main account using this guide. I have upgraded to 4 and activated the initial download - but 4 is not shown on the 'My Downloads' page. We thank you very much for your feedback and patience. If you can meet these requirements, please post as much here and I will send out invitations and instructions to you directly. Are willing to stick with the troubleshooting process for (potentially) weeks.Are ok to submit data (startups, running services, sysinfo, etc) upon request.Able to reproduce crashes at will with the latest version of Fences 4 (not Fences 3).English speaking and preferably in the Western Hemisphere (for real-time chat).The requirements for participation would be: To best accomplish this, we are going to set up a Microsoft Teams 'Team' \ Channel and invite clients having this issue to it. That said, we take this very seriously and want to try and triage specific cases to see if there is a common denominator.Īs one would suspect, this cant be done in the forums for a variety of reasons, not the least of which is we need data (startups, running services, sysinfo, etc). We are continuing to look into the crashing reports but we believe the number of users impacted is small at this time. One can do so by downloading and running this registry edit file: To enable it, the Fences registry needs to be changed. To help see if Fences is the cause of any crash, Fences has the capability to capture more data when there are crashes. instructions on how to do this has been posted here: We are now asking for the manual collection of crash dumps. ![]() Specifically for them, we need more data to find the cause. 'Fences has detected that Explorer was not closed properly' If nothing is resolved from it, please proceed with the below.įor some, when enabling Fences, they are seeing: Performed an SFC \ Restore health scan:.Prior to doing any of the below, we ask that you have 1st don't the following. We are seeing that many PC \ OS related issues are clouding the data \ feedback received on this issue. If it is absent, the post will likely be removed. Also, to find said cause, the data asked for above is crucial. ![]() Please uninstall WindowBlinds to see if you still have the issue.Īny post that does not directly contribute to finding the cause will likely be removed. If you are seeing this issue on Windows 11, and have WindowBlinds installed as well, it will very likely crash. If you have DisplayFusion installed, or other 3rd party multimonitor software (Actual Multiple Monitors, UltraMon, etc), please try uninstalling and a reboot. Thanks to help from user altae here, we have confirmed that if DisplayFusion is running, this can cause the issue. Special thanks to k3nny5 for working with us in Teams to help resolve it.Ĭhanged the process for collecting data \ crash dumps in the instructions below. Please see if the just-released beta does indeed resolve it for you and report back here either way, please. We think we might have a fix for one crash that is possible with Fences and folder portals. Should your issues be resolved, there is a substantial discount to upgrade to Fences 4: If you are still using Fences 3 and experiencing crashes, please install the trial for Fences 4 to see if you still see them: Seeing that all known crash issues have been addressed within Fences 4, we are closing this thread. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |