Showing results for 
Show  only  | Search instead for 
Did you mean: 
Former Member
Not applicable
Report Inappropriate Content
Message 11 of 12

Re: wrong DATVersion in registry

to get past our Nessus scanning....

Here is what I had to do.

Followed the "To Manually Fix the registry issue:" above, but

1) Click Start, Run, type regedit, and click OK, right clicked and selected Run As Administrator.

2) Navigated to the appropriate location below: 64-bit systems: HKLM\Software\Wow6432Node\AVEngine, AVDatVersion

3) Stop the McShield and Framework service first.

4) In the right pane, right-clicked and selected AVDatVersion (ours was already there).

     Modified the AVDatVersion and set Value data to 7195.

     Modified the AVDatDate and set the Value data to 2013/09/11.

5) Closed the registry editor.

6) restarted services.

** issue I see is that when we get scanned again, since this is a "dead, non-updating" registry entry, we will get a false-negative again...

Has anyone just deleted this "old" AVEngine registry entry???

Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 12 of 12

Re: wrong DATVersion in registry

anybody got solutions for this problem?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community