|
MinimWatch Runtime Exception
|
|
31-05-2016, 11:42
Post: #15
|
|||
|
|||
|
RE: MinimWatch Runtime Exception
Problem now identified though not completely fixed. Even this would not have been possible without your help, and the process of elimination arising therefrom.
The points you mention certainly needed checking. AFAIK, the Windows 10 setups (including networking) on the two machines are identical; that is certainly the intention. What is obviously different is the security software - Kaspersky on the main machine and AVG on the secondary. So, given your advice from the logs about what was happening (a communications failure between MinimServer and MinimWatch), Kaspersky was the obvious place to start. Temporarily disabling Kaspersky re-enabled the Windows firewall, which immediately required me to allow Java/MinimWatch. With that done, the rescan ran normally. With Kaspersky re-enabled, the rescan failed again, as before. Unfortunately, Kaspersky, which is a complex application and has a lot of settings, was creating this blockage silently, and it was not immediately clear where the problem lay. Eventually, going through Kaspersky Settings > Application Control > Manage applications, I found the Minimwatch installer listed in the 'Low Restricted' (Yellow) section of the table. Moving it (by right-clicking and selecting) to the 'Trusted' (Green) section temporarily removed the blockage and fixed the problem. Unfortunately, it has now returned. Clearly, I need to work through the Kaspersky settings and (if I can find them) logs. I shall report further. David |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 3 Guest(s)

Search
Member List
Calendar
Help



