• 0

AVG 7 with Outlook 2003? How?


Question

Goodevening everyone,

I was just wondering if someone could help me out with setting up my AVG 7 to work with emails i recieve with Outlook 2003. I have the latest version of AVG and on the 'Control Center' of the program, it states that "Email Scanner Is Not Fully Functional". What do i need to make it be functional?

When i click on Activate for the E-mail scanner, it comes up with the Email Application Selection screen but only shows Outlook Express 4, 5 and 6. But no Outlook 2003

Can anyone help?

Thank you for your help and time

Alex

Link to comment
https://www.neowin.net/forum/topic/153301-avg-7-with-outlook-2003-how/
Share on other sites

20 answers to this question

Recommended Posts

  • 0

Download the latest version from www.grisoft.com and then run the installer and select to add componets (not remove, etc). Then add the email scanner and the MS Outlook plugin. The MS Outlook plugin will work out of the box so to speak however you will need to setup the email scanner which is a proxy between your Outlook and your mail server. So you set your servers (both POP and SMTP) to 127.0.0.1 and the ports you specify. Your mail will then be checked when you send/receive it as it will automatically go through AVG and be scanned.

Technically you don't need both plugins installed but it won't hurt doing it. PM or MSN (I would prefer MSN) me if you need any help.

  • 0
Yeah, thats what i did basicly, only im not too keen on the proxy type one, so i dont use it

Technically the Email Scanner (local proxy) is the most powerful antivirus email scanning posibility as it means AVG has exclusive access to the email and all atachments. The problem with plugins is that the developer of the plugin is limited to the APIs that the client (in this case Outlook 2003) has on offer. Now I don't know a great deal about the Outlook 2003 plugin however I very much doubt that AVG is given exclusive access to the email. Outlook probably says "this is the attachment, does it have a virus?" and AVG will reply saying either yes or no.

I use both the Email Scanner and the plugin for The Bat! email client however if I had to choose I would pick the Email Scanner. Just my opinion though. Why do you not like it btw?

  • 0
uninstalled AVG... it sucks with Email scanning IMO

Alex :cool:

Why do you think it sucks? You never got it working so therefore you can't have a real opinion of the email scanning. Your opinion of the plugin configuration and setup is probably not very high as you have had problems but you can't really say its email scanning sucks. That is like me looking at a Ford and not liking the design so saying "all Ford's suck".

  • 0

sorry, i was just in a mood the other day,

Im eager to get AVG working with Outlook 2003 again

But even when i had the Plugin selected, it still came up with the email scanning not working properly.. why is this?

What versions are you all using? Im have the latest :huh:

Thanx for your help everyone

Alex :cool:

  • 0

Alex_is_Axel what options do you have in AVGs drop down list for email plugins?

If you have just the AVG MS Outlook Extenstion then it should work no problem. It can't not work really as it is just an extension that Outlook loads. If you have "Personal E-mail Scanner" installed and not setup then it will be reporting an error and that is why you will get the red error . On all the installed plugins click the "Ignore plugin status" check box so that it reports no errors, then untick it for one plugin and check the status, keep doing that until you get the error again and then you know which plugin(s) are causing problems.

  • 0

i thought id try something out and download the free version of AVG

AVG 6 Free Download

And guess what?!?!?.. Outlook worked with it no problem! I couldnt believe it

For once IMO, Free version of software works better than a paid edition.. *laughs to himself*

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!