Need help with Computer Problem

[Dominic J. Maricic]

Originally Posted by relliott

My AVG will not update and there is no anti virus protection, so I may be going back to McAffee.

Have you downloaded version 8 yet, or is your computer sitting back on version 7?

[relliott]

Originally Posted by dmaricic

Have you downloaded version 8 yet, or is your computer sitting back on version 7?

I just installed it on that new netbook.
It will not update.
8.0 and I get the balloon for out of date with with invalid CTF file.

May be getting another website soon and will use you of course.

!00 is not enough.
Only $29.99 a month right?

[Dominic J. Maricic]

Originally Posted by relliott

I just installed it on that new netbook.
It will not update.
8.0 and I get the balloon for out of date with with invalid CTF file.

May be getting another website soon and will use you of course.

!00 is not enough.
Only $29.99 a month right?

Websites are $19.99 a month for InterNACHI members

Uninstall and reinstall AVG.

[relliott]

Originally Posted by dmaricic

Websites are $19.99 a month for InterNACHI members

Uninstall and reinstall AVG.

Better than I thought (will let you know)

Did and it worked.

I think you need to hit the check for update now option at install or it corrupts that feature.

[Mark Nahrgang]

Originally Posted by bking

Here you go.........

http://www.helpwithwindows.com/techf...r-crashes.html

Ok, I'm up and working again. And it truly was a group effort, thank you all very much. This link that Bruce provided, linked me to a piece of software that allowed me to turn off some shells that were running on my system and fouling things up (it was actually two files in combination.)

Here's how I got it going again:

I was running the sfc /scannow that Dom had suggested and got an error message that some but not all of the corrupt files were fixed.

I thought that was odd, and decided to try running this as the administrator login. (My account has administrator rights and privelidges, but sometime actually logging in as administrator helps.)

I noticed when I logged in as administor, that my problem went away, and when I logged back in as myself, it came back.

That lead me to believe that it was a program that was running in my account but not the admistrator account. Using the ShellExView.exe program referenced in Bruce's link allowed me to turn off the shell files for all the applications one at a time until I found the culprit.

This was actually harder that you might think. I started by turning off ALL the non microsoft shells (there were about 100 of them). And my problem went away. I turned them on one by one but the problem remained fixed until re-boot. That told me that it wasn't one but several in combination. I then sorted them by application, and turned them off in groups until I found the bad guy.

Thank you again everyone! I was stressing over this, and your support and advise helped me tremendously!

[Dominic J. Maricic]

Originally Posted by mnahrgang

Ok, I'm up and working again. And it truly was a group effort, thank you all very much. This link that Bruce provided, linked me to a piece of software that allowed me to turn off some shells that were running on my system and fouling things up (it was actually two files in combination.)

Here's how I got it going again:

I was running the sfc /scannow that Dom had suggested and got an error message that some but not all of the corrupt files were fixed.

I thought that was odd, and decided to try running this as the administrator login. (My account has administrator rights and privelidges, but sometime actually logging in as administrator helps.)

I noticed when I logged in as administor, that my problem went away, and when I logged back in as myself, it came back.

That lead me to believe that it was a program that was running in my account but not the admistrator account. Using the ShellExView.exe program referenced in Bruce's link allowed me to turn off the shell files for all the applications one at a time until I found the culprit.

This was actually harder that you might think. I started by turning off ALL the non microsoft shells (there were about 100 of them). And my problem went away. I turned them on one by one but the problem remained fixed until re-boot. That told me that it wasn't one but several in combination. I then sorted them by application, and turned them off in groups until I found the bad guy.

Thank you again everyone! I was stressing over this, and your support and advise helped me tremendously!

Glad you got it working

That ShellExView.exe is pretty cool, I'd never seen it before. Thanks!