• Content count

  • Joined

  • Last visited

  1. V11 .msi silent install fails

    I agree. Installing silently with configuration is really useful to me, and if I didn't have the .msi workaround ESET would be the only software out of my approximately 15-20 software of all types that I install silently via my batch file every time I reformat and reinstall Windows (and I'm not even counting drivers which I also install silently). For most software there is a way to achieve this, i.e. whether silent install or direct copy of the installed software under "Program Files", along with direct configuration as part of the silent install switches, copying AppData folder and/or merging registry settings. I was unable to figure out a way to achieve this for ESET via the registry or AppData routes (I suspect it's possible though and that I just didn't dig deep enough, but this seems more complex than I'm used to).
  2. V11 .msi silent install fails

    Sorry, it is not 100% working unfortunately, despite my post just above. The settings from the cfg.xml file are not applied. Quotes or no quotes. Percent sign or no percent sign. ESET installs with the default settings regardless of having specified --msi-property ADMINCFG=
  3. V11 .msi silent install fails

    Thanks Marcos, I confirm it works now, with a slight modification to your above instructions: -silent should be --silent (you had double dashes everywhere except for the first argument silent and I found it didn't work with a single dash, you really need two dashes everywhere) I also found that the % are not required in the path_to_the_cfg_xml Here's the command that I used, with correction made, and it was successful in a complete silent install of NOD32 using the .exe: eav_nt64.exe --silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eav --msi-property ADMINCFG="D:\Reformat\Programs\NOD32-v11-Config.xml" Replace whatever's between the quotes after ADMINCFG= with the actual path to your own config file.
  4. V11 .msi silent install fails

    Unfortunately, no there were no spaces. My command line was: eav_nt64.exe --silent --accepteula --language 1034 --msi-property ADMINCFG="%D:\Reformat\Programs\ESET-NOD32-v11-Config.xml%" Although I also tried: eav_nt64.exe --silent --accepteula --language 1034 --msi-property ADMINCFG=%D:\Reformat\Programs\ESET-NOD32-v11-Config.xml% (without the quotes as I wasn't sure if these should be included or not, usually not required unless there are spaces in the path, although even without spaces having quotes isn't an issue normally) eav_nt64.exe --silent --accepteula --language 1034 --msi-property ADMINCFG="D:\Reformat\Programs\ESET-NOD32-v11-Config.xml" (without the % symbols that were in your example; again, I wasn't sure if these were needed or not, I usually don't see % other than for environment variables to be expanded) eav_nt64.exe --silent --accepteula --language 1034 --msi-property ADMINCFG="%D:\Reformat\Programs\cfg.xml%" (with a shorter file name, just in case there's some legacy 8 character limitation) eav_nt64.exe --silent --accepteula --language 1034 --msi-property ADMINCFG="%D:\Reformat\Programs\ESET-NOD32-v11-Config.xml%" (single space between property and ADMINCFG, in this this was a typo) eav_nt64.exe -silent -accepteula -language 1034 -msi-property ADMINCFG="%:\Reformat\Programs\ESET-NOD32-v11-Config.xml%" (single dashes instead of double dashes, because, as NBPC mentioned, double dashes for command lines are unusual). I tried all those variants above and the outcome was either a complete failure to accept the command line arguments/switches (no install at all), or an incomplete install (just the EULA files...) as I mentioned in my previous message.
  5. V11 .msi silent install fails

    Sorry it took me so long to test this, but --silent --accepteula --language 1034 --msi-property ADMINCFG="%path_to_the_cfg_xml%" does not work for me when using the .exe installer. The NOD32 install does start (as confirmed by seeing the process in Task Manager) and is silent, but appears to end prematurely and silently (without error message) adter about 10 seconds), and NOD32 does not get installed. C:\Program Files\ESET\ESET Security only contains eula.rtf, eula.html and a "help" folder, but nothing else. So, back to the .msi method for me, as this one works. EDIT: and before someone asks, obviously yes I did replace the ""%path_to_the_cfg_xml%"" with my actual path
  6. V11 .msi silent install fails

    Thanks @Marcos this is very helpful and thanks @NBPC for following-up. I will try those switches tonight and if it works as intended this resolves by issue on my end. (And just to clarify, my initial workaround was to modify the .msi file, but later on based on NBPC's findings a registry method could be used without having to touch the .msi file and this was my preferred approach. Looks like if everything works as described by Marcos I won't have to use the .msi anymore as the .exe installer will do everything I want (silent install and pre-configuration).
  7. V11 .msi silent install fails

    @NBPC, thanks a lot, much better than my approach of hacking the .msi installer file using Orca, and I confirm this also works perfectly for me (it also seems to resolve a few minor issues I was having).
  8. V11 .msi silent install fails

    So, anyone knows of silent install switches for installing using the regular .exe installer (not the .msi installer)?
  9. V11 .msi silent install fails

    Well, it's not a very elaborate use case, I just like installers of software that I use to have silent install switches, that's all. This is what allows me to reformat, reinstall Windows, and run a batch file that I wrote which installs all drivers and software that I use silently and unattended. I like to reformat/reinstall Windows frequently (roughly every month or so), and this makes the difference between a 20 minute operation (silent, automated installs) and a few hours of manually installing and configuring all software.
  10. V11 .msi silent install fails

    Thanks Marcos. I understand consumer products aren't offered as .msi installers. However, the .msi installers are available straight from ESET servers, so surely they are meant for someone (non-consumers?), and that someone will likely run into the same problem I did if they try to silently install. Personally, I don't need my installer to absolutely be a .msi, but I do need silent install and I didn't find a way to achieve that other than using the .msi installer. Is there a way to achieve silent install with the regular .exe installer, including picking up the configuration file so that NOD32 is configured as desired after install? (the old ADMINCFG=cfg.xml trick, which I confirm still works with v11 .msi installers by the way). If this is possible I
  11. V11 .msi silent install fails

    Aha! found a fix to my own issue, or workaround... or a hack actually: I was able to fix by modifying the .msi installer with SuperOrca, as follows: - Open SuperOrca. - Search for ProductACode. - Open section Registry. - At the ProductACode line, replace #[PRODUCT_A_CODE] with [ProductACode] --> this was only a guess from me, but I thought it was off that the string looked different from the one just above, so I made it look the same by typing [ProductACode] in there. - In the line just below (line should be called ProductBase), replace #[PRODUCT_BASE] with [ProductBase]. This is the second registry error that appeared when using /qb - Save the .msi. - Silent install now works without errors, and didn't see anything wrong so far with the functioning of NOD32. Still seems to me like the installer has bugs which should be fixed officially instead of using hacks like this.
  12. Command line (from an administrator CMD window): msiexec /i "eav_nt64.msi" /qn /log log.txt Fails to complete install (progress bar rolls back changes and installer exits). Following error found in log.txt: Error 1406. Could not write value ProductACode to key \Software\ESET\ESET Security\CurrentVersion\Info. System error . Verify that you have sufficient access to that key, or contact your support personnel. EDIT: Error still occurs after setting registry permission to Everyone = Full control for key "HKEY_LOCAL_MACHINE\SOFTWARE\ESET", and taking ownership of the key. EDIT 2: Clarified that I am running CMD with Administrator rights, of course. EDIT 3: Using /qb instead of /qn displays two errors (cannot write registry key) during install, which can be ignored and the install can complete. The registry key HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info does exist after installing this way. Looks like the installer throws an error about not being able to write to this registry key when in fact it can.