LavaJ431

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LavaJ431

  • Rank
    Member
  1. "Everything" is a freeware file and folder name search utility that is renowned for the speed of its searches. It offers the full range of Windows Explorer functions from the right-click context menu for each item in search results. Under Windows XP SP2, as soon as I request Ad-Aware 9-06 to add itself to the context menu for Explorer, the right-click functionality in Everything is lost. Any attempt to right-click immediately causes the application to crash. Removing Ad-aware from the menu immediately fixes the problem. Attached are the text output from WinDbg when running the "!analyze -v" command on a minidump file produced by the crash, which is also attached.
  2. [quote name='CeciliaB' post='126443' date='Apr 28 2011, 03:47 AM']Maybe my memory isn't correct, but didn't you have problems with the original installation of Ad-Aware and did a lot of manual steps to compensate? Then it is possible that something was in the wrong state in 9.0.4 and the program update to 9.0.5 doesn't work.[/quote] You're right about that history, CeciliaB. However, by Monday night I had the adjustments made so that everything--files, registry entries, startup states of drivers and services--matched a clean install of Ad-Aware with default settings in a Windows XP virtual machine with almost nothing else running. The installation was running fine. Even if there had been a problem, the installation of 9.0.5 should not have been affected by them. It should have detected any deficiencies, and corrected them, like it would for a "repair" reinstallation.
  3. Following the update, the normal boot sequence into Windows XP has been disrupted. The desktop wallpaper does not appear until 30 seconds or more after the "Welcome" sound is played. Then, the wallpaper is visible, as is the mouse, but the Start Button, Taskbar, System Tray, and desktop icons do not appear for 4-5 minutes. Thus, the total time before the system is usable has been increased by the sum of these delays. This behavior has persisted through 4 reboots, with the identical problem each time. If you understand how "BootLog XP" works (I do not), it might give you an idea about what is causing this. I downloaded a trial version of the program from the Internet to produce a boot log, in hopes of being able to identify the source of the problem. However, the time it ran during boot, everything was normal. I can only guess that the program perhaps produces something of the same effect that can sometimes appear when a program is started by a debugger, and does not perform as it does when started by Explorer.
  4. [quote name='LavaJ431' post='126391' date='Apr 26 2011, 01:57 PM']However, the "repair" parameter breaks things. When I add that parameter to "update all," Ad-AwareAdmin.exe loads, but does not run properly. The Update progress bar graph does not appear, even to indicate that no updates were found. I hear the Windows "notice" ring, but don't see any popup, or find any visible window indicated in the TaskBar or in the Alt-Tab window. Worse, after running my task with the "repair" parameter, and then deleting it to return to the original set of "update all," the task refuses to run until after rebooting the machine.[/quote] Here are some new findings that contradict one of the points I made previously. Based on the new evidence, I can confirm that the "repair" parameter is NOT causing updates to fail. First, let me clear up a misstatement in my initial post. Speaking about the Tasks created by the Ad-Aware installation, I said: "My installation created none." This was a typo with very serious implications for the meaning. The installation created "one" process, rather than "none." It is that task to which I am referring in the text below when I speak of the Ad-Aware Weekly Task. Sometime after posting, I had another idea about this problem, and manually ran my Task again to note more details. Within 10 seconds, it had loaded Ad-AwareAdmin.exe, opened the progress bar graph, displayed a popup indicating that "Software is already up-to-date", and played the notice sound. At that point, a button is visible on the Taskbar, and attempting to shift through the open tasks with Alt-Tab shows the "Ad-Aware Update Manager" as an open application. The application stays open indefinitely, unless closed directly in the window, by selecting "Close" from the context menu for its Taskbar button, or killing the Ad-AwareAdmin.exe process. Since the Windows system "Notice" sound was the same one I had identified in my original post in describing the events following the launch of the Ad-Aware Weekly Task with the "repair" parameter, I decided to test that Task again. This time I noticed all the same symptoms as previously: The Update progress bar graph does not appear, even to indicate that no updates were found. I hear the Windows "notice" ring, but don't see any popup, or find any visible window indicated in the TaskBar or in the Alt-Tab window." However, when I looked at Task Manager, I found that the Ad-AwareAdmin.exe process was still loaded, altlhough it was not using any CPU capacity or causing any disk activity. This was the same condition I described in the second paragraph of this post, following the completion of the update process with my Task, until the update application is closed by one of methods described. I now believe that the "symptoms" described when the Ad-Aware Task is run relate not to the "repair" parameter but to the fact that the task is being run as "NT AUTHORITY\SYSTEM." This is the identity showing in the Task information tab for the Ad-Aware weekly task in the "Run as" information box. I believe that that this Identity may not be able to create or close windows. Accordingly, after changing the startup string for that task to omit the "silent" parameter, the script lacked the ability to close the invisible windows that had been opened. This, in turn, kept the Ad-AwareAdmin.exe process in memory until the next reboot--and thus prevented the update script from running again until that was done. To confirm this, I restored the Ad-Aware Weekly Task to the original string of 4 parameters, ran it manually, and watched Task Manager. I saw that it opened Ad-AwareAdmin.exe, closed the Ad-Aware processes for both the tray and service, caused CPU and disk activity, restarted the Ad-Aware service process, and then exited. The update.log showed the following activity: MSG [4584] 2011/04/26 15:09:03: Downloading file: metafile.dat.lzma size: 56kB MSG [4584] 2011/04/26 15:09:03: Connected: download.lavasoft.com//public/aawcherry/ MSG [4584] 2011/04/26 15:09:08: Extended definition: current version is 9127 and latest is 9128 MSG [5076] 2011/04/26 15:09:09: Extended definition: current version is 9127 and latest is 9128 MSG [5076] 2011/04/26 15:09:10: Extended definition: current version is 9127 and latest is 9128 MSG [5076] 2011/04/26 15:09:33: Extended definition: applying 1 update. MSG [5076] 2011/04/26 15:09:43: Extended definition: applied 1 updates successfully, current version: 9128 MSG [4584] 2011/04/26 15:10:20: Update finished Therefore, apparently the only problem with my installation was that the Ad-Aware Weekly Update task created by the Installer was only scheduled to run on 2 days of the week, and only once each day. That in itself would not account for the problems of the users who have not been updated at all, but it suggests that a probable cause for that problem is that the installer created no Task at all, or did not set the Task that was created to run on any days.
  5. [quote name='LS Jeffery' post='126373' date='Apr 26 2011, 02:30 AM']Hello LavaJ431 That message is from our old compatibility check. This is not used anymore, seems we forgot to remove the message for it. But you need not worry, our other compatibility test is running silently. Let me know if you do have any compatibility problems. Regards, Jeff - Lavasoft[/quote] It's good to know the message is not indicating a problem. It would, however, be preferable to eliminate the message from the log. Would you please tell me if the two conclusions in my original post are correct: "The debug.log appears to maintain a record of every process loaded into memory at any time Ad-Aware is running." "Each time the Ad-Aware service is started, a number of standard integrity checks are performed."
  6. [quote name='LS Jeffery' post='126374' date='Apr 26 2011, 02:32 AM']Hello LavaJ431 Thanks for helping with this post. Can you tell me, are you able to create scheduled tasks at all on your system? Regards, Jeff - Lavasoft[/quote] I am able to create tasks. After selecting "Add Scheduled Task" from the Control Panel, a dialog appears with 3 tabs. On the first tab, Windows fills in the name of the user currently logged on, in the "Run as" information box. Then, by putting a check in the box to the left of "Run only if logged in," scheduling can be completed easily. Since creating my task, I've had no trouble updating at the scheduled times, even if the Ad-Aware tray process is running. The "update all" parameters shut down the tray process, download and install the updates, and then restart the tray process. I don't like for updates to go on without my knowledge, so I don't use the "silent" parameter. However, the "repair" parameter breaks things. When I add that parameter to "update all," Ad-AwareAdmin.exe loads, but does not run properly. The Update progress bar graph does not appear, even to indicate that no updates were found. I hear the Windows "notice" ring, but don't see any popup, or find any visible window indicated in the TaskBar or in the Alt-Tab window. Worse, after running my task with the "repair" parameter, and then deleting it to return to the original set of "update all," the task refuses to run until after rebooting the machine. Unfortunately, the Task that was created by the installer provides for 2 updates each week, and each time it is supposed to run with the "repair" parameter. Hopefully, these findings will enable you to resolve the update problems.
  7. [quote name='LS Tobias' post='126375' date='Apr 26 2011, 03:38 AM']The design is meant to be a shield on top of a globe, indicating if Ad-Watch Live is turned on or off. The shield is gray when Ad-Watch is turned off and red if it is turned on. we have had discussions about a redesign for an upcoming version of Ad-Aware.[/quote] A redesign would be great. Particularly in view of the purpose of "indicating if Ad-Watch Live is turned on or off," using the current design has significant security implications. The icon should easily catch the user's eye when live protection is turned off. I have just looked at the icon under a screen magnifier. It would help your purposes if you: 1. Eliminate the globe, and devote all your pixels to the shield; 2. Use a more standard color coding; 3. Fill in all the shield area with the chosen color. 4. Use lighter, iridescent shades of the chosen colors. 5. Once you have an easily visible shield design, spin it around its central axis (like the hands move on a clock) when updating, scanning, or taking other actions. Regarding idea #2: In most of the world, I believe red is a color associated with danger. I can't recall the system used for traffic lights in Europe, but in the United States, green means "go," and red means "stop." I suggest you use green for "protection on," and red for "protection off." Regarding idea #3: The current design of the shield shows it divided into uneven quadrants by a gold "lightning bolt" (?) running horizontally. The interface tells me that "Live Watch" is enabled, but the red coloring is only applied to the outer edge of the shield in the lower right quadrant.
  8. [quote name='LS Jeffery' post='126376' date='Apr 26 2011, 04:23 AM']Hello everyone I have someone looking in to this right now, and will reply when we have a solution. Regards, Jeff - Lavasoft[/quote] Would you please go back to my original post, look at the questions at the end, and provide answers? Except for the first question (which you've just answered), those answers will probably not be affected by any "solution" you may develop for the problem with saving exclusions created by the user.
  9. [quote name='glnz' post='126332' date='Apr 24 2011, 11:59 AM']LavaJ - Noted. However, a number of lines in my new log files are "ERR", which I assume means "ERROR". Do you see the same in yours?[/quote] I'm sure you're right about the meaning of "ERR." Fortunately, most of the instances in my Debug.log occur in relation to the disabled compatibility check: "ERR [5664] 2011/04/24 00:34:38: Incompats..." The only other occurrences pretty much confirm the meaning of ERR as "error," because they appear on lines which indicate a failed operation: "ERR [1392] 2011/04/24 20:57:53: Failed to launch: D:\Program Files\Lavasoft\Ad-Aware\Ad-AwareAdmin.exe uploadcrashdumps" The good news is that the failure to upload crashdumps has occurred because there are no crashdumps to upload. It seems like they'd check for the existence of files before trying to upload them.
  10. [quote name='CeciliaB' post='126328' date='Apr 24 2011, 07:36 AM']The Sunbelt drivers are part of the antivirus program in Ad-Aware Free and Pro.[/quote] That's good to know, but bad news for me. Since there are three Sunbelt drivers, and 3 types of real-time protection that are not enabled in the Free edition, I was hoping that they were only utilized in the Pro version. There are no references in my registry to any of those drivers. The installer included an INF file for one of them, but after running it, and moving the driver to the System32\Drivers directory, I couldn't get it to start.
  11. After the System Tray icon appears during Windows startup, which announces that the Ad-Aware Tray Application has begun to operate, there is considerable disk and CPU activity for the next several minutes. This makes it hard to get much done until the scan has finished, even on a system with 3 GB of RAM and an Intel Core 2 Duo CPU. Can this scan be disabled? Can it be limited, so that it perhaps only scans memory, loaded processes, and the registry?
  12. On 4/24, glnz posted part of his debug.log: [url="http://www.lavasoftsupport.com/index.php?showtopic=31091"]Strange new log files since thorax issue resolved in AAW 9.0.4[/url] It also shows the entry for "Warning : !! Incompatible check disabled !!"
  13. My debug.log looks just like yours. I believe that the repeating sequences beginning with "RP::QueryTraceCallback" are indications that AAW has checked the identified file as it is loaded into memory, and found that it is OK ("DIAGNOSIS_CLEAN"). I believe this is how they achieve what they call the "process protection" provided by "Ad-Watch Live." I wasn't using the program before yesterday, so I can't say whether or not it represents a change from previous functioning.
  14. I can't say the icon in the System Tray area is ugly, because even with a screen magnifier it's hard to make out what it "is." I don't really care about "ugly," but I am annoyed that the design is just not functional at all on my system. I have the standard blue Windows XP theme, and the icon hardly contrasts with the background at all. It just looks like a blob. When something is happening, and the icon animation is working, I hardly notice, because motion is almost invisible. Does anyone else have trouble seeing their icon? Can the icon be changed by the user? Can the company come up with something better?
  15. After running my first scan, I decided I didn't want to have Ad-Aware flag a couple of items in future scans, so I chose the "ignore" option as the response. However, after my next scan completed, I noticed that the same items had been flagged again. At that point, I looked at the "Ignore List" tab under the "Scan" menu, and found that it was empty. On 1/12, tonylukak reported an identical problem. On 1/13, Visitor said, "Thanks for the info. This was previously reported to Lavasoft, so I've updated the info to let them know the bug's still present in version 9." Nothing seems to have been done with that info, however. On 3/25, "LS Digger Barnes" addressed a similar issue, and asked a question of the poster: "Do you mean that they are found in an actual scan again depite being added to the ignore list or did Ad-Watch detect them? the ad-aware scan and the realtime protection in Ad-Watch uses different rule sets." The original poster never replied, but I can say that the items that are not being ignored have been found during on-demand scans. Is a fix in the works for this problem? Is there any way, or any plan to create a way, to allow users to add items directly to the Ignore List through the interface? Can the Ignore List be revised to allow paths, and the entire contents of folders, to be ignored? Is the Ignore List an editable file, to which items can be entered manually? What file contains the data that is supposed to populate the Ignore List?