AVG Ini & Display Set

[Randy]

Any ideas?

About 3 of 4 boots, I get the following message at Desktop: "Could not
initialize AVG Anti-Virus kernel interface. Application cannot run." Then I
must fire-up AVG 7.5.432 manually with its handy pull-start rope.

Also, RC1 5600 forgets resolution or frequency settings on the ol' GF3
Ti500. Pull-start expected here too or is there maybe a registry-mix fix?

Thanks and Happy Oh-Seven!

~cheeryvistacamper

 

[Dale]

I'd look for both of these issues to go away shortly after release to the
public at the end of January.

Dale

 

[Frank Saunders, MS-MVP OE/WM]

Any ideas?

About 3 of 4 boots, I get the following message at Desktop: "Could not
initialize AVG Anti-Virus kernel interface. Application cannot run." Then
I must fire-up AVG 7.5.432 manually with its handy pull-start rope.

Also, RC1 5600 forgets resolution or frequency settings on the ol' GF3
Ti500. Pull-start expected here too or is there maybe a registry-mix fix?

Thanks and Happy Oh-Seven!

~cheeryvistacamper

No problems with 7.5.432 on RTM.

 

[Ed.]

I get that same exact thing happening with my AVG and the same message. I am
using 7.5.432.
Hopefully they will get it fixed.
Glad to see that I am not the only one.

 

[Randy]

Until MS V final is released, I'll use hibernate to bypass issues.
Cheers!

 

[Guest]

I have the same issue with AVG 7.5.432 and Vista RTM (same on RC1 and 2).
Come Jan 30, I don't think we'll see much of a difference unless AVG
addresses this (I've tried 4 AV software and only AVG exhibits this).

Going on various forums, and the AVG support forum, it seems some people are
convinced that at boot up Windows is starting before a certain AVG component
is given permission by Defender and hence the error. This may explain why
waiting 15-20 seconds after logging in you'll be able to start AVG manually.
I can't verify this but some are completely convinced of it.

My workaround is like yours; hibernate. It will fix this as the issue only
happens on boot up.

 

[Frank Saunders, MS-MVP OE/WM]

I have the same issue with AVG 7.5.432 and Vista RTM (same on RC1 and 2).
Come Jan 30, I don't think we'll see much of a difference unless AVG
addresses this (I've tried 4 AV software and only AVG exhibits this).

Going on various forums, and the AVG support forum, it seems some people
are
convinced that at boot up Windows is starting before a certain AVG
component
is given permission by Defender and hence the error. This may explain why
waiting 15-20 seconds after logging in you'll be able to start AVG
manually.
I can't verify this but some are completely convinced of it.

My workaround is like yours; hibernate. It will fix this as the issue only
happens on boot up.

As I said, I have no problem with RTM. I had that often with the Release
candidates but I'm not sure whether I had 7.5.432 yet. It's possible that I
had it in the beginning with RTM, but certainly not recently.

However, that hypothesis sounds reasonable. One could test it by disabling
Defender temporarily if they have the problem.

 

[Ed.]

I don't use hibernate but I do use STR and this occurs with it too at times.

 

[Randy]

I do this instead of crossword puzzles. Fixed the resolution/frequency
settings with an obvious HKLM Run setting. Downloaded the latest Defender
definitions and now it shows AVG "Permitted" but still get the warning
unless I give avgcc.exe Admin Privileges then the warning doesn't appear
but the program still doesn't load. No biggy. Just fun trying.

Just noticed in Windows Mail that if you make changes to a message the click
Send, you end up with two messages ready to go. The original and the edited.
Hmmm, another puzzle?

Uh-oh. Looks like I'm talking to myself... again.

 

[Randy]

Found this in the AVG Discussions and it works for me (still, use at your
own risk):


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Try this:

Take AVG out of your registry startup items. Either use msconfig to disable
the startup item or open regedit and go to
HKLM\software\Microsoft\windows\CurrentVersion\run and delete the AVG_CC
entry)

Create a new txt file, and rename it from a .txt file to .vbs. I called mine
Start_AVG.vbs. I created this script to delay the startup of the AVG Control
center for 2 minutes. Copy the following code into the new VBS file you
created:

'------------------------------------------------
dim WSHShell, strProgPath

set WSHShell=CreateObject("wscript.shell")


wscript.sleep 120000

strProgPath = """C:\Program Files\Grisoft\AVG Free\avgcc.exe""" & "
/STARTUP"

wshshell.run strProgPath,7,false

'------------------------------------------------

Now copy this file into your "Startup" folder in your start menu. Restart
your computer and about 2 minutes after your desktop appears, AVG will then
appear in your Notification tray.

Something apparently isn't started up all the way when AVG wants to start
up. This solves the issue. Hopefully this will help until Grisoft fixes the
issue.

 

[Ed.]

I see that AVG Free is now updated to 7.5.433. I haven't tried it yet and
don't know what is new in it.
Perhaps this might correct our problem.

The site says just to upgrade it from your current version by using the
check for updates. Right click on the AVG icon down by the clock and then on
Check for Updates.

http://www.grisoft.com/doc/update/lng/us/tpl/tpl01

Ed.

 

[Daze N. Knights]

My AVG Free version is 7.5.433 and its updater says it has the latest
updates. Nevertheless, I, too, have this failure to initialize kernel
problem at startup on, not one, but two computers running Vista 32 RTM.

 

[Ed.]

Oh man, what a bummer. Sure hope they get this fixed.

Thanks for the info. I haven't installed yet so I won't bother.