How Well is Your System Protected?? --Five Simple Test from AMTSO

Hey TH, that REVO is quite a piece of kit, but it didn't make any changes regarding Chrome unfortunately. I used REVO to uninstall Chrome as well, reinstalled it, then reinstalled WSA once again and still no extension beyond the Webroot Password Manager, and no Chrome folder or extension populated for manual insertion. I appreciate the info provided however; it looked like something that could make a difference. There was quite a few bits left behind to delete for sure. It sure would have been nice to have had access to something like REVO back in the NAV days!

Why do I keep getting this error when I try to post btw? I'm not using any HTML in my posts but I've gotten this several times.

"Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied."

Thanks!

Bob

Hello TH....I did call for that purpose, but was told the estimated hold time would be 40 minutes. I called at a bad time I'm sure, as business typically picks up in the early evening after work, so I'll try again this morning.

What contributes to the strangeness is that it is on two of my Windows 8.1 machines, the Surface Pro and the ThinkPad X61. That suggests to me that it isn't a hardware issue at all and that there is some type of a conflict between WSA and the late versions of Chrome, but support wasn't able to replicate it.

I'm not running any other Security software, no. I now have Malware Bytes installed, just in case of a disaster, and some good backups. I do have time left on a Bitdefender product, which I could install, but WSA has such a small footprint, it's perfect for both of my SSD (storage space challenged) machines. I'd like to get it worked out anyway, as I'm sure it's not just me having this issue. The Surface Pro has very little installed excepting MS Office, so it's not much more than a virgin machine (haven't had enough time to corrupt!).

I agree that we've gone as far as we can on the forum with this, and if I get any positive results from tech support live, I'll post for the benefit of others. I certainly appreciate everyone's efforts and support!

Thanks,

Bob

Hello Daniel,

I'm still communicating with Tech Support on this issue, and just got back home and will try to call them right now. Thanks!

Bob

Hi Bob
 
Just got into the Community.
 
How are you?
 
Very interesting but does not surprise me.  Not quite a perfect result but at least you know that you are now not alone.  Do keep us posted with whatever the Support Desk come back with...and if you do not hear from anyone after what appears to be a reasonable while do not be afraid to 'nudge' both via the Support Ticket system and over here in the Community.
 
Have a great weekend.
 
Regards
 
 
Baldrick

Hey guys,

The response from the team made a lot of sense to me; it didn't fix my problem, but I believe they're on the right track. I believe Chrome, or at least the later versions of it, are making it a little more difficult regarding extensions. I knew that to be the case; all of them are supposed to come from the Play store I'm told. That doesn't explain how the Webroot Password Manager extension is able to sneak through of course. At any rate, I'm posting their suggestion here, as it may help others, even though it didn't work for me. It just looks reasonable to me anyway. This from an Escalation Engineer:

"Hello,

There are a number of changes that Google has made to make Chrome more secure, one of these initiatives was started with the 33.x build. The idea is to force all extension installation via the Chrome store. While this isn't yet a requirement, some of the code base to make this a reality is in place on the 33.x build.

It is possible that the method we are using to install the extension isn't working in your particular installation of Chrome. This may be because of several issues, however, it may be possible to force the extension installation by following a procedure. I've outlined this process below, while there is no guarantee that this will work, it would be good to try it as we've had some success in the past.

1. Uninstall Webroot
2. Uninstall Chrome
3. Reboot
4. Install Chrome
5. Reboot into Safe Mode with Networking
6. Install Webroot
7. Reboot into normal Mode

Check to see f the extensions installed properly,If so, great, if not, please let us know and we'll update our development team to reflect the information.

Thanks,"

So we'll see when/if there is anything they can do to resolve. I've left Chrome and am working it out in Firefox and getting more comfortalble each day I think. So there's no hurry.

Just keepin' you up to date!

Bob

Hey TH I just read your post here and I needed that info and pictures. Thanks

Can you look under extensions in Chrome and confirm the you have the Web Filtering extension the number doesn't matter?
 
Thanks,
 
Daniel
 

@ wrote:
Can you look under extensions in Chrome and confirm the you have the Web Filtering extension the number doesn't matter?
 
Thanks,
 
Daniel
 

Oh.., in Chrome I still have the extension signed with 1.0.0.32.
Was it updated?

Hello! I do indeed have the filtering extension installed. I had to do it manually from the Chrome store, but it's there...just not working entirely, but will be soon as tech support is pushing something in the next couple of days.
 
Bob
 
 

Let me see what I can do.

After further testing, it is our business customers using the legacy PhishCheck web filtering component that are not blocked by this. Consumers using the new PhreshPhish web filtering are properly blocking this test page.
 
I am having this added to the PhishCheck database and should be blocked within 24hrs.
 
Let me know if anyone is seeing anything different.
 
Thanks all,

Hi Shawn
 
Thanks for keeping us posted on this one.  An interesting conumdrum...should it be block or not, etc.  Glad that we now have clarity on this point.
 
Regards
 
 
 
Baldrick