I am running the latest version of Avast Free on my personal computer (Windows 7 Enterprise and the latest version of Chrome). I have installed the Motorola Connect Chrome extension in order to connect to my Motorola Droid Turbo. The extension works perfectly when I disable my Avast Web Shield, but it will not connect with the Web Shield active.
Is there a way to whitelist a particular Chrome extension?
Sure, add it to the exclusion list.
Hello,
send us the extension to analyze, please. Use https://support.avast.com/ → Avast Virus Lab.
Thanks,
Milos
I am also having this issue. It began occurring sometime in December 2014 and is still a problem. I will send the extension in to the virus lab but when can we expect this to get resolved?
And how would we do that on the WebShield? Chrome extensions aren’t .exe files, you know.
Exclusions don’t have to be executables 
They do because the exclusion list for WebShield has only MIME, URL, and Processes. When attempting to exclude a “process,” it only allows you to select .exe files. If I exclude the entire folder containing the aforementioned extension or even the Profile 1\Extensions\ folder using a wildcard, it still fails. Literally the only fix I have found is to completely disable the shield.
You are wrong.
It shows executables by default (filetype > .exe), but you can select to show all files (filetype > .)
Regardless, excluding the entire folder of the extension does nothing. Nor does excluding the entire extensions folder for Chrome. Issue still occurs.
I have this same problem. getting it fixed would be a great help.
Try this board https://forum.avast.com/index.php?board=54.0
I got it to work by adding the Chrome extension to the Web Shield’s URL by going to Avast, clicking the following links
[ol]- Avast Main Window
In the input field, enter the following:
http://chrome-extension://kigmoblgooahdmdibodmcnffgnejlndh/*.*
This should allow it to work again.
It should still be sent to Avast as requested. If it’s a false positive, it will be corrected and the exclusion will not be needed.
I would never exclude anything without first making sure it isn’t something that could harm my system.
But, it’s your system not mine. 
There is a discussion going on on this “suspicious” extension here: https://productforums.google.com/forum/#!topic/chrome/2yTVWdfC4Gg
polonus
One used to be able to drop the CRX file directly onto the Extension page.
Down and dirty and I don’t know if it still works in Chrome. Here’s an example:
http://youtu.be/LRLESIpai2M