That leaves a question about what blocked the data gathering. The account is not a limited account, so that can't be the issue. This could be any number of things from a limited user account to a security program to damage caused by numerous other things from data degradation to malware to badly-applied patches (never seen that be the user's fault). Something interfered with a normal Windows function. The script ran, as the framework is there, but the data is not filled. Specifically, the Windows Scripting Engine is normally used to gather a set of information using a VB Script in the log-gathering utility, but this information is utterly missing. (I don't think this is the issue personally, but it's a possibility.) If the second of those works, definitely let us know, as it means that we will want to check on what McAfee is doing and we are doing in response that is causing the issue. 2: Tell McAfee to ignore Webroot files, especially c:windowssystem32wruser.dll. You might find it beneficial to either or both: 1: Clear McAfee off and do a clean install of it (make sure you have your license information for them prior to doing so). The copy of McAfee installed on the system has been updating since 2006 or so. Could also be a non-issue, since I research what the items were. This means there could be damage to the system that could not be rolled back by Webroot because it wa preexisting. There was a threat detected on the initial install of WSA. Didn't look too deeply into them, but on cursory inspection, some stuff jumped out at me. Regardless, I found the logs from October 18th. As a good example, there is an HP WebHelper.dll being injected into IE that is technically comprised of incomplete code (TODO:). Injected DLLs are also not always in addons, mind you. The information I posted is partially generic and generalized information. I am currently in QA, so any work I do on the forums is extracurricular. Before commenting, please read the entire thread. I had also indicated initially that I started IE w/o any addons. Kit, if you took the time to read this, I had submitted all the logs. It wipes all stuff that has been there over the use of IE and takes it back to a state as if you just ran IE for the very first wrote: If you didn' go poking at the guts of IE's advanced settings, then it should be fine and safe. If you have a lot of custom configuration in the Internet settings, then you may not want to perform a reset. In reality, much of it is pretty badly-written.Ī quick contact with support will allow us to check your logs and see if anything like that is the case, or what is going on if not.Įdit: One of the main ideas behind a reset of IE is that it unloads and re-configures all addons and extra stuff that the browser could be loading, so it has a potential to fix things that a lot of other programs can really badly mess up. In a perfect world, code is written in such a way that it handles pico-delays. This indicates that there is likely an addon or injected DLL that is being monitored by Webroot and doesn't deal properly with being watched. For example, it doesn't happen on any system that I have tried it on here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |