Loading Profile...
Windows Installer won't work correctly
I run the .exe file downloaded from the site. I've purchased the home licence. I've installed it on two machines so far with no issue, but on this machine (XP SP3), it tries to unpack, and then a windows installer box pops up with command line arguments in it, and that's it. I can't find any way to extract the .msi and run msiexec from the command line either. Help!
I’m indifferent
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thank you for posting,
This is a strange issue which may be related to something being awry with your Windows Installer. From what I've seen this has only happened on XP sp3 systems.
Please contact our support department at support@sunbelt-software.com or call 877-673-1153 M-F 9am-6pm est and we will have someone work one-on -one with you. Reference ticket number 001-00-239819.
Thanks,
Jason Layman -
Inappropriate?I have resolved this issue, and you can close this support ticket.
Perhaps this will help if you have any future similar issue raised but this is what had occurred.
I had acquired this machine giving me issues from a client. It already had Windows XP installed on it, and due to Microsoft's crazy licensing system, and as I didn't get a back OS CD with it, I had to be careful not to delete Windows, although ideally I'd like to have reformatted the hard drive and re-install the OS.
What I did do, however, was change both the computer name, and the user name. This had the effect of creating a new 'My Documents" directory. When a self extracting .exe is run, such as vipre.exe, it extracts the *.msi file(s) to a temp directory within the Documents & Settings directories. As I changed the user and computer name, msiexec couldn't do it's job of installing the msi as it quite simply couldn't find the correct path.
After a little head scratching and poking around, I located the temp files, and was able to manually load, and therefore intstall Vipre on this machine.
Finally, I'd like to take this opportunity to say that I've been running the beta version of VIPRE on a couple of machines here for a while, and have indeed found it to be both safe, and an efficient user of system resources (unlike other major AV and AS products!). I'm also very pleased to see the home-wide license, as it can be very difficult to justify purchasing numerous licenses for home computers, and most of us have more than one these days. (We have a total of 6 here, 4 of which are windows machines).
I have joined your affilate program, and shall continue to recommend your excellent products. -
Inappropriate?Eyebee,
Thank you for the information! I'm sure this will help similar users with the same problem. :)
~ Jason
