It works nicely. The problem that everyone is facing with the unattended switches on the main MSI installer file is with the serial number. If you edit the main installer and force the serial number in the "Property" -> "SERIALNUMBER" entry the installer will run through in full GUI mode perfectly. As soon as you use the silent switch on the MSI the wheels fall off (as stated in another MSFN Nero 10 thread a custom DLL is indeed unpacked and loaded into memory which seems to strip the serial info when silently installed). You can check this by adding the "log errors" option "/le c:\nero.txt". Check the text file and it says the install failed due to no serial being present, even though we have forced it. A ll the main MSI does is check the serial number, then execute each Nero app installer in sequence. My solution is to bypass the main MSI installer eliminating the main problem, and then by hijacking a dummy registry entry in the Nero Burning MSI installer so that our serial is written to the registry so that "advrcntr5.dll" is satisfied Nero 10 has been installed properly. You can use this method to add more serials into the registry for plugins etc. As long as the "Registry" -> [name] you add is unique and you put that row into the same "Group" it will be executed. It may be possible to also hunt down and remove the install sequence that loads the custom DLL, but with previous experiences with other programs this will most likely make the installer crash. Another option is to author your own simplified main MSI installer and replace the Nero one. I think this is too much work compared to compiling a simple Inno Setup script and repacking the individual Nero installers.