Product release information for VIPRE Advanced Security for Home - Windows Edition, released on December 12, 2019. This Beta release is version 11.0.5.
Important: VIPRE Advanced Security for Home uses advanced technologies for today’s newer operating systems and does not install on Windows XP or Vista.
To run VIPRE Advanced Security for Home features effectively, you need a PC-compatible computer with:
32- or 64-bit versions of either
Applies to email PC internet security protection
Other email products that use SMTP/POP3 for sending and receiving messages, including Mozilla Thunderbird, and many others.
Note: SSL and TLS security protocols are only supported with Microsoft Outlook.
Product and company names are trademarks and registered trademarks of their respective owners.
This section lists issues that are known at the time of release. In some cases, these are bugs that we are working to resolve with a subsequent release. Other items may be due to causes outside of our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider, should you experience an issue.
If you have questions about a specific issue, please provide the issue ID (if applicable) when contacting our Technical Support team.
This message happens because VIPRE requires .NET 4.6 to run. On some computers, Windows must be updated before .NET 4.6 can be installed.
To install .NET 4.6 on Windows 8.1 and Windows Server 2012 R2, you must first run Windows Update and patch your PC.
See the Microsoft KB articles below for more details, or our VIPRE Support article.
The following bugs are resolved with this release.
© 2019 j2 Global, Inc. and its affiliates (collectively, “j2”). VIPRE, VIPRE Advanced Security, ThreatTrack, ThreatAnalyzer, ThreatIQ, ThreatNet, and ThreatSecure are trademarks or registered trademarks of j2. All other trademarks are the property of their respective owners. All rights reserved.
Good, very quick, clean update from Beta 1 to Beta 2. No issues so far.
Smooth update from Beta 1 to Beta 2 on Microsoft 10 Pro 64bit. No issues to date. Great job.
Smooth update from Ver 22.214.171.124 to 126.96.36.199 on the following PCs.
- Desktop Windows 7 Home Premium 64bit
- Laptop Windows 8.1 64bit
- Laptop Windows 10 Home 64bit
Both my Win10 fast ring platforms installed the software, but got an error at the end of the process that stated the definitions could not be updated. Then the install finished and appears to be functioning properly with this mornings updated defs (80012).
This installed version says it is 11.0.5. Anything in particular that I should check?
Chris, this error can sometimes display if it takes longer than usual for the definitions to apply. This generally happens on slower machines or systems where something else is using a lot of resources, specifically disk usage. Often, if left for a little bit longer, VIPRE will actually finish updating the definitions, which is sounds like is what happened in your case.
As long as you can now successfully check for updates without an error, it sounds like everything is working fine.
Nick - The defs are now at 80100 or 80094 depending on the machine and everything appears fine. These are slightly older Dell platforms, so they can be kind of slow at times.
Updated my fathers PC Laptop Win 7 Home with this version (forced beta update), because Vipre was not loading every time he booted his machine. Hopefully he won't have the problem again.
Just upgraded my 2nd Win 7 box (1 Home and 1 Pro). Both upgrades were smooth and flawless.
I am still contemplating installing on my new Win 10 1809 box.
Still smooth and flawless here as well.
You can use your own key if you like. We supply the beta key so you can test the product without wasting registrations on your own key. If you are just upgrading an existing installation, it's perfectly fine to keep using your own key.
Just an update on the Duration (from History) of recent Vipre scans (Win7 Home Premium 64bit):
Last night: just over 8hrs
The night before: 2.3Hrs
The shortest time about a week ago in amongst longer times: 1.4Hrs