I have surveillance DVR which I view through Internet Explorer 8. It is dependent on an ActiveX ... which I notice resides at C:Program FilesVideoSystemOCXCtrlOCXCtrl.ocx. I used Firefox for all other browser needs.
I looked into IE and found reference to Webroot, under "Tools, Manage Add-Ons": I disabled four references, to no avail.
I looked into Webroot, and whitelisted here and there... it's confusing... to no avail. What DOES work is to Shut down Protection completely... not what I want.
Please advise. Thank you.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
OK, while I do understand the problem, I do not understand quite where you 'whitelisted' within WSA itself, so I am going to go over all I know and hopefully will not miss anything.
Please let me know if this helps get it working!
Also, as I said go ahead and get a Trouble Ticket filed either way. In the event that a .ocx file is for any reason not able to be locally allowed by the user, Webroot Support may be able to whitelist it globally and that would fix the issue. Obviously being the Easter weekend, response from Support may be slower than usual, and I would not be surprised if they would be inable to before Monday.
Have a Great day...and again thank you for all you do...
Yup, come across them (stands for OLE Control eXtension, BTW). Have checked what you had described in your ealier post and can find nothing that you have missed. In fact I located a .ocx on my system and folllow your instructions and was able to add it successfully under the 'Block/Allow' feature.
Interestingly enough I have occassionally seen this behaviour with other files types. It is rare but unexplained, and what I have found the best thing to do is to reboot and then try again...that usually fixes the issue for me...but have never had the issue or tried to fix it re. a .OCX. But worth a try as I can see no reason as to why a file with that extension cannot be so added/have proved that it can be.
Hope that helps?
I do have one other thought: Do you have the most recent version of the software installed? If not, you might want to install the most recent version. My thinking is simply that the most recent version might not have the same problem, and also even it if does perhaps WSA still catch the file in question and give you a chance to allow it during the install.
I do not have much confidance in that, but it might be worth a try.
I am convinced that the inability to add the .OCX is an intermittent issue with WSA...so do check out whether you can do so after you next reboot. If that clears that issue then yo can progress with the underlying issue of getting your DVR to work with WSA.
Please keep us posted on development/progress...this is of interest to us re. assisting users who may call out this or a similar issue in future.
Have a great Easter.
Though I am now getting a bit....
Try this: Identity Protection gear > Application Protection
Is anything in there under Deny or Monitor?
You may also want to right click on the green W icon, Save a Scan Log, open what you saved, scroll to the end, and see if you see any lines that say "Monitoring." If you do, paste them here.
Welcome to the Community Forums.
Did you try to register the relavant item under the Identity Shield?