Hi all, Just a follow up. I'm using a GPO based deployment which has been working fine for years. Using a GPO based deployment means I cant prepend "%~dp0\" (working directory) to the commandline as shown above. I can however use the following command line to reproduce the issue using msiexec /i TeamViewer_host.msi TRANSFORMS=TeamViewer_host.mst" /qb /l*v I contacted TeamViewer support 10(!) days ago. Since I havent heard from them, I asked for an update 4 days ago. Finally today they responded with "Apologies with the delay of my reply. There is no issue at the moment with installing TeamViewer Host with the .reg file imported. Please make sure you're installing the latest host .msi ( 15.3.8497 ), that the file is named TeamViewer_Settings.reg Please also share the script you've been trying to use." Pretty useless answer. :-( Long story short. The problem is clearly related to importing the reg file. The installation works fine with my transform (.MST) file if I keep IMPORTREGFILE=0. Inspired of the prepended %~dp0\ string in the post above, I did a procmon trace of the installation. Notice the "Path": reg.exe is searching for TeamViewer_Setting.reg in all folders of the environment path. This happens only - and only - if reg.exe is called with "import TeamViewer_Settings.reg" (not path to the location) which aligns nicely with the suggested workaround when installing from command line. Opening the event and showing the Process tab also shows this: So the options seems to avoid the IMPORTREGFILE=1 when doing GPO based deployments, The following options can then be used instead: Import the settings via GPP (use the import wizard for a quick import to the GPP) Import the settings via a computer startup/shutdown script calling reg.exe import ... Or ... modify the environment PATH variable on the clients during deployment (or at least undtil TV fixes the issue) to include the UNC path to the installation source. This can be achieved using GPP as well. I anybody has better suggestions - please let me know. I'll keep you posted when someone from TV support hopefully takes the issue seriously and involves development team for a fix.
... View more