Jump to content

arbrich

Members
  • Content Count

    69
  • Joined

  • Last visited

About arbrich

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Happening to me as well - Blocks all over the place - something is wrong !!!
  2. Here are 2 captures: Cap1 is The controller running and then failing and I stopped the capture Cap2 is after the Controller has failed. The Client PC is 192.168.1.244 where the controller is running. captures.zip
  3. I excluded everyhting I could see running including Unify.exe, mongod.exe, java.exe, javaw.exe and javaws.exe with no luck. Can you guide me on Wireshark at all ?? - I did download and install it.
  4. I assume I should Exclude the java applications as well since this runs through java ?
  5. Just an update that the Controller continued to run normally overnight with only the Web Protection turned off. So we just need to figure out what exception to put in to keep it running and allow me to keep web protection on. Thanks
  6. Here are the logs. I ran this while the Unify Controller was running and it had not failed yet. Again the goal is to determine what Exclusions I need to put in so the Controller will not shut down. If I turn OFF Web Protection and Exploit Protection the Controller will continue to run normally. I was able to keep the Controller Running when I just turned of Web Protection today. mbst-grab-results.zip
  7. Running Malwarebytes and it causes Unify Controller to stop. I have tried turning the Java Protection Off with no luck as well as setup exclusions for The entire Ubiquiti UniFi folder and for the ace.exe that runs the controller. Running on Windows 10 1809 If I turn off Malwarebytes exploit and web protection, Controller will run fine. I am looking for some way to put in Exclusions or change malware settings to allow the controller to run without stopping.
  8. I have seen this behavior as well on Windows 7 machines with RAID1 arrays where drives go offline.
  9. Just had another Windows 7 machine that had not shown any issue do the same thing when clicking on Devices and Printers lock up instantly.
  10. Just trying to add more data to help this along. We had 3 different machines today (all Windows 7) that as soon as you clicked on Devices and Printers the machines froze up right away and had to be restarted. This is the 4th machine I have seen do exactly this same thing. We are rolling back to Prior Component Update until this gets resolved.
  11. Just had 3 more customers tell me that they have been freezing intermittently but did not think much about it until it repeated a few times which they let em know today. There are a lot more people out there having these issues then you think. They are just not reporting it here yet. I am actively rolling everyone reporting lock ups back to CU 1.0.482. Thanks for your continued support on this.
  12. I am willing to help with this as soon as possible - Need to get to the bottom of this. Thanks
  13. Latest update - since I cannot get KB4471318 uninstalled - "it is stuck" I am going to roll back to older MBAM component version before 1.0.508 and see if it locks up. Will report back
  14. Update - I went and looked and I do not have KB44713187 showing as installed on this system or needing to be installed. This appears to be a typo from above and should be KB4471318 which is the Windows December (2012-12) Security and Quality Roll up.
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.