Try to install "XDCC-9.1.12_nl_NL_WIN_64" getting the following error:
MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (s) (D8:E8) [15:29:51:453]: Executing op: IconCreate(Icon=ARPPRODUCTICON.exe,Data=BinaryData)
MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CADeploy,,)
MSI (s) (D8:E8) [15:29:51:469]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeployme ntManagerCA,CustomActionData=mode=install;sourceDir=C:\install\XDCC-9.1.12-def\Build\;inst allDir=;origDB=C:\install\XDCC-9.1.12-def\Build\XDCC-9.1.12-def.msi;installLang=)
MSI (s) (D8:2C) [15:29:51:469]: Invoking remote custom action. DLL: C:\windows\Installer\MSI1C78.tmp, Entrypoint: runDeploymentManagerCA
CustomAction CADeploy returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
After that a rolling back will take place and the installation failed. Zie log part below this line.
MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (s) (D8:E8) [15:29:51:453]: Executing op: IconCreate(Icon=ARPPRODUCTICON.exe,Data=BinaryData)
MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CADeploy,,)
MSI (s) (D8:E8) [15:29:51:469]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeployme ntManagerCA,CustomActionData=mode=install;sourceDir=C:\install\XDCC-9.1.12-def\Build\;inst allDir=;origDB=C:\install\XDCC-9.1.12-def\Build\XDCC-9.1.12-def.msi;installLang=)
MSI (s) (D8:2C) [15:29:51:469]: Invoking remote custom action. DLL: C:\windows\Installer\MSI1C78.tmp, Entrypoint: runDeploymentManagerCA
CustomAction CADeploy returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Any idea how to solve this? I cannot install the update on any windows 10 computer.
Up to version XDCC5.0.12_nl_NL_WIN_64 never had such porblem.