Michael Lamczyk

started a topic
almost 2 years ago

VIPRE Edge Protection blocking all sites

I installed the VIPRE 9.3 Business agent on several Windows 7 Professional workstations and everything seemed to be fine. Today, I upgraded a few of those machines to Windows 10 and found that the Edge browser is not able to access any web pages with the VIPRE Edge Protection service running. As soon as the edge protection service is shutdown, the Edge browser works and can access all sites. Is there a simple way to repair the edge protection? I assume part of the problem was that VIPRE 9.3 was installed prior to the Windows 10 upgrade since I did not have this issue on any machines that already had Windows 10 when VIPRE was upgraded.

John Watson

said
almost 2 years ago

Thank you for bringing this to our attention. The only way I know to repair the edge service is to reinstall the agent software.

I'm gonna send this over to our testers to try and reproduce it, it is most likely something in the windows 10 upgrade that caused this.

I'll let you know what we find, if the reinstall doesn't fix the issue please let me know.

M

Michael Lamczyk

said
almost 2 years ago

Reinstalling the agent does correct the problem... However, I would like to know if and when this issue is resolved as I expect that we will be dealing with more and more upgrades in the next few months.

R

Russ McKee

said
almost 2 years ago

I have an identical problem after upgrading two systems from Win 7 Ultimate to 10 that have Vipre Internet Security 2016.

John Watson

said
almost 2 years ago

This will be fixed in the next agent release. The fix will also be ported in the the consumer version, I'm just not exactly sure on when it will be available in the home version at this time.

The problem is caused because the edge service doesn't see that OS was upgraded and it still loading the driver for windows 7 instead of windows 10. That is why the reinstall correct the issue.

I hope this information is helpful.

G

GrantG

said
almost 2 years ago

We have a nearly identical problem, but with computers with clean Windows 10 installs, and Vipre installed separately.

Some users cannot access any sites with Edge, some others just don't work on specific sites.

Stopping Vipre Edge Service makes it work for both those groups.

Will attempt agent reinstalls.

R

Ray Grace

said
almost 2 years ago

Is there currently a way to remove this service via the console?

John Watson

said
almost 2 years ago

No the service cannot be removed.

There has been some issue identified with the protection blocking certain site and mostly internal sites. That is something our developers are still working on fixing. As for it blocking all pages in the edge browser we were able to reproduce that after upgrading from window7 to windows 10 it loads the wrong version of the driver so everything in the edge browser was being blocked. Reinstalling the agent would fix that issue, Or upgrade to the current released agent 9.3.6012.

If you are still having issue after upgrade to the latest agent please do open a case with support.

J

Jason Metzger

said
almost 2 years ago

90% of our clients have the latest 9.3.6012 build and the majority of them cannot reach the spam portal among other local resources. I can't tell if the common thread is the invalid SSL cert or the use of an IP address rather than a domain name. Either way, the Vipre Edge service doesn't like it and completely blocks it without a proper error message. This is not a feature I desire to pay for. Currently I'm paying in man hours to come up with a work around and to contact you about the persistent issue with the Vipre product. Please either fix this new feature or allow us to turn off the malfunctioning part.

C

Cameron Schroder

said
almost 2 years ago

This is preposterous! Did you hire John Mcafee?

This needs to be fixed ASAP!

My company is having the exact same issues. Running the 9.3.6012 build and clients are not able to reach the spam portal.

Please fix!

John Watson

said
almost 2 years ago

This particular thread started as an issue with the edge service blocking all pages in the edge browser when you upgrade the windows operating system from windows 7 to windows 10. This issue was fixed with the release of agent version. 9.3.6012.

As for the various pages not opening our developers are working to correct that as soon as possible. You can work around those issue by stopping the VIPRE Edge service and setting it to disabled. If you do not have a case open for this please do open one with support so we can notify you when it is fixed.

I hope this information is helpful.

J

Jason Metzger

said
almost 2 years ago

I'm sorry I thought this particular thread was started because the Vipre Edge service is malfunctioning and not nearly ready for prime time. My bad. Yes we have started a case.

I'd like to think that the majority of the cases I open with Vipre would be because Vipre let something through that it shouldn't have or that it blocked some obscure legit item. This is sadly not the case. Most of the cases have been due to software and definitions that haven't been vetted properly. This is probably going to hurt your Gartner Magic Quadrant status.

J

Jason Metzger

said
almost 2 years ago

It seems as though magically this has now resolved itself. No version change observed but non-the-less users are reporting the issue fixed. Thank you for your help.

B

Brenda White

said
over 1 year ago

This just happened to me...I had to uninstall Vipre and reinstall to get it to work. Just curious if there has been a resolution.

John Watson

said
over 1 year ago

This particular thread started as an issue with the edge service blocking all pages in the edge browser when you upgrade the windows operating system from windows 7 to windows 10. This issue was fixed with the release of agent version. 9.3.6012.

As for the various pages not opening our developers are working to correct that as soon as possible. You can work around those issue by stopping the VIPRE Edge service and setting it to disabled. If you do not have a case open for this please do open one with support so we can notify you when it is fixed.