AVG Shell Extension causing issues with Windows 10 Explorer.exe

I been looking up this issue for quite a while and came across this forum when trying to figure out this issue. Which I will note what I have tried to do so far.

I have tried both recommended commands in the CMD sfc /scannow and the other one. I have reinstalled Windows 10 using the Microsoft Media Creation Tool and have successfully reinstalled it with no problems or loss of data. When I thought the issue may have finally fixed it has not. Then I came across a video that recommend using CCleaner and I noticed someone the other day mention AVG.

Well I used CCleaner and disabled both AVG Shell Extensions (screenshot: https://i.imgur.com/d2oImQ0.png )

While the issue was still happening mind you I downloaded CCleaner without the ability to access my folders since clicking File Explorer was not working on my start menu and I could not right click any folders. After disabling both AVG Shell Extensions it started to work again right after I did this.

So that leaves me with the conclusion that AVG Shell Extension causing the confliction issue with Windows 10, but I personally used AVG all my life and Malwarebytes and know no others, but would like to keep using AVG, but I was wondering if there was a work around this at all to fix my issue while still continuing to use AVG?


Note: I do apologize if it seems odd my first post is here I literally been searching up this issue and been trying to fix it for days. I just registered here. :P

dalchina said:

Hi, could you explain what the symptom of your conflict actually is please?
(Note: screenshots can be posted using the icon to the left of the little video icon).

Well time varies. It just randomly happens no errors or anything in event logs. My file explorer on Windows 10 does not work and right clicking folders causes the explorer.exe to crash and restart.

As I mention all this in the first post. While this issue happen I tried CCleaner suggest by someone else. I disabled AVG shell extentsions and it started working again. When usually it takes a pc restart to get it to work again.

I believe AVG is the one causing conflict issues most likely considering disabling AVG shell extentions got it to work again over having to restart my pc.

dalchina said:

Hi, thanks, missed your symptom as it's in the middle of your first post.. sorry.

There's nothing I can find or can recall about AVG's extension here- there may be somewhere of course. Two thoughts:
- if your Win 10 is an upgrade, did you upgrade with AVG installed (not recommended)?
- is your AVG 2015 or 2016?

You could try uninstalling it, reinstalling it.

Right now I am at work but I am pretty sure it is 2016. Also I upgraded to Windows 10 from 7 last year. This issue started about a week ago out of the blue. Its possible AVG updated and it corrupted the shell extension? Since it is pretty obvious its coming from it.

Going to give an update I uninstalled AVG and just currently using Windows Defender for now. It seems the issue has not happen since uninstalling AVG like it would normally have by now. So I am 100% for sure it was AVG causing my issue.

I had exactly the same problem and the problem is with the AVG Shell Extension Class. Disabling the context entries for the two AVG entries of that name, followed by killing the explorer.exe process and running a new one (both actions done via task manager), fixes the immediate problem of not being able to start new file explorer instances. The symptoms of this for me were seeing existing file explorer instances freezing up completely when right clicking a file or folder in them, and also not being able to start a new instance from either the taskbar or via the shortcut (Win+E). Instances can be started by start/run and specifying a folder name.

This issue was not present until a recent update by AVG some time around the 15th May 2016. I have a paid subscription to AVG and do not want to uninstall anything so disabling the context entries is what's working for me. I used regedit but a good tool for this for anyone not familiar with the registry would be ShellExView by NirSOFT.

Happens here just since this week as well, and it is likely to be caused by one of the latest updates of AVG.
When removing the AVG-application from the context-menu, the problem is solved.

To get rid of AVG from the context-menu, download CCleaner (from piriform.com), install & open the application. Then click "Tools" -> "Startup" -> "Context Menu" and disable "AVG Shell Extension". Note, the AVG-extension can be twice in the list, disable both of them. As far as I know this is not making your pc less secure, it will just not provide you the option "scan with avg" when right clicking a folder or document.
Hopefully AVG picks this bug up soon & fixes it.

I just wanted to drop in and report that I'm experiencing the same issue. Problem started a week or two ago from a fresh Win10x64 install. Disabling the AVG context menus resolved the File Explorer crashes for me, as well. System works fine on reboot with no modifications, but eventually the AVG context menus cause a hang that persists until reboot or disable.

However, I would note that the AVG GUI no longer works properly after the context menus are disabled. I can not confirm whether disabling the context menus has any effect on the resident shield.