FileBot

just downloaded the latest FileBot 3.8 'live' installer for Windows from the home page to install on a Windows 8.1 Pro x64 machine. Selected no to both sponsor co-installs, clicked install, the downloader did it's thing... then I ran into the error below:

msiexec error 1603


Logged in as a local admin account (non domain PC). Tried running normally and 'as administrator', file is not 'blocked' and is being run from the active profile's default 'Downloads' folder.

AV is just the stock Windows Defender, along with Spybot Search & Destroy (which doesn't run any active agents).

rednoah - you seen this one before?

Yep, that's basically a generic error code that doesn't tell us anything...

Do you get this all the time? Even if you just grab the .msi?

You could try this guide and see if we can get some extra logging:
http://www.msigeek.com/715/how-to-troub ... stallation

I don't think I can enable the extra logging in the live downloader as the msi is created on the fly, and I don't believe that command will work when referencing the exe.

As for downloading the msi from sourceforge and trying with that - and with the exception of an issue with shortcuts (issue on my end, don't worry about it), it all went swimmingly, and FileBot opens correctly.

So... looks like it's just an issue with the live installer :-/

Side Note: Much to my amusement, drag and drop, and my network drive both work on this computer, haha.

No, but you could grab the msi and try this from the cmdline: (plus the options for logging)

Though I guess it'll also work. Not sure what the issue might be, I'd guess some sort of anti-virus blocking the installer from installing msi files from temp locations.

This happens because your AV is blocking the installation file of the 3rd party spyware that is bundled with this software (that you can opt out of). THe conduit software that is installed if you pick a default installation is "legal" spy/adware. It sends your searching and browsing habits to conduit. All AV systems will flag this as a virus.. because it is... but you agree to install it on your machine legally.

Hi Demi,

While there is a big difference between adware (and bloatware) versus spyware, I disabled that option during the install, so I'm doubting that was a contributing factor.

That being said tho, my system is configured to block executables from running in %appdata% and %localappdata% because it's a massive security hole (see: http://www.foolishit.com/vb6-projects/cryptoprevent/).

Depending on where it stores the temporary msi it main installer downloads, that could account for it because a mentioned, when I run the separate msi, it works like a charm.

Personally, I'm really not a fan of the current monetisation packages (it is the better vendor of those sort of things, but still not ideal), but without it rednoah would need to find another way to monetise, and finding the right fit for that isn't as easy as it sounds.

Nope, you're getting a msiexec error, which is when the nsis tries to install the .msi package. MSI package (.msi) doesn't contain code, the NSIS installer (.exe) naturally does (including additional install logic and OpenCandy).