Looking for: SBVIPRE_DEFS_EN.msi

I rcvd an equally confusing non-answer from a lvl 1 support person today - 5 months later - when trying to reinstallthe same release (because v3.1.2710 cause far too many Block notifications).

Andrew, Errors with SBVIPRE_DEFS_EN.msi are normally caused by a problem with the installation, and Vipre is trying to repair itself but cant find that file.

To resolve it uninstall Vipre using add/remove programs, then reinstall VIpre. The current version listed on the website is still 3.1.2416, or you can re-download 3.1.270 from this link http://www.sunbelt-software.com/suppo...

If you continue to have problems with this error please let us know.
Thanks,
Peter

I have just found a response on SB's website (in the KB) using the following google link:

http://74.125.93.104/search?q=cache:H...
[The KB reference is Answer ID: 1781 Product: VIPRE Last Updated: 1/9/2009 ]

It basically says that, at the point where the installation stops and asks you for this .MSI file, you first go to your Temp folder (enter %TEMP% in CMD mode) and find the folder with a similar registry key format - mine was {4CB2D770-FB49-44FE-8D99-AC9BEC59576B}. You'll find the MSI file inside it. Then copy this whole folder to your desktop, return to the Installer step searching for the .MSI file, and now point it to your Desktop folder.

Incidentally, I'm not sure whether this is the whole story. Before trying to install Vipre 3.1.2614 again, (after v3.1.2710 gave me grief with persistent, repeated Block/Allow Notices). I observed that VIPRE was still in my Add/Remove Folder and wouldn't uninstall. Why? Because it was looking for this same SBVIPRE_DEFS_EN.MSI file! Which of course it couldn't find.

I suspect that the Installation (or reinstallation of Vipre v 3.1.2614) is dependent on this .MSI file because it needs it to uninstall a previous copy first. Hence the unistall asks for this exact same .MSI file.

I may be wrong, but that the route I've taken. Instead or trying to Install Vipre with the MSI file I now copied to my desktop, as described above, I instead ran the Unistall from my Add/Remove fold, and proceeded to observe controlled uninstall, pauses for me to select Total Uninstall including all previous config and report files, or simply a Program Uninstall. I selected just the Program Unisnstall and rcvd a clean completion message.

I shall now attempt to install Vipre again, from v3.1.2614, and supect it will install cleanly without requesting this MSI file again.

In fact, that is exactly what happened. I reinstalled Vipre without any request for the stupid .MSI file. So I suggest, if your install is bugging you for this MSI file, save a copy to your desktop as instructed above (and in the KB link). I then recommend you stop the install, and go to Add/Remove Programs and uninstall Vipre, pointing the uninstaller to this MSI file. When the it completes cleanly you can the go ahead and install Vipre again without any hassles.

I have just found a response on SB's website (in the KB) using the following google link:

http://74.125.93.104/search?q=cache:H...

[The KB reference is Answer ID: 1781 Product: VIPRE Last Updated: 1/9/2009 ]

It basically says that, at the point where the installation stops and asks you for this .MSI file, you first go to your Temp folder (enter %TEMP% in CMD mode) and find the folder with a similar registry key format - mine was {4CB2D770

-FB49-44FE-8D99-AC9BEC59576B}. You'll find the MSI file inside it. Then copy this whole folder to your desktop, return to the Installer step searching for the .MSI file, and now point it to your Desktop folder.

Incidentally, I'm not sure whether this is the whole story. Before trying to install Vipre 3.1.2614 again, (after v3.1.2710 gave me grief with persistent, repeated Block/Allow Notices). I observed that VIPRE was still in my Add/Remove

Folder and wouldn't uninstall. Why? Because it was looking for this same SBVIPRE_DEFS_EN.MSI file! Which of course it couldn't find.

I suspect that the Installation (or reinstallation of Vipre v 3.1.2614) is dependent on this .MSI file because it needs it to uninstall a previous copy first. Hence the unistall asks for this exact same .MSI file.

I may be wrong, but that the route I've taken. Instead or trying to Install Vipre with the MSI file I now copied to my desktop, as described above, I instead ran the Unistall from my Add/Remove fold, and proceeded to observe controlled

uninstall, pauses for me to select Total Uninstall including all previous config and report files, or simply a Program Uninstall. I selected just the Program Unisnstall and rcvd a clean completion message.

I shall now attempt to install Vipre again, from v3.1.2614, and supect it will install cleanly without requesting this MSI file again.

In fact, that is exactly what happened. I reinstalled Vipre without any request for the stupid .MSI file. So I suggest, if your install is bugging you for this MSI file, save a copy to your desktop as instructed above (and in the KB link). I then recommend you stop the install, and go to Add/Remove Programs and uninstall Vipre, pointing the uninstaller to this MSI file. When it completes cleanly you can then go ahead and install Vipre again without any hassles.

You can also try to disable any vipre programs in start up.
\ start>run>msconfig

Uncheck all programs that are related to vipre and then restart your pc.

by then you can uninstall the vipre program to add/remove program at control panel and re-install it